CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-setup

Configure popular MCP servers for enhanced agent capabilities

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/mcp-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 is highly actionable with executable commands throughout and a clear sequenced workflow including verification. Minor conciseness gains and a slightly stronger validation loop would round it out.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and justified menu staging, but the completion-message block and overlapping troubleshooting/Common Issues sections add minor trimmable padding.

4 / 5

Actionability

Every server path ships copy-paste-ready `claude mcp add` commands with exact flags, env vars, transport options, and user prompts, covering the common cases fully.

5 / 5

Workflow Clarity

A clear five-step sequence (choose, gather, add, verify, complete) with a `claude mcp list` verification checkpoint, though it lacks an explicit validate-fix-retry loop so it stops just short of a 5.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized sections and no nested references, but at ~240 lines with no external reference split it sits at good structure rather than the ideal one-level-deep reference layout.

4 / 5

Total

17

/

20

Passed

Description

41%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.

The description conveys a clear purpose but lacks any trigger guidance and only generic action language, capping both completeness and specificity. Adding a "Use when..." clause with natural user terms would markedly improve it.

Suggestions

Add a "Use when..." trigger clause naming concrete user intents, e.g. "Use when setting up MCP servers like web search, GitHub, or filesystem access in Claude Code."

Expand the action list beyond the generic "Configure" to specific actions such as add, list, verify, and remove MCP servers.

Include natural trigger keywords users actually say (web search, GitHub integration, filesystem access) rather than only the technical term "MCP servers".

DimensionReasoningScore

Specificity

The phrase "Configure popular MCP servers" names the domain and one generic action but offers no comprehensive list of concrete actions, matching the anchor where actions are minimal or generic.

2 / 5

Completeness

It states a clear "what" (configure popular MCP servers for enhanced agent capabilities) but has no "Use when..." trigger clause, so per the guideline a missing trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Only the technical keyword "MCP servers" appears; natural user phrases like web search, GitHub, or filesystem are absent, so it provides one generic keyword missing the natural terms users would say.

2 / 5

Distinctiveness Conflict Risk

"Configure popular MCP servers" carves a clear niche that is mostly distinct from other skills, with only minor overlap risk, though the lack of trigger phrases keeps it just below a 5.

4 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Yeachan-Heo/oh-my-claudecode
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.