mcp

Model Context Protocol server management and tool integration

Quality

51%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/mcp/SKILL.md

Quality

Discovery

22%

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 description is too vague and abstract to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and natural user keywords. While 'Model Context Protocol' provides some specificity, the rest of the description fails to communicate what the skill actually does or when it should be used.

Suggestions

Add specific concrete actions like 'Start/stop MCP servers, configure server connections, list and invoke MCP tools, troubleshoot connection issues'

Add an explicit 'Use when...' clause with trigger terms like 'MCP', 'context protocol', 'connect server', 'MCP tools', 'server configuration'

Include natural user phrases and variations users might say when needing this skill, such as 'add MCP server', 'MCP not working', 'list tools'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'management' and 'integration' without specifying concrete actions. It doesn't list what specific operations can be performed (e.g., 'start servers', 'configure connections', 'list available tools').	1 / 3
Completeness	The description only vaguely addresses 'what' (management and integration) and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains 'Model Context Protocol' and 'MCP' (implied), 'server', and 'tool' which are relevant technical terms, but misses common user phrases like 'MCP', 'connect to server', 'add tools', or file extensions/protocols users might mention.	2 / 3
Distinctiveness Conflict Risk	'Model Context Protocol' is a specific technology which provides some distinctiveness, but 'server management' and 'tool integration' are generic enough to potentially overlap with other server or tooling skills.	2 / 3
	Total	6 / 12 Passed

Implementation

79%

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

This is a solid API reference with excellent conciseness and actionability - every code example is executable and the content respects Claude's intelligence. However, it functions more as a reference manual than a skill guide, lacking workflow guidance for common tasks and could benefit from better progressive disclosure by splitting into overview + detailed reference files.

Suggestions

Add a 'Getting Started' workflow showing the complete sequence: install server → configure → connect → verify connection → use tools, with explicit validation steps

Split the detailed TypeScript API reference into a separate REFERENCE.md file, keeping SKILL.md focused on quick-start and common patterns with links to details

Add error handling examples and troubleshooting guidance for common failure modes (connection timeouts, authentication failures)

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting commands, code examples, and configuration without unnecessary explanation. It assumes Claude understands MCP concepts and jumps straight to actionable reference material.	3 / 3
Actionability	Provides fully executable TypeScript code examples, complete CLI commands, and copy-paste ready JSON configuration. Every section contains concrete, runnable examples rather than abstract descriptions.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow for common multi-step processes like setting up a new server end-to-end. Missing validation checkpoints for operations like testing server connections before use.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic reference document. Could benefit from splitting detailed API reference into separate files while keeping SKILL.md as a quick-start overview with links.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

Reviewed: 28 days ago

Table of Contents

Discovery Implementation Validation

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.