CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastmcp-server

Build, extend, or review MCP servers with Python FastMCP, using documentation matched to the project's version.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/fastmcp-server/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.

This is a strong, expert-oriented instruction skill: lean prose with no filler, concrete named APIs and verification steps, and a coherent author-then-verify-then-evaluate workflow. Its main gaps are the absence of any executable code example and a single long Authoring section that could be split for easier navigation.

DimensionReasoningScore

Conciseness

The body is dense, expert-level guidance with no padding and no explanation of concepts Claude already knows — e.g., "An upstream failure is not an empty result" and "Namespace transforms change component names and resource URIs, but do not rewrite URI text inside prompt messages" deliver non-obvious, load-bearing facts in single sentences. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Concrete, named facilities appear throughout: fetch the llms.txt index and select /v3/ pages by installed version, use ToolError/ResourceError/PromptError from fastmcp.exceptions, functools.wraps for SDK wrappers, mask_error_details=True caveats, Client for in-process verification, and SkillsDirectoryProvider/SkillCatalogProvider for skill serving. It is mostly executable guidance but includes no copy-paste code or commands, so it sits at anchor 4 rather than 5; per the scoring notes the absent code is not itself penalized for an instruction-only skill.

4 / 5

Workflow Clarity

A clear sequence runs from version-matched API discovery, through authoring (interface choice, error handling, skills), to explicit verification via Client and agent-workflow evaluation, with a feedback loop ("Inspect traces for discovery misses... before changing tool descriptions or structure"). It is not rendered as an explicit step list with checkpoints or checklists, so it matches anchor 4 rather than 5; no destructive/batch cap applies.

4 / 5

Progressive Disclosure

Sections are clearly headed, and detail is deferred one level deep to well-signaled external versioned documentation ("Fetch [the documentation index](https://gofastmcp.com/llms.txt)... Read individual pages through their .md URLs"). The ~90-line single-file body is still somewhat monolithic — the multi-topic "Author the server" section (interface choice, errors, tool search, skills, verification) could be split — keeping it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

61%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 concise, third-person, and names a distinct niche with the right primary trigger terms (MCP, FastMCP), but it stops at high-level verbs and omits any explicit "when to use" guidance. Adding a trigger clause and a synonym such as "Model Context Protocol" would raise completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or reviewing MCP (Model Context Protocol) servers in Python, or when the user mentions FastMCP."

Include the full term "Model Context Protocol" alongside "MCP" so users who spell out the protocol name still match the description.

Mention one or two concrete capabilities (e.g., defining tools, resources, and prompts, or verifying servers with FastMCP's Client) to sharpen the what.

DimensionReasoningScore

Specificity

"Build, extend, or review MCP servers with Python FastMCP" names the domain plus three action verbs, but the verbs are high-level and no concrete capabilities (tools, resources, auth, transports) are enumerated. It matches anchor 3 (domain plus a couple of actions, not comprehensive) more than anchor 4, whose examples list specific concrete operations.

3 / 5

Completeness

The "what" is clear (build, extend, or review MCP servers with FastMCP using version-matched documentation), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The "when" is at best weakly implied by naming the domain.

3 / 5

Trigger Term Quality

"MCP servers", "Python FastMCP", and "Python" are exactly the natural terms a user would say when needing this skill. It falls short of anchor 5 only because common synonyms such as "Model Context Protocol" are missing.

4 / 5

Distinctiveness Conflict Risk

"MCP servers with Python FastMCP" carves a clear niche with minimal conflict risk. Minor overlap remains with closely related skills (e.g., the Python MCP SDK), and the description does not carry the body's distinction that the standalone fastmcp package differs from mcp.server.fastmcp, so it is not anchor 5.

4 / 5

Total

14

/

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

skills/fastmcp-server/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.