CtrlK
BlogDocsLog inGet started
Tessl Logo

mlava/agent-ready-api

Use the Agent Ready (agent-ready.dev) REST API to scan any public URL for AI agent-readability against the Vercel Agent Readability Spec, the llmstxt.org standard, and agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). Activates for "scan this site for AI agent-readability", "run an Agent Ready scan on {URL}", "check the Agent Ready score for {URL}", "what's the agent-readability rating for {URL}", or any time the user wants a programmatic readability scan via HTTP. Picks this skill when the user does NOT have the Agent Ready MCP server installed — for MCP, use the `agent-ready-mcp` skill instead.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable, well-sequenced REST API workflow with executable code and good error/rate-limit/security guidance. Its main weakness is progressive disclosure: EXAMPLES.md and REFERENCE.md are referenced but not bundled, so those links are dead.

Suggestions

Bundle the referenced EXAMPLES.md (Node/TypeScript and Python start-and-poll equivalents) and REFERENCE.md (endpoint list / OpenAPI spec) alongside SKILL.md, or remove the links and inline the essential parts.

Trim the repeated spec-name list in the opening paragraph since it already appears in the description frontmatter, to improve token efficiency.

Add a short validation note on the response shape for Step 2 (confirm the 202 + pollUrl contract) so the poll step's precondition is explicit.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the opening paragraph re-lists the spec names already present in the description, a minor redundancy that could be trimmed; otherwise efficient.

4 / 5

Actionability

Fully executable curl commands with real Authorization/Content-Type headers, JSON bodies, a jq-driven poll loop, and a public no-key /ask example — copy-paste ready and covering the common start/poll/summarise/ask cases.

5 / 5

Workflow Clarity

A clear numbered Step 1–5 sequence with ordered API-key scenarios, explicit terminal-status handling ('the terminal values are completed and failed'), and checkpoints (capture id, poll until status leaves running, treat failed as no usable score).

5 / 5

Progressive Disclosure

References are one level deep and clearly signaled (EXAMPLES.md, REFERENCE.md), but neither file exists in the skill bundle — the references/ assets/ scripts/ directories are absent, so the linked navigation does not resolve, leaving structure present but navigation broken.

3 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that clearly answers both what the skill does and when to use it, with strong disambiguation against the sibling MCP skill. It is on the verbose side due to the spec-name list, but every phrase earns its place.

DimensionReasoningScore

Specificity

Quotes concrete actions ('scan any public URL for AI agent-readability against the Vercel Agent Readability Spec, the llmstxt.org standard, and agent-protocol manifests') and enumerates the manifest types, giving comprehensive specific coverage rather than vague language.

5 / 5

Completeness

Explicitly states the 'what' (REST API scan of a URL against named specs) and the 'when' ('Activates for ... or any time the user wants a programmatic readability scan via HTTP'), with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes several natural user phrases verbatim ('scan this site for AI agent-readability', 'run an Agent Ready scan on {URL}', 'check the Agent Ready score for {URL}') with synonym coverage and the {URL} placeholder, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

A clear niche (programmatic HTTP agent-readability scanning) plus explicit disambiguation from the sibling skill ('for MCP, use the `agent-ready-mcp` skill instead') keeps conflict risk minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents