agent-readiness-scan

Solid

Use when a client audit, GEO/AI-visibility snapshot, or remediation re-scan needs the Cloudflare agent-readiness score from isitagentready.com — e.g. Theo client audits, "is the site agent-ready", markdown negotiation / MCP / llms.txt / Content-Signal checks, or tracking score deltas after Tier 0/1 fixes.

AI & Automation 13 stars 2 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
38
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Agent-Readiness Scan (isitagentready.com) Produce the official Cloudflare agent-readiness result for a domain as audit-grade artifacts: fixed-schema CSV + raw evidence + the 0-100 score. ## Critical facts (learned the hard way) 1. **Two sources, both required:** - `POST https://isitagentready.com/api/scan` body `{"url":"https://<domain>"}` → full JSON (level, levelName, per-check status + embedded request/response evidence, nextLevel remediation prompts + skillUrls). **No numeric score in the JSON.** - **The 0-100 score renders only in the web UI.** Playwright-navigate to `https://isitagentready.com/<host>` and read the score dial: an `<svg>` carrying `aria-label="Overall score: N out of 100"`. **Never `wait_for` that text** — it's an attribute, not visible text (text-waits time out). Take a page snapshot or evaluate `document.querySelector('[aria-label*="Overall score"]')`. A fresh "Last scanned" timestamp = results are rendered (the step-1 API POST itself refreshes the scan, so no Scan click is normally needed). Without the 0-100 you cannot track deltas (e.g. a site improving 21→43 after fixes). 2. **Don't freeze the checklist.** The scanner evolves (new checks appear). Emit whatever `.checks` returns, mapped through the fixed CSV schema — never hand-author check rows. 3. **Scored vs supplementary.** llms.txt, llms-full.txt, security.txt are NOT scored by Cloudflare but Theo audits track them — they go in `Supplementary (not scored)` rows from curl probes, never ...

Details

Author
techhorizonlabs
Repository
techhorizonlabs/thl-open
Created
1 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

agent-readiness-audit

Audit whether AI agents can actually use your product — docs, APIs, onboarding, errors, and discoverability, evaluated from a non-human user's perspective. Use when asked if a product is agent-ready, to audit a site or API for AI usability, to prepare for agentic traffic, or when agents keep failing against your product. Produces a scored readiness report with per-surface findings and a prioritised fix list. For optimising a single article for AI citation use aeo-optimizer; for designing the MCP server itself use mcp-server-spec.

1,228 Updated today
mohitagw15856
Web & Frontend Listed

agent-web-audit

Audit a website or web app for AI-agent readiness, accessibility, and AI-search legibility, then fix the issues found. Use this skill whenever the user wants their site to work well for AI agents or LLMs (Claude, ChatGPT, Perplexity, Grok, Gemini, browser agents), or mentions "agentic SEO", "GEO", "AEO", "AI-friendly site", "agent-ready", "accessibility tree", "llms.txt", "make my site readable for AI", or the Lighthouse "Agentic Browsing" audit. Also trigger when the user asks to check or fix a frontend for semantic HTML, ARIA, label linking, cursor:pointer, layout stability, or how a site appears to crawlers and agents. Works on plain HTML, React/Next.js, Vue, and server-rendered templates. Trigger even if the user only says "make this site useful for AI" without naming a specific check.

0 Updated 3 days ago
ahmadabdulnasir
AI & Automation Solid

agent-readiness

Score a task or workflow on its coordination-vs-judgment ratio to tell whether it's a good agent candidate (EXO 3.0 task-decomposition matrix).

75 Updated today
JKHeadley