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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill mcp-management81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its specialized domain (MCP servers) and provides explicit trigger conditions. The description effectively covers both what the skill does and when to use it, with good trigger term coverage for the MCP ecosystem. The main weakness is that the capability verbs (manage, discover, analyze) could be more concrete about specific actions.
Suggestions
Replace generic verbs like 'manage' and 'analyze' with more specific actions (e.g., 'list available tools', 'inspect server capabilities', 'debug connection issues')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MCP servers) and lists several actions (discover, analyze, execute tools/prompts/resources), but the actions are somewhat generic and could be more concrete about what 'manage' and 'analyze' specifically entail. | 2 / 3 |
Completeness | Clearly 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, server configuration, tool execution errors). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural terms: 'MCP servers', 'MCP integrations', 'capability discovery', 'tool filtering', 'programmatic execution', 'context bloat', 'server configuration', 'tool execution errors' - these are terms users working with MCP would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | MCP servers is a very specific niche with distinct terminology (MCP integrations, context bloat, tool execution errors). Unlikely to conflict with other skills due to the specialized domain. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid actionable guidance with executable commands and clear tool execution patterns. However, it suffers from some redundancy across sections and lacks validation/error handling workflows. The content could be more concise by eliminating repeated examples and consolidating overlapping sections.
Suggestions
Add validation steps after tool execution (e.g., 'Verify output: check for error field in JSON response')
Consolidate Quick Start, Implementation Patterns, and Integration Strategy sections to eliminate redundancy
Remove duplicate bun/bunx alternatives - show one preferred method with a note about alternatives
Add error handling guidance: what to do when Gemini CLI fails, when tool execution returns errors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary explanation (e.g., 'MCP is an open protocol enabling AI agents...') and repetitive content (bun vs bunx alternatives shown multiple times). The 'Key Benefits' and 'When to Use' sections add moderate value but could be trimmed. | 2 / 3 |
Actionability | Provides concrete, executable commands throughout - actual CLI invocations, specific file paths, and copy-paste ready examples. Commands like 'bunx tsx scripts/cli.ts list-tools' and 'gemini -y -m gemini-2.5-flash -p "..."' are immediately usable. | 3 / 3 |
Workflow Clarity | Presents clear execution priority (Gemini CLI → Direct Scripts → Subagent) but lacks validation checkpoints. No guidance on verifying tool execution success, handling errors, or confirming results before proceeding. | 2 / 3 |
Progressive Disclosure | References external files (assets/tools.json, .claude/.mcp.json) appropriately, but the document itself is somewhat monolithic with overlapping sections (Quick Start, Implementation Patterns, Integration Strategy all cover similar ground). Could better organize into overview + detailed references. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.