SKILLEMALL.ai
GitHub ↗ RU Sign in

CD mcp-integration-reference

Template for skills that integrate with an MCP server. Demonstrates the reference file pattern: Claude reads a domain-specific MCP cheatsheet before making any tool calls, reducing query failures caused by server-specific gotchas. Fork this skill and replace the Sentry example with your target MCP.

FlorianBruniaux/claude-code-ultimate-guide Agent Skills author: FlorianBruniaux CC-BY-SA-4.0 2 files body ≈ 1 019 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Template for skills that integrate with an MCP server.

As a process D 36/100 · Unfinished process — References files that are not bundled: references/<mcp-name>.md, references/<your-mcp>.md

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
D
36/100
Unfinished process
References files that are not bundled: references/<mcp-name>.md, references/<your-mcp>.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/<mcp-name>.md
  • warning missing-ref reference to a missing file: references/<your-mcp>.md
  • note frontmatter-key unknown frontmatter key "effort"

Process rating: all ten parameters 36/100

Will not run. References files that are not bundled: references/<mcp-name>.md, references/<your-mcp>.md
  • 0Tools and files. 2 referenced file(s) missing: references/<mcp-name>.md, references/<your-mcp>.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 85Steps. 24 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1019 tokens
  • low The response is described with custom markup (3 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 299: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 24 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.