Agent Ready

What it does

When your agent uses it

• Asked to make our site agent-ready
• Improve Agent Score
• Fix llms.txt coverage
• Agents keep 404ing on our docs

Example prompts

• “make our site agent-ready”
• “improve Agent Score”
• “fix llms.txt coverage”
• “/agent-ready”

Requirements

• Node.js
• A Bash shell
• Compatibility (from SKILL.md): The verification script needs Bash and curl. Scanner commands need Node.js and npm registry access.

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1The map: llms.txt on the docs host, a link to it in the first lines of every markdown twin, and Link headers that advertise both. Agents…
2. 2Failures the product actually has (docs HTML that agents cannot read, HTML error pages on a real API, gated public docs with no alternate…
3. 3Warnings on those same surfaces (llms.txt coverage, buried directives, wrong Content-Type).
4. 4Recommended checks that match a surface already in the repo (OpenAPI, MCP, OAuth).
5. 5Emerging extras (commerce protocols, A2A, DNS-AID) only when the product already offers them or the user asked to add them.

What it can do on your machine

Read from SKILL.md and the folder at commit cef4cfa. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (Shell), which the agent can run.

  Shell commands in SKILL.md call:

  • npx

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • isitagentready.com
  • llmstxt.org

  Also links to:

  • github.com
  • is-agentic.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  The verification script needs Bash and curl. Scanner commands need Node.js and npm registry access.

  From compatibility in the SKILL.md frontmatter.

Context cost

Agent Ready loads about 2.1k tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 973 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~96

When it runs · the whole SKILL.md, loaded when a task matches

~2.1k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mblode/agent-skills at commit cef4cfa, republished under its MIT licence (© mblode). 973 words, ~2,081 tokens.

name

agent-ready

description

Implements agent-readiness on public sites and docs from Mintlify Agent Score, AFDocs, Is Agentic, Is It Agent Ready, or url-discovery-bench reports, or from server logs of agents 404ing on guessed URLs. Use when asked to "make our site agent-ready", "improve Agent Score", "fix llms.txt coverage", "agents keep 404ing on our docs", or when a pasted scorecard is the brief.

compatibility

The verification script needs Bash and curl. Scanner commands need Node.js and npm registry access.

Agent-ready progress:
- [ ] Step 1: Ingest the report, the agent 404 log, or run scanners against the public URL
- [ ] Step 2: Inspect the existing codebase before any edit
- [ ] Step 3: Inventory every knowledge surface the origin serves and map each finding to a real one; skip surfaces the product does not offer
- [ ] Step 4: Load the matching reference and implement the map first, then failures, then warnings. For Next.js App Router `llms.txt` and markdown routes, load `seo` (that skill's `nextjs-implementation.md` and `answer-engines.md`) instead of a second recipe.
- [ ] Step 5: Add or update tests for every behavior you change
- [ ] Step 6: Verify every public endpoint and machine-readable file you touched (`scripts/check-surfaces.sh`, then the curl recipes for anything it does not cover)
- [ ] Step 7: Report changes, quoted verification, and remaining product decisions

npx afdocs check <docs-url> --format scorecard --sampling deterministic
npx is-agentic <domain> --json

© mblode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references) in skills/agent-ready of mblode/agent-skills.

• SKILL.md
• evals/evals.json
• references/api-surfaces.md
• references/docs-afdocs.md
• references/site-discovery.md
• references/verification.md
• scripts/check-surfaces.sh

Open the folder on GitHubat commit cef4cfa