CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-issue

Carry a selected FastMCP bug from reproduction through a scoped fix, compatibility review, validation, and a monitored pull request.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 lean, well-sequenced orchestration skill that delegates executable detail to specialized sibling skills while retaining concrete directives, explicit validation checkpoints, and a clear feedback loop. Its only minor gap is relying on those references for fully copy-paste-ready commands.

DimensionReasoningScore

Conciseness

The ~20-line body is lean and directive with no over-explanation of concepts Claude already knows; every line ('Reproduce the failure on unchanged code, confirm it fails for the right reason') earns its place.

5 / 5

Actionability

Guidance is concrete and specific (named files AGENTS.md/CONTRIBUTING.md, named skills, 'smallest causal fix', 'test explicit overrides and neighboring supported paths'), with only minor gaps from deferring executable detail to referenced skills.

4 / 5

Workflow Clarity

A clear sequenced workflow (Establish the contract → Red, green, review → Publish and follow through) with explicit validation checkpoints and a feedback loop: 'If a required check fails, investigate and report evidence rather than hiding the failure.'

5 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep cross-skill links ([review-issue], [python-tests], [code-review], [review-pr]); as an orchestration skill with no own bundle files, this is appropriate progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

71%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 is specific and well-scoped to a concrete FastMCP bug-fix pipeline, with strong action coverage and a clear niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the 'when to use' only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when assigned a FastMCP bug to fix end-to-end, or when the user asks to reproduce, fix, and open a PR for a selected issue.'

Include common trigger synonyms like 'issue', 'defect', or 'PR' alongside 'bug' and 'pull request' to broaden natural-language match coverage.

DimensionReasoningScore

Specificity

Names the FastMCP bug domain and five concrete pipeline actions — 'reproduction', 'scoped fix', 'compatibility review', 'validation', and 'monitored pull request' — giving comprehensive coverage of the workflow.

5 / 5

Completeness

The 'what' is clearly stated (carry a bug through the full fix pipeline), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like 'bug', 'fix', 'reproduction', 'pull request', and 'validation' are present, but common synonyms a user might say ('issue', 'PR', 'patch') are missing.

4 / 5

Distinctiveness Conflict Risk

The FastMCP-scoped end-to-end fix niche is distinct, but there is minor overlap risk with the closely related review-issue, code-review, and review-pr skills it delegates to.

4 / 5

Total

16

/

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 suspicious

Warning

Total

15

/

16

Passed

Repository
PrefectHQ/fastmcp
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.