CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-builder

Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.

68

Quality

81%

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

93%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 tight, highly actionable skill body with concrete commands and a sequenced workflow including validation, needing only an explicit error-retry loop to perfect workflow clarity.

DimensionReasoningScore

Conciseness

Lean imperatives with no padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Concrete copy-paste commands (`codewhale mcp add ... --url ...`), a specific config path, and an explicit `Accept` header value cover the common cases fully.

5 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation gate (`codewhale mcp validate`, then `codewhale mcp tools`) and a happy/failure-path testing step; just missing an explicit fix-and-retry loop to reach 5.

4 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and well-organized into clear sections, so the simple-skill exception allows a 5.

5 / 5

Total

19

/

20

Passed

Description

70%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.

A concise, specific description of the MCP-building domain with strong trigger terms and clear distinctiveness, weakened only by the absence of an explicit "Use when..." clause.

Suggestions

Append an explicit trigger clause such as "Use when the user asks to create, configure, or debug an MCP server or tool integration for codewhale." to raise completeness.

Add a couple of natural synonyms or phrasings users might say (e.g. "MCP tool", "tool integration") to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists four concrete actions ("Design, build, configure, or debug") over a named domain plus transport specifics (stdio, HTTP/SSE), placing it at several-specific-actions with minor coverage gaps rather than a comprehensive action set.

4 / 5

Completeness

The "what" is clear, but there is no explicit "Use when..." trigger clause, so per the rubric guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "MCP server", "configure", "debug", "stdio", and "HTTP/SSE" would be said by users, giving good keyword coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to "Model Context Protocol servers for codewhale" with named transports, giving a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Hmbown/Codewhale
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.