CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docs

Write or revise a page under docs/ for gofastmcp.com. Use when adding a feature's documentation, fixing a docs issue, reworking a page, or auditing pages for accessibility and consistency. Covers the page shape, the voice, the checks that run in CI, and how a merged page reaches the live site.

Quality

95%

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

SKILL.md
Quality
Evals
Security

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.

The body is a dense, fully actionable working document: exact commands, a complete page template, explicit validation with a fix-and-rerun loop, and gotchas grounded in specific file paths. Its only structural tradeoff is keeping all reference material inline in a single file rather than splitting some into bundle references.

DimensionReasoningScore

Conciseness

Every sentence carries project-specific information Claude could not infer (the Mintlify/published-docs deploy flow, "A page exists only when docs/docs.json lists it", the frozen v2/v3 snapshots, the mcp_types naming), with no padding and no explanation of already-known concepts, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Guidance is fully executable: copy-paste commands ("rg -l \"<feature>\" docs --glob '!docs/python-sdk/**'", "npx --yes mint@latest broken-links", "uv run pytest tests/docs -n 0"), a complete MDX page template, and exact config locations ("navigation.versions[0].version") cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The six-step Procedure is clearly sequenced with an explicit validation checkpoint ("Run the checks in **Verify** and fix what they report") backed by named commands, expected outputs, and an escape hatch ("A block that must not run takes test=\"skip\" on its fence"), matching the anchor with explicit validation and error-recovery guidance.

5 / 5

Progressive Disclosure

Sections (Procedure, Template, Voice, Accessibility, Verify, Gotchas) are well-labeled and the one external pointer ("follow 'Publishing docs by hand' in .agents/skills/release/SKILL.md") is clearly signaled and one level deep. However, at ~84 lines with the template, voice, accessibility, and gotchas all inlined, it sits just above the under-50-line single-file case the rubric exempts, so structure is good but not the ideal split of a 5.

4 / 5

Total

19

/

20

Passed

Description

92%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 explicitly states both what the skill does and when to use it, with concrete trigger phrases and a site-specific scope that sharply limits conflict risk. Its only weakness is keyword coverage that omits a few natural synonyms a user might say.

DimensionReasoningScore

Specificity

"Write or revise a page under docs/", "adding a feature's documentation", "fixing a docs issue", "reworking a page", "auditing pages for accessibility and consistency" lists multiple concrete actions that comprehensively cover the skill's domain, matching the anchor for comprehensive concrete actions rather than the anchor 4 example with minor gaps.

5 / 5

Completeness

The 'what' is explicit ("Write or revise a page under docs/ for gofastmcp.com… Covers the page shape, the voice, the checks that run in CI") and the 'when' is explicit with concrete trigger phrases ("Use when adding a feature's documentation, fixing a docs issue, reworking a page, or auditing pages…"), clearly matching the anchor that answers both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural terms users would say are present ("docs", "documentation", "docs issue", "accessibility", "page"), but a few common variations such as "Mintlify", "user guide", or "how-to" are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to a specific niche ("a page under docs/ for gofastmcp.com") with distinct triggers (docs issues, accessibility audits for this site), giving minimal overlap risk with generic documentation skills; it clearly matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

19

/

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

PrefectHQ/fastmcp

Path

.agents/skills/docs/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.