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

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A strong, expert-level procedural skill: executable commands throughout, explicit validation and recovery loops for an immutable operation, and lean prose that assumes competence. Only minor room to split deeper reference material, otherwise excellent.

Suggestions

The 'Publishing docs by hand' section could optionally live in a separate reference file referenced one level deep, keeping the main procedure focused on the release flow.

Consider a one-line pointer near the script invocation describing what changelog_entry.py produces, so the dependency on the bundle file is signposted without opening it.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout — assumes Claude knows git/gh/PyPI/Mintlify and never pads with background; prose present (e.g. 'The slim run is keyed to the tag; the others are workflow_run events') carries non-obvious domain knowledge that earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready commands at every step (git fetch/log, gh api/create/run watch, uv run changelog_entry.py, npx mint broken-links, curl verify), with placeholders and concrete flag values covering the common cases.	5 / 5
Workflow Clarity	Clearly sequenced 7-step procedure with explicit validation checkpoints (broken-links validator 'repeat until it reports no errors', --exit-status run watches, endpoint grep checks) and feedback loops (step 5 re-run if branch moved, step 7 fix-and-republish), appropriate for an immutable-release operation.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Procedure, Publishing docs by hand, Template, Gotchas, Check before finishing) with a single one-level-deep, well-signaled script reference (scripts/changelog_entry.py invoked with full usage); the bulk of the procedure is appropriately inline rather than split further.	4 / 5
	Total	19 / 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.

An excellent description: third-person voice, concrete action list, explicit 'Use when' trigger clause with natural quoted phrases, and a tightly scoped niche with negligible conflict risk. No improvements needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'notes preview', 'the title pun', 'docs changelog PR that must land before the tag', 'the tag itself', 'the publish fan-out', and 'verifying gofastmcp.com actually deployed' — giving comprehensive coverage of the release lifecycle.	5 / 5
Completeness	Explicitly answers both: 'what' ('Cut a FastMCP release end to end. Covers the notes preview...verifying gofastmcp.com actually deployed') and 'when' ('Use when the maintainer says...'), both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Quotes natural maintainer phrases users would actually say — "cut a release", "prep a patch", "ship 4.x.y", and 'asks what a release would contain' — covering the realistic trigger space for this niche.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (FastMCP release cutting) with distinct maintainer-triggered phrases and a specific deploy-verification step, making overlap with other skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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: PrefectHQ/fastmcp
Path: .agents/skills/release/SKILL.md
Commit: 345647d

Reviewed: 5 hours ago

Table of Contents

Discovery Implementation Validation

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.