CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release

Cut a FastMCP release end to end. Use when the maintainer says "cut a release", "prep a patch", "ship 4.x.y", or asks what a release would contain. Covers the notes preview, the title pun, the docs changelog PR that must land before the tag, the tag itself, the publish fan-out, and verifying gofastmcp.com actually deployed.

Quality

94%

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

88%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 highly actionable, well-sequenced runbook with real executable commands and thorough validation checkpoints for irreversible operations. Its only weaknesses are minor: slight repetition and long policy prose in the attribution section, and a couple of references that resolve outside the skill bundle.

Suggestions

State the docs-PR-appears-in-GitHub-notes-but-not-the-mirror fact once (step 4) and have step 5 reference it instead of restating it.

Reference the helper scripts with skill-relative paths (e.g., scripts/changelog_entry.py) and note that scripts/release_contributor_credit.py lives at the repository root, so paths resolve unambiguously from the skill bundle.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific operational knowledge and explains nothing Claude already knows, but it is not perfectly lean: the docs-PR-not-in-its-own-mirror point is stated in both steps 4 and 5, and the attribution-policy prose in step 1 runs long. This matches the efficient-with-minor-trimmable-instances anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Commands are copy-paste ready with clearly marked placeholders — the notes preview (git log, gh api generate-notes, uv run helper), changelog entry with validator, gh release create --notes-file, fan-out watches with --exit-status, and curl/jq verification checks. Not score 4: the commands are complete and cover the common cases (patch vs. point release, maintenance branch) rather than leaving minor gaps.

5 / 5

Workflow Clarity

A numbered 1–7 procedure with explicit validation checkpoints at every risky step: the mint broken-links validator ("repeat until it reports no errors"), re-running the preview before tagging with a recovery path if the branch moved, watching the publish fan-out to completion, and a count-based "Check before finishing" checklist. Feedback loops for red deploys and Mintlify queue backlogs are spelled out, which satisfies the validation bar for irreversible operations like tagging and immutable PyPI publishes.

5 / 5

Progressive Disclosure

Sections are well organized (Procedure, Publishing docs by hand, Publication checks, Template, Gotchas, Check before finishing) and the changelog_entry.py reference is one level deep and verified present in the bundle. Not score 5: the script is referenced by repo-root path (.agents/skills/release/scripts/changelog_entry.py) rather than a skill-relative link, and scripts/release_contributor_credit.py plus the contributing.mdx link are not part of the bundle, leaving minor navigation gaps.

4 / 5

Total

18

/

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.

The description is exemplary: third-person, concise, and concrete, covering the full release pipeline while explicitly listing quoted trigger phrases a maintainer would naturally use. It fully satisfies the what/when requirement with minimal conflict risk.

DimensionReasoningScore

Specificity

"Cut a FastMCP release end to end" plus "Covers the notes preview, the title pun, the docs changelog PR that must land before the tag, the tag itself, the publish fan-out, and verifying gofastmcp.com actually deployed" enumerates multiple concrete actions spanning the whole release lifecycle with no generic filler. This matches the comprehensive-coverage anchor; score 4 would require minor gaps, but every pipeline stage is named.

5 / 5

Completeness

Explicitly answers both: "what" via the enumerated pipeline stages and "when" via the explicit "Use when the maintainer says..." clause with concrete quoted trigger phrases. The score-4 anchor ('when' could be more explicit) does not apply because the when-clause is already fully concrete.

5 / 5

Trigger Term Quality

Quotes the natural phrases a maintainer would actually say — "cut a release", "prep a patch", "ship 4.x.y", "asks what a release would contain" — giving comprehensive synonym coverage of the request forms. Score 4's anchor (a few natural terms missing) fits less well, since the quoted set already spans the plausible phrasings for this niche.

5 / 5

Distinctiveness Conflict Risk

Pins a clear niche (the FastMCP release process, gofastmcp.com deployment, the docs changelog PR) with maintainer-specific triggers like "ship 4.x.y", so overlap with any other skill is minimal. It clearly matches the distinct-triggers anchor rather than the minor-overlap anchor at 4.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

PrefectHQ/fastmcp

Path

.agents/skills/release/SKILL.md

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.