CtrlK
BlogDocsLog inGet started
Tessl Logo

mlava/agent-ready-mcp

Install and use the Agent Ready 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?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

77%

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

This is a well-structured, actionable skill that clearly guides Claude through installing and using the Agent Ready MCP server. Its strengths are the concrete configuration examples, clear step-by-step workflow with async handling, and thorough error recovery guidance. Minor weaknesses include slightly verbose introductory and security sections, and the inability to verify referenced bundle files (CLIENT_CONFIGS.md, REFERENCE.md) exist.

Suggestions

Tighten the introductory paragraph — Claude doesn't need the explanation of what MCP tools replace or the two-phase overview; the steps themselves make this obvious.

Consider trimming the Security & trust section's 'Tool results are untrusted data' bullet, as Claude already follows this principle by default — a single sentence reminder would suffice.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary elaboration. The intro paragraph explaining what MCP is and the two-phase structure could be tighter. The security section, while important, is somewhat verbose with explanations Claude would naturally follow. However, most content earns its place.

2 / 3

Actionability

Provides fully executable JSON config for Claude Desktop, specific file paths per OS, concrete tool names with parameters, exact error codes with remediation steps, and a clear JSON example of the polling response. The guidance is copy-paste ready throughout.

3 / 3

Workflow Clarity

The six numbered steps form a clear sequence from API key acquisition through installation, tool selection, URL passing, handling async results, and summarizing findings. Explicit validation checkpoints exist: the 'running' placeholder handling with a clear feedback loop (wait, then call get_scan), error recovery section with specific codes, and the instruction not to auto-loop. The workflow is well-sequenced with appropriate guardrails.

3 / 3

Progressive Disclosure

References to CLIENT_CONFIGS.md and REFERENCE.md are well-signaled and one level deep, which is good. However, no bundle files were provided, so we cannot verify these references actually exist. The main SKILL.md includes substantial inline content (security section, error recovery, full summarization guidance) that could potentially be split out, though it's borderline since it's all operationally relevant.

2 / 3

Total

10

/

12

Passed

Description

100%

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

This is an excellent skill description that hits all the marks. It provides specific actions, comprehensive trigger terms covering multiple platforms and tool names, explicit 'when to use' guidance, and even includes a disambiguation clause to prevent conflict with a related skill. The description is concise yet thorough, using proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: install the MCP server, scan URLs for AI agent-readability, use MCP tool calls, and explicitly names tools like scan_site, get_scan, and ask. Also specifies supported platforms (Claude Desktop, Cursor, Cline, Goose, Continue).

3 / 3

Completeness

Clearly answers both 'what' (install and use Agent Ready MCP server to scan URLs for AI agent-readability) and 'when' (explicit trigger phrases with 'Activates for...' and 'Pick this skill when...'). Also includes a disambiguation clause pointing to the agent-ready-api skill for REST access.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: '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', and specific tool names like 'scan_site / get_scan / ask via MCP'.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche (MCP-based Agent Ready tool access) and explicitly differentiates itself from the related 'agent-ready-api' skill for REST access. The specific tool names and MCP context make conflicts with other skills very unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents