CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-review

Review fallow's MCP server for tool contract clarity, output stability, and agent usability. Use when changes touch crates/mcp or AI-agent integration surfaces.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/mcp-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, well-organized instruction-only skill that delegates detail to two referenced files and ends with a constrained verdict. Its only real weakness is that the referenced files are repo paths outside the skill bundle rather than bundled reference files.

DimensionReasoningScore

Conciseness

Extremely lean overview that assumes Claude's competence: a short read list, focus bullets, and a required verdict, with every token earning its place.

5 / 5

Actionability

Gives concrete, actionable guidance—specific files to read, explicit focus areas, and a constrained verdict set (APPROVE/CONCERN/BLOCK); the actual review criteria live in the referenced files, leaving a minor gap inline.

4 / 5

Workflow Clarity

A clear read-then-review-then-conclude sequence with a defined output; no validation checkpoint is needed for a verdict-producing review skill, but the sequence is simple rather than richly sequenced.

4 / 5

Progressive Disclosure

Well-structured overview with clearly signaled one-level-deep references to the reviewer and rules files; the referenced paths live in the repo rather than the skill bundle, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

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

The description clearly states what the skill does and when to use it, with concrete review dimensions and a codebase-specific trigger. Its main weakness is the repo-path-bound trigger language, which is less natural for users than generic MCP-related phrasing.

Suggestions

Add natural-language trigger synonyms such as 'MCP server', 'tool definitions', or 'agent tools' so the skill surfaces when users describe these in plain terms rather than only via the crates/mcp path.

Consider listing one or two more concrete review actions (e.g. 'validate JSON schema of tool outputs') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (MCP server review) and several concrete review actions ('tool contract clarity', 'output stability', 'agent usability'); minor coverage gaps keep it just below comprehensive.

4 / 5

Completeness

Both 'what' (review MCP server for the three listed qualities) and 'when' ('Use when changes touch crates/mcp or AI-agent integration surfaces') are present; the 'when' could be more explicit.

4 / 5

Trigger Term Quality

Includes relevant terms ('MCP server', 'AI-agent integration') but the trigger is bound to a repo path ('crates/mcp') rather than natural user phrasing, and lacks common synonyms/variations.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (MCP server review tied to a specific codebase) with distinct triggers; minor overlap risk with general code-review skills keeps it at 4 rather than 5.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fallow-rs/fallow
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.