CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-troubleshooting

Diagnose and fix MCP configuration/runtime issues across supported integrations using agents CLI checks.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

93%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 content is concise, highly actionable, and well-structured with concrete commands and a clear sequence. Its only gap is the absence of an explicit retry/feedback loop after the verification step.

Suggestions

Add an explicit feedback loop after the verify step, e.g. 'If agents sync --check still reports issues, return to step 2 and re-diagnose.'

Optionally clarify how to interpret each command's output so Claude knows which result points to which troubleshooting priority.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or over-explanation; every line delivers a concrete command or actionable priority, respecting the token budget.

5 / 5

Actionability

Each step is a fully executable, copy-paste-ready command ('agents status --fast', 'agents mcp test --runtime', 'agents doctor', 'agents sync --check') covering the common diagnostic cases.

5 / 5

Workflow Clarity

A clear 5-step sequence with an explicit verification step ('verify with agents sync --check'), but it lacks an explicit retry/feedback loop describing what to do if verification fails.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, and well-organized into a numbered workflow plus a priorities list, with no need for external references, which qualifies for a top score per the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

61%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 clearly communicates the skill's purpose and niche but omits an explicit 'when to use' trigger clause, which caps completeness. It is concise and uses natural terminology, though synonym coverage is incomplete.

Suggestions

Add a 'Use when ...' clause with concrete trigger phrases (e.g., 'Use when MCP servers fail, are missing, or not visible, or when integrations show errors').

Broaden trigger term coverage with natural synonyms users say, such as 'MCP server', 'MCP connection', or 'integration not loading'.

Consider listing a couple more specific actions (e.g., 'inspect integration status', 'validate runtime connectivity') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('MCP configuration/runtime issues across supported integrations') and 1-2 concrete actions ('Diagnose and fix' via 'agents CLI checks'), but does not enumerate multiple specific actions for comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' but lacks any 'Use when...' or equivalent trigger clause, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('MCP', 'configuration', 'runtime issues', 'integrations') with good coverage, though common synonyms like 'MCP server' or 'MCP not connecting' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (MCP troubleshooting via agents CLI) that is mostly distinct from other skills, with only minor overlap risk against closely related diagnostics skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JoseMD12/finance-hub
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.