CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-builder

在构建 MCP 服务器或 MCP 工具时使用 —— 系统化的生产级 MCP 构建方法论,覆盖工具设计、错误处理、传输层选择与测试,让 AI 助手连接外部能力

67

Quality

83%

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

78%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 comprehensive, highly actionable MCP-building methodology with executable code, checklists, and debugging feedback loops. Its main weakness is progressive disclosure: everything lives in one long inline document with no references or supporting files.

Suggestions

Split detailed reference material (deployment configs, the security section, the debugging symptom/cause/fix table) into files under references/ and link to them from the body so SKILL.md reads as an overview.

Refactor the topical sections (design, implement, test, deploy) into one explicit gated build workflow with validation checkpoints between phases.

Trim rationale sentences that restate why a practice matters, keeping only the directive, to tighten the token budget toward a 5 on conciseness.

DimensionReasoningScore

Conciseness

The body is dense and mostly actionable with little padding of concepts Claude already knows, though brief rationale sentences (e.g. 'AI 助手靠名称选工具,模糊命名导致误调用') could be trimmed for a leaner token budget.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript and Python code plus concrete commands (`npx @modelcontextprotocol/inspector`) and config snippets (npm bin, Dockerfile, pip scripts) covering the common MCP build cases.

5 / 5

Workflow Clarity

Sequenced workflows with checkpoints appear (lifecycle '先初始化 → 再 connect → 监听关闭信号', debugging flow with a feedback loop, and a build checklist), but the overall design→deploy flow is organized topically rather than as one gated, validated sequence, leaving minor validation gaps.

4 / 5

Progressive Disclosure

The ~250-line body is well-structured with clear numbered sections but is entirely monolithic with no bundle files and no references signaling deeper materials, despite content (full deployment configs, security, debugging reference) that could be split out.

3 / 5

Total

16

/

20

Passed

Description

87%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 cleanly states both purpose and trigger condition with concrete, domain-specific terms and minimal conflict risk. It is strong overall, with only minor gaps in action-verb specificity and trigger-term synonyms.

DimensionReasoningScore

Specificity

Names the MCP domain and several concrete coverage areas ('工具设计、错误处理、传输层选择与测试') rather than vague language, but lists topical sub-domains instead of action verbs and omits areas the body covers (security, deployment, debugging), leaving minor gaps.

4 / 5

Completeness

Explicitly answers both 'what' ('系统化的生产级 MCP 构建方法论,覆盖...') and 'when' ('在构建 MCP 服务器或 MCP 工具时使用') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural trigger phrases ('构建 MCP 服务器', 'MCP 工具') a user would say, but misses common variations such as 'develop/create', the full 'Model Context Protocol' name, and 'set up'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (building MCP servers/tools) with distinct triggers, making overlap with other skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.