mcp-development

MCP server development including tool design, resource endpoints, prompt templates, and transport configuration

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mcp-development/SKILL.md

Quality

Content

80%

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, highly actionable MCP reference with executable code and a useful anti-patterns/checklist section, but it is a monolithic single-file reference with no progressive disclosure to bundle files and no explicit multi-step workflow with validation feedback loops.

Suggestions

Move the per-capability code references (tools, resources, prompts) into separate files under references/ and keep SKILL.md as a concise overview that links one level deep, lifting progressive_disclosure toward 3.

Add a short sequenced 'Build an MCP server' workflow with explicit validation checkpoints (e.g. validate Zod schemas, test tool via stdio, verify error responses carry isError) to raise workflow_clarity.

Define or note the undefined helpers used in examples (glob, db, loadConfig, redactSecrets) so the code is fully self-contained and copy-paste runnable.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code with minimal prose and no preamble explaining what MCP/libraries are; it assumes Claude's competence and every section earns its place, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	It provides complete, specific, copy-paste-ready TypeScript for tools, resources, prompts, transport, and a concrete JSON client config, matching the 'fully executable code/commands; specific examples; copy-paste ready' anchor rather than the pseudocode at 2.	3 / 3
Workflow Clarity	Content is organized into clear topical sections and includes a verification Checklist, but it presents reference patterns rather than an explicit sequenced multi-step workflow with validation checkpoints and feedback loops, so it sits at the 'steps listed but checkpoints missing/implicit' level rather than 3.	2 / 3
Progressive Disclosure	No bundle files exist and the SKILL.md is a single ~180-line file holding all code inline; sections are well-organized (so not a 1), but the inline reference bulk that could be split into separate files matches the 'content that should be separate is inline' 2-anchor rather than a one-level-deep reference structure.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly scopes a distinct niche (MCP server development) and lists its concrete components, but it omits any explicit 'Use when...' trigger guidance and leans on noun phrases rather than action verbs, which limits specificity and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or configuring MCP servers, or when the user mentions MCP, Model Context Protocol, tool/resource/prompt endpoints, or server transports.'

Rephrase the component list as concrete actions (e.g. 'Design tools, expose resource endpoints, build prompt templates, configure stdio/SSE transports') to lift specificity from 2 to 3.

Include the spelled-out 'Model Context Protocol' alongside 'MCP' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('MCP server development') and enumerates concrete sub-capabilities ('tool design, resource endpoints, prompt templates, and transport configuration'), but these are noun phrases rather than the concrete verb-actions (e.g. 'Extract... fill... merge') that anchor a 3.	2 / 3
Completeness	It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	'MCP' and 'MCP server' are natural trigger terms a user would say, but the surrounding terms are technical jargon and common variations like the spelled-out 'Model Context Protocol' are missing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'MCP server development' is a clearly bounded niche with a distinct technical trigger unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor; it is not the generic 'helps with code and documents' that would score 1.	3 / 3
	Total	9 / 12 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: rohitg00/awesome-claude-code-toolkit
Path: skills/mcp-development/SKILL.md
Commit: ebdf1d5

Reviewed: 2 days 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.