mcp

Model Context Protocol server management and tool integration

Quality

26%

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 names the domain (Model Context Protocol) but fails to list specific actions or provide any trigger guidance for when the skill should be used. It needs substantial improvement in specificity, completeness, and trigger term coverage.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about MCP servers, connecting tools via MCP, or configuring Model Context Protocol integrations.'

List specific concrete actions such as 'Start and stop MCP servers, configure tool connections, list available MCP tools, debug MCP server issues.'

Include natural keyword variations users would say: 'MCP', 'MCP server', 'MCP tools', 'Model Context Protocol', 'tool server'.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('management and tool integration') without listing any concrete actions. It does not specify what actions are performed, such as 'start servers', 'configure connections', or 'list available tools'.	1 / 3
Completeness	The description weakly addresses 'what' with vague terms and completely lacks any 'when' guidance or explicit trigger clause. There is no 'Use when...' or equivalent.	1 / 3
Trigger Term Quality	It includes 'Model Context Protocol' and 'MCP' is implied, which are relevant technical terms users might use. However, it lacks common variations like 'MCP', 'MCP server', 'MCP tools', or natural phrases users would say.	2 / 3
Distinctiveness Conflict Risk	'Model Context Protocol' is a fairly specific domain which helps distinguish it, but 'server management and tool integration' is generic enough to potentially overlap with general server management or tool integration skills.	2 / 3
	Total	6 / 12 Passed

Implementation

29%

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

This skill reads as a comprehensive but monolithic API reference dump rather than an actionable skill guide. It lacks workflow sequencing, validation checkpoints, and progressive disclosure—everything is inlined into one long document with no external references. The code examples are structured but their executability is questionable given the unverifiable import paths, and the content would benefit significantly from being split into a concise overview with linked reference files.

Suggestions

Split the content into a concise SKILL.md overview (quick start + common patterns) with links to separate files like API_REFERENCE.md, CLI_REFERENCE.md, and CONFIGURATION.md

Add a clear workflow section showing the typical sequence: configure server → connect → verify connection → discover tools → call tools, with explicit validation at each step

Remove obvious best practices Claude already knows (e.g., 'use env vars for tokens') and trim console.log boilerplate from code examples to improve conciseness

Add error handling examples and recovery patterns (e.g., what to do when connection fails, how to handle tool call timeouts) to make the guidance more actionable

Dimension	Reasoning	Score
Conciseness	The content is reasonably structured but includes some unnecessary verbosity—console.log statements in every example add bulk without teaching anything new, and the best practices section states obvious things Claude already knows (e.g., 'use env vars for tokens'). The popular MCP servers table and some repetitive patterns could be tightened.	2 / 3
Actionability	The TypeScript code examples appear concrete and executable, but they reference a 'clodds/mcp' package that may not be a real/verifiable package, making the examples potentially non-functional. The chat commands and CLI commands are specific but lack context on what tool/environment they apply to. The code is copy-paste shaped but its executability is uncertain.	2 / 3
Workflow Clarity	There is no clear multi-step workflow with sequencing or validation checkpoints. The content is organized as an API reference listing individual operations, but there's no guidance on the typical workflow (e.g., configure → connect → verify → use tools), no error handling patterns, and no validation steps for operations like adding/removing servers.	1 / 3
Progressive Disclosure	This is a monolithic wall of content—a complete API reference inlined into a single SKILL.md with no references to external files. The TypeScript API, CLI commands, chat commands, configuration, and best practices are all crammed together. The API reference section alone should be in a separate file, with SKILL.md serving as a concise overview with navigation links.	1 / 3
	Total	6 / 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: e71a5f6

Reviewed: 11 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.