CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-mcp-tool

Add a single tool to one of this repo's existing MCP servers (google-docs, google-sheets, google-calendar, google-gmail, google-drive, clickup, slack, etc.). Wires the addTool block into src/<provider>/server.ts using the canonical pattern (Zod params, UserError handling, log.info breadcrumb, getXClient helper), classifies the tool as read or write in e2e/tools.ts, bumps the CLAUDE.md tool count, and optionally chains to /add-e2e-test to scaffold the smoke test. This skill is the single source of truth for the tool shape used across the codebase — use it whenever the user wants to add, create, or wire up a new MCP tool, action, endpoint, or operation, even when phrased indirectly ("expose X to Claude", "I want a tool that does Y"). Also use when invoked as `/add-mcp-tool <toolName> [provider]`.

Quality

95%

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

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

An exemplary procedural skill: concrete, sequenced, validated, and well-factored across its bundle. The only noteworthy defect is a frontmatter/body inconsistency — the description claims the skill 'bumps the CLAUDE.md tool count' while step 8 explicitly says 'Do not bump any tool count — docs/MCP_TOOLS.md is generated and authoritative' — which should be reconciled to avoid misleading execution.

DimensionReasoningScore

Conciseness

The body is almost entirely repo-specific procedure (collision greps, annotation lines, e2e/tools.ts updates) rather than concepts Claude already knows, but a few rationale passages run longer than needed — step 3's multi-sentence read/write justification ('Getting it wrong has runbook consequences... so it's never correct') and step 9's closing paragraph ('Better to handle them deliberately than rush at the tail of adding a tool') could be tightened. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean-everywhere anchor at 5.

4 / 5

Actionability

Fully executable guidance throughout: exact commands ('Grep src/<provider>/server.ts for name: \'<toolName>\'', 'npm run typecheck'), enumerated template placeholders ({{toolName}}, {{zodFields}}, {{executeBody}}), exact annotation lines ('annotations: { readOnlyHint: false, destructiveHint: true },'), a copy-paste report block, and verbatim follow-up offer text. Code generation is anchored to real template files in assets/templates/.

5 / 5

Workflow Clarity

Eleven clearly sequenced steps with explicit validation checkpoints and a feedback loop: step 1 confirms the target file exists, step 2 aborts on name collision, and step 10 runs typecheck with enumerated failure modes and fixes ('Zod schema doesn't match what the execute body destructures'). This matches the anchor with explicit validation steps and error-recovery guidance; checkpoints are explicit, not merely present.

5 / 5

Progressive Disclosure

Clean split confirmed against the actual bundle: SKILL.md is the insertion procedure, the canonical pattern lives in references/tool-pattern.md ('Read references/tool-pattern.md before generating'), and code lives in assets/templates/google-tool.ts.tmpl and third-party-tool.ts.tmpl — all referenced paths exist, and tool-pattern.md itself contains no nested references, so references are exactly one level deep. The File layout section documents the navigation.

5 / 5

Total

19

/

20

Passed

Description

100%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 model description: concrete actions, third-person voice, an explicit use-when clause with direct and indirect trigger phrasings, and a clearly bounded niche within this repo's MCP servers. Its only flaw lies outside the description itself — it states the skill 'bumps the CLAUDE.md tool count', which the body's step 8 contradicts.

DimensionReasoningScore

Specificity

Multiple concrete actions with file-level specificity: 'Wires the addTool block into src/<provider>/server.ts using the canonical pattern (Zod params, UserError handling, log.info breadcrumb, getXClient helper)', 'classifies the tool as read or write in e2e/tools.ts', 'optionally chains to /add-e2e-test'. Coverage spans identification, wiring, classification, and follow-up — no gaps, matching the comprehensive anchor rather than the minor-gaps anchor at 4. Voice is third person throughout ('Wires', 'classifies'); the quoted 'I want a tool that does Y' is an example user utterance, not the skill speaking in first person.

5 / 5

Completeness

Explicitly answers both questions: the 'what' is the concrete wiring pipeline ('Wires the addTool block... classifies the tool... optionally chains to /add-e2e-test'), and the 'when' is explicit with concrete trigger phrases ('use it whenever the user wants to add, create, or wire up a new MCP tool... even when phrased indirectly'). This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage: 'add, create, or wire up a new MCP tool, action, endpoint, or operation, even when phrased indirectly ("expose X to Claude", "I want a tool that does Y")'. It captures synonyms and the indirect phrasings users actually say, so it exceeds the 'good keyword coverage; a few natural terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

Clear niche — adding a single tool to 'one of this repo's existing MCP servers (google-docs, google-sheets, google-calendar, google-gmail, google-drive, clickup, slack, etc.)' — with triggers specific to tool addition. The synonym widening ('action, endpoint, or operation') stays inside the MCP-tool domain, so conflict risk with sibling skills like server scaffolding is minimal, matching the clear-niche anchor.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

boarlabsxyz/awesome-mcp

Path

.claude/skills/add-mcp-tool/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.