CtrlK
BlogDocsLog inGet started
Tessl Logo

mlava/agent-ready-mcp

Install and use the Agent Ready (agent-ready.dev) MCP server to scan any URL for AI agent-readability via MCP tool calls. Activates for "install agent-ready mcp", "set up agent-ready in Claude Desktop / Cursor / Cline / Goose / Continue", "add agent-ready as an MCP tool", "scan this site via agent-ready", "run scan_site / get_scan / ask via MCP". Pick this skill when the user wants tool-native access to Agent Ready — no curl, no fetch wiring. For direct REST access without MCP, use the `agent-ready-api` skill instead.

72

Quality

90%

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

78%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.

Highly actionable, well-sequenced content with copy-paste config and thorough error recovery, slightly held back by minor redundancy and by referencing bundle files (CLIENT_CONFIGS.md, REFERENCE.md) that are not actually shipped.

Suggestions

Ship the referenced bundle files CLIENT_CONFIGS.md and REFERENCE.md (or inline their essential content) — both are linked from the body but absent from references/, so navigation breaks for the reader.

De-duplicate the keyless/free-tier guidance: it is restated in Step 1, Step 2's env note, and the scan_site table row; state it once and reference back.

Add a one-line verification step after Step 3 (e.g., confirm the chosen tool's required parameters are present before invoking) to strengthen the workflow's checkpoints.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the keyless/free-tier point is restated across Step 1, Step 2, and the tool table, and a few sentences could be tightened without losing clarity.

4 / 5

Actionability

Provides a copy-paste-ready MCP config block with exact macOS/Windows config paths, concrete tool signatures (url, pageLimit), named prompts, and a full error-code-to-recovery mapping — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

A clear Step 1–6 sequence with an explicit verification checkpoint ('After restart it should advertise three tools') and an Errors and recovery feedback section, though validation checkpoints are otherwise light (acceptable since scanning is read-only, not destructive/batch).

4 / 5

Progressive Disclosure

Structure and one-level-deep signaling are good (Step sections, Reference section linking CLIENT_CONFIGS.md and REFERENCE.md), but both referenced files are absent from the bundle, so the navigation the body promises is broken.

3 / 5

Total

16

/

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 strong, well-crafted description that states concrete capabilities, provides natural trigger phrases, answers both what and when explicitly, and disambiguates from a related skill. No fluff or over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Install and use the Agent Ready MCP server to scan any URL' and the specific tools 'scan_site / get_scan / ask' — giving comprehensive coverage of the skill's capabilities rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' (install/use the MCP server to scan URLs via tool calls) and 'when' ('Pick this skill when the user wants tool-native access to Agent Ready', with concrete 'Activates for' trigger phrases).

5 / 5

Trigger Term Quality

Lists comprehensive natural trigger phrases users would actually say ('install agent-ready mcp', 'set up agent-ready in Claude Desktop / Cursor / Cline / Goose / Continue', 'scan this site via agent-ready') plus tool names, covering synonyms and client variants.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Agent Ready MCP tool-native access) and actively disambiguates from the sibling skill: 'For direct REST access without MCP, use the agent-ready-api skill instead', minimizing conflict risk.

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: 4 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents