CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mcp-management

Manage MCP servers - discover, analyze, execute tools/prompts/resources. Use for MCP integrations, capability discovery, tool filtering, programmatic execution, or encountering context bloat, server configuration, tool execution errors.

55

Quality

69%

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 ./plugins/mcp-management/skills/mcp-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 body provides concrete commands but is undermined by heavy duplication (identical bun/bunx blocks, thrice-repeated execution-priority guidance), a redundant MCP concept explainer, placeholder JSON arguments, and an unexplained subagent fallback. Referenced bundle files (scripts/cli.ts, assets/tools.json) are absent from the package, leaving navigation dangling.

Suggestions

Deduplicate the content: collapse the identical "Preferred: Using bun" / "Alternative: Using bunx" pairs, remove the "bun install # or: bun install" self-duplicate, and merge the Patterns, Quick Start, and Integration Strategy sections into one execution-priority workflow.

Make the guidance fully executable: replace the '{"entities":[...]}" placeholder with a complete JSON example, and give concrete dispatch instructions for the "mcp-manager Subagent" fallback (the command/prompt to launch it and what to tell it), which is currently a bare heading.

Fix progressive disclosure: either include the referenced scripts/cli.ts and assets/tools.json in the bundle or remove/correct the references, and cut the "MCP is an open protocol..." explanation plus the Overview benefits list that Claude can infer.

DimensionReasoningScore

Conciseness

"MCP is an open protocol enabling AI agents to connect to external tools and data sources" explains a concept Claude already knows, the "Preferred: Using bun" and "Alternative: Using bunx" code blocks are byte-identical duplicates repeated twice, "bun install # or: bun install" is a self-duplicate, and Quick Start restates the Patterns and Integration Strategy sections verbatim — several padded and duplicated sections, matching anchor 2 rather than anchor 3's 'some' unnecessary explanation.

2 / 5

Actionability

Commands like "bunx tsx scripts/cli.ts list-tools" and "gemini -y -m gemini-2.5-flash -p \"Take a screenshot of https://example.com\"" are concrete, but arguments such as '{"entities":[...]}' are placeholders and the "Fallback: mcp-manager Subagent" section is a bare heading with no dispatch instructions despite being referenced throughout — incomplete executable guidance that falls below anchor 4's 'minor gaps'.

3 / 5

Workflow Clarity

The Execution Priority section does give a sequence with an availability checkpoint ("Check: command -v gemini"), but no validation of execution results exists and the same priority sequence is restated in three redundant sections, matching anchor 3's 'sequence present but checkpoints missing' rather than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The body has section headers and points to "scripts/cli.ts", "assets/tools.json", and "cd .claude/skills/mcp-management/scripts", but no bundle files (scripts/, assets/, references/) actually exist in the skill package, so references are not clearly signaled and dangle — some structure with organization gaps, matching anchor 3.

3 / 5

Total

11

/

20

Passed

Description

83%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 strong description that clearly states what the skill does and when to use it, with a solid set of natural trigger terms. Its main weakness is slightly incomplete action coverage (the generic "Manage") and a few trigger terms (context bloat, server configuration) that risk overlap with adjacent skills.

DimensionReasoningScore

Specificity

"discover, analyze, execute tools/prompts/resources" names the MCP domain and several concrete actions, but the generic verb "Manage" and unmentioned capabilities (config management, tool catalog persistence) leave minor coverage gaps, matching anchor 4 rather than the comprehensive coverage of 5.

4 / 5

Completeness

It explicitly answers both what ("Manage MCP servers - discover, analyze, execute tools/prompts/resources") and when ("Use for MCP integrations, capability discovery, tool filtering, programmatic execution, or encountering context bloat...") with concrete trigger phrases, matching the anchor-5 example structure; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural phrases like "MCP integrations", "tool filtering", "context bloat", "server configuration", and "tool execution errors" give good keyword coverage, but "Model Context Protocol" is never spelled out and common variants are missing, so it sits between anchors 4 and 5 but not at full coverage.

4 / 5

Distinctiveness Conflict Risk

The MCP niche is clear with distinct triggers, though "context bloat" and "server configuration" could pull in general context-management or config skills, giving minor overlap risk consistent with anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

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: 13 missing

Warning

Total

14

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/mcp-management/skills/mcp-management/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.