CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-builder

MCP 服务器构建方法论 — 系统化构建生产级 MCP 工具,让 AI 助手连接外部能力

52

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/mcp-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 content is a comprehensive, well-structured, code-rich methodology with strong actionability and clear sequencing, though it is monolithic with no progressive disclosure to separate reference files.

Suggestions

Move the detailed deployment/packaging recipes (npm, pip, Docker) and the extended debugging table into separate reference files linked from SKILL.md to improve progressive disclosure.

Add an explicit validate-then-retry feedback loop for destructive/batch tool operations (e.g., confirm → execute → verify result → rollback on failure) to lift workflow clarity.

Tighten the three-primitive definitions in section 1 to assume MCP familiarity, keeping only the selection-principle guidance.

DimensionReasoningScore

Conciseness

The body is dense and code-heavy with tight sections; it mostly assumes Claude's competence and avoids padding, with only minor over-explanation (e.g., the three-primitive definitions) that could be trimmed.

4 / 5

Actionability

It provides mostly executable, copy-paste-ready TypeScript/Python examples for registration, validation, testing, and deployment, with only minor gaps (a few `/* ... */` handler placeholders).

4 / 5

Workflow Clarity

Numbered sections, an explicit lifecycle order ('先初始化 → 再 connect → 监听关闭信号'), a debugging flow, and a build checklist provide clear sequencing and validation checkpoints; not a 5 because destructive/batch operations lack a single explicit validate-then-retry feedback loop.

4 / 5

Progressive Disclosure

The skill is well-organized into 10 clear sections but is a monolithic ~250-line single file with no bundle files or external references; content that could live in separate files (full deployment guides, extended examples) is inlined, so it does not reach a 4.

3 / 5

Total

15

/

20

Passed

Description

48%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 clearly identifies a distinct niche (MCP server building) and states what the skill does, but it is written in abstract methodology language with no 'Use when' trigger guidance and only generic actions, limiting its specificity and completeness.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building or deploying an MCP server, defining tools/resources/prompts, or wiring an AI assistant to external systems.'

Replace abstract phrasing ('系统化构建方法论') with concrete actions the skill performs (design tools, register resources, validate inputs, package for npm/pip).

Include natural trigger synonyms users would say ('MCP server', 'Model Context Protocol', 'MCP tool') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('MCP 服务器构建方法论') and a generic action ('系统化构建生产级 MCP 工具'), but the actions are minimal and abstract rather than concrete; it does not reach the '1-2 concrete actions' clarity of a 3.

2 / 5

Completeness

It clearly states what the skill does (systematically build production-grade MCP tools) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

It includes relevant keywords ('MCP 服务器', 'MCP 工具', 'AI 助手') that a user building MCP servers would say, but lacks common variations/synonyms and has no natural user-facing trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

'MCP 服务器构建' is a clear, narrow niche with distinct triggers and minimal overlap with other skills, though the absence of explicit trigger phrases keeps it just below a 5.

4 / 5

Total

12

/

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.