mcp-setup

Configure popular MCP servers for enhanced agent capabilities

Quality

36%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/mcp-setup/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.

The description is too vague and lacks both concrete actions and explicit trigger guidance. It mentions the domain (MCP servers) but fails to specify what configuration actions are performed, which servers are supported, or when Claude should select this skill. The phrase 'enhanced agent capabilities' is meaningless fluff that adds no discriminative value.

Suggestions

List specific concrete actions such as 'install, configure, and troubleshoot MCP servers including filesystem, GitHub, Slack, and database servers'.

Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks to set up an MCP server, add a tool server, configure claude_desktop_config.json, or connect Claude to external tools'.

Replace the vague phrase 'enhanced agent capabilities' with specific outcomes like 'to enable file access, API integrations, or database queries'.

Dimension	Reasoning	Score
Specificity	The description is vague — 'configure popular MCP servers' names a domain but doesn't list any concrete actions (e.g., install, set up config files, register endpoints). 'Enhanced agent capabilities' is abstract fluff with no specifics.	1 / 3
Completeness	The 'what' is weak (just 'configure' with no detail), and there is no 'when' clause or explicit trigger guidance at all. The missing 'Use when...' clause would cap this at 2 regardless, but the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	'MCP servers' is a relevant keyword that users might say, but the description lacks common variations or natural trigger terms like 'MCP setup', 'add MCP server', 'tool server configuration', or specific server names.	2 / 3
Distinctiveness Conflict Risk	'MCP servers' provides some specificity that distinguishes it from generic configuration skills, but 'configure' and 'enhanced agent capabilities' are broad enough to potentially overlap with other setup or configuration skills.	2 / 3
	Total	6 / 12 Passed

Implementation

50%

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

The skill provides excellent actionability with concrete, executable commands for each MCP server, but suffers from significant verbosity—the scripted menu flows, completion message templates, and usage tips inflate the token count well beyond what's necessary. The workflow is sequenced but lacks robust error handling/feedback loops during the configuration steps. The content would benefit from splitting into multiple files given its length.

Suggestions

Drastically reduce the completion message template and troubleshooting section—Claude can generate contextually appropriate messages without a full template. Condense to key facts only (e.g., 'Remind user to restart Claude Code; mention `claude mcp list` for verification').

Add explicit error handling after each `claude mcp add` command: check exit code, parse stderr, and retry or report failure before proceeding to the next server.

Split the custom server section and troubleshooting into separate referenced files (e.g., CUSTOM-MCP.md, TROUBLESHOOTING.md) to reduce the main skill's token footprint.

Condense the AskUserQuestion menu scripting—provide the decision tree as a compact table or brief outline rather than spelling out every question and option verbatim.

Dimension	Reasoning	Score
Conciseness	The skill is excessively verbose. The completion message template, usage tips, troubleshooting section, and detailed menu flow descriptions add significant token bloat. Claude already knows how to present completion messages and troubleshooting advice. The multi-step AskUserQuestion flow with exact wording for every menu is overly prescriptive and could be condensed dramatically.	1 / 3
Actionability	The skill provides fully executable, copy-paste-ready bash commands for every MCP server configuration. API key URLs, specific scopes, and concrete command patterns with environment variable flags are all included. The custom server section covers both stdio and HTTP transports with complete command templates.	3 / 3
Workflow Clarity	The steps are clearly sequenced (choose → gather info → add servers → verify → complete), but the verification step is minimal—just `claude mcp list` with no explicit validation of whether tools are actually functional. There's no feedback loop for handling failures during the `claude mcp add` step itself (e.g., what if npx fails, what if the command errors out).	2 / 3
Progressive Disclosure	The content is a monolithic document with no references to external files despite being long enough to benefit from splitting (e.g., the custom server section, troubleshooting, and the detailed menu flow could each be separate files). The structure uses headers well but everything is inline in a single large file.	2 / 3
	Total	8 / 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: Yeachan-Heo/oh-my-claudecode
Commit: 3e94567

Reviewed: 1 day 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.