CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-integration

This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable skill with excellent concrete examples and verified one-level-deep references, but it is verbose and somewhat redundant across sections. Tightening inline duplication and interleaving validation checkpoints in the workflow would raise the two middle dimensions.

Suggestions

Collapse the duplicated auth/HTTPS/env-var guidance that recurs across 'MCP Server Types', 'Authentication Patterns', and 'Best Practices' into the references, leaving SKILL.md a lean overview to lift conciseness toward 3.

Add explicit validation checkpoints between Implementation Workflow steps (e.g. 'After configuring .mcp.json, run /mcp and confirm the server appears before pre-allowing tools') to move workflow_clarity to 3.

Move the per-server-type JSON examples and deep auth detail into references/server-types.md and references/authentication.md, keeping only one example per type inline, to strengthen progressive_disclosure.

DimensionReasoningScore

Conciseness

The body runs ~550 lines and repeats material across 'MCP Server Types', 'Authentication Patterns', and the closing 'Best Practices'/'Quick Reference' sections (e.g. HTTPS/WSS, env-var documentation, and OAuth appear multiple times), so it is mostly efficient but could be tightened — not a full 3.

2 / 3

Actionability

It provides concrete, copy-paste-ready JSON configs for every server type, real commands (`claude --debug`, `/mcp`), explicit allowed-tools frontmatter snippets, and worked integration patterns, meeting the level-3 'fully executable' anchor.

3 / 3

Workflow Clarity

The 'Implementation Workflow' lists a clear 1–9 sequence and there are checklists, but validation checkpoints are not interleaved between steps — the checklist sits at the end rather than gating each step — so the feedback-loop anchor for level 3 is not fully met.

2 / 3

Progressive Disclosure

References are real and well-signaled at one level deep (server-types.md, authentication.md, tool-usage.md all exist), but the SKILL.md itself is a ~550-line monolith that duplicates much of what the reference files cover, so content that should be separate remains inline — a 2 rather than a 3.

2 / 3

Total

9

/

12

Passed

Description

90%

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 strong, well-structured description with explicit trigger guidance and a clearly delineated niche. The only weakness is the slightly generic action summary ('Provides comprehensive guidance') in place of enumerated concrete actions.

Suggestions

Replace 'Provides comprehensive guidance for integrating...' with 2–3 concrete actions (e.g. 'Configure .mcp.json server entries, wire OAuth/token authentication, and pre-allow MCP tools in commands') to lift specificity to 3.

DimensionReasoningScore

Specificity

It names the domain ('integrating Model Context Protocol servers into Claude Code plugins') and lists concrete server types, but the action summary is the abstract phrase 'Provides comprehensive guidance' rather than multiple discrete concrete actions, so it is not a full 3.

2 / 3

Completeness

It explicitly answers both 'what does this do' ('Provides comprehensive guidance for integrating Model Context Protocol servers...') and 'when should Claude use it' via an explicit 'should be used when the user asks to...' trigger clause, satisfying the level-3 anchor.

3 / 3

Trigger Term Quality

It covers natural phrases a user would actually say — 'add MCP server', 'integrate MCP', 'use .mcp.json', 'set up Model Context Protocol', 'connect external service' — plus concrete server-type keywords (SSE, stdio, HTTP, WebSocket), giving strong natural coverage.

3 / 3

Distinctiveness Conflict Risk

The trigger set is tightly scoped to MCP integration within Claude Code plugins (including the ${CLAUDE_PLUGIN_ROOT} cue), defining a clear niche that is unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (555 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
Galaxy-Dawn/claude-scholar
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.