CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-tools-setup

Set up, connect, validate, and repair Claude Desktop and MCP servers using Desktop Commander — inspecting and fixing mcp.json / claude_desktop_config.json, getting MCP servers to connect, and diagnosing local AI tooling. Use when a user wants to install, configure, connect, validate, or fix Claude Desktop, an MCP server, an MCP config file, or a local AI agent/gateway. Trigger on the symptoms that actually bring people in: "Claude can't see my tools", "my MCP server isn't showing up", "tools aren't loading in Claude", "add an MCP server", "my MCP isn't connecting", "fix my Claude Desktop config", "the agent won't respond", "wire up Ollama / LM Studio", "restart Claude Desktop". Also covers local agent gateways like OpenClaw and Hermes.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable skill body that routes cleanly to one-level-deep references and bakes verification into every workflow. The main opportunity is tightening a few prose-heavy golden rules and inlining one or two exact command strings.

Suggestions

Tighten the longer golden rules (e.g. rules 2 and 6) to imperative one-liners so each rule earns its token budget with no explanatory padding.

Inline the exact provider test command (e.g. a sample curl with the auth header) rather than only describing "a quick curl to the provider", so the early auth check is copy-paste ready.

Show one concrete example of the backup-then-edit_block-then-validate JSON loop as a short sequence so the core repair pattern is fully executable from the body.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence (no explaining what an MCP server or config file is), with domain-specific rationale rather than generic padding; a few golden-rule sentences could be tightened slightly.

4 / 5

Actionability

Names concrete Desktop Commander tools and shell commands (get_config, start_process, cp ... .bak, list_processes, lsof/netstat, edit_block) with mostly executable guidance; minor gaps where exact command strings (e.g. the provider curl test) are only described, deferred to the reference files.

4 / 5

Workflow Clarity

Clear 6-step general workflow plus explicit validation checkpoints ("Verify, then stop" with list_processes/lsof, "Validate the JSON after every edit") and a backup-edit-validate feedback loop for destructive config changes; the diagnostic is a well-ordered checklist.

5 / 5

Progressive Disclosure

SKILL.md is a tight overview routing to three clearly signaled one-level-deep references (→ Read references/X.md); verified the bundle files contain no further nested .md links, so content is appropriately split with easy navigation.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete actions, natural trigger phrases, explicit what-and-when guidance, and a clearly bounded niche with named tools. Written in third person with no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Set up, connect, validate, and repair", "inspecting and fixing mcp.json / claude_desktop_config.json", "getting MCP servers to connect", "diagnosing local AI tooling" — covering the domain comprehensively.

5 / 5

Completeness

Explicitly answers both what ("Set up, connect, validate, and repair...") and when ("Use when a user wants to...", "Trigger on the symptoms that actually bring people in...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users actually say ("Claude can't see my tools", "my MCP server isn't showing up", "fix my Claude Desktop config") plus config file names and named tools (Ollama, LM Studio, OpenClaw, Hermes).

5 / 5

Distinctiveness Conflict Risk

Clear niche (Claude Desktop / MCP servers / local AI tooling) with named tools and distinct symptom-based triggers; minimal overlap risk with unrelated skills.

5 / 5

Total

20

/

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
wonderwhy-er/DesktopCommanderMCP
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.