CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagnose

Interactive troubleshooting assistant for Claude Code issues

56

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./examples/skills/diagnose/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 skill body is a strong, actionable diagnostic workflow: concrete commands, fallback paths, symptom-cause-example patterns, and a structured output format. The main gaps are minor — a missing validation step for the fetched knowledge base and some content that could live in separate reference files.

DimensionReasoningScore

Conciseness

The body is procedural and lean — commands, category lists, patterns, and worked examples with almost no explanation of concepts Claude already knows. Minor trim opportunities: the opening line repeats the frontmatter description and the "You are an expert diagnostic assistant..." preamble is mild padding.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready curl and jq commands, a script fallback with manual checks, and two complete worked examples (pnpm permission mismatch, hooks not triggering) that cover common failure modes.

5 / 5

Workflow Clarity

Six clearly sequenced steps with a fallback path ("If the script fails, fall back to manual checks") and ambiguity checkpoints ("Ask targeted follow-up questions if the cause is ambiguous"), though there is no validation that the fetched guide actually loaded (e.g., confirming Section 10.4 exists).

4 / 5

Progressive Disclosure

Well-organized sections (Instructions, Patterns, Examples) with the external guide reference clearly signaled at one level deep and no nested references; the inline patterns and examples could partially be offloaded but are modest in size.

4 / 5

Total

17

/

20

Passed

Description

45%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 identifies the domain but relies on a single generic action verb with no trigger guidance. It reads more like a title than a capability description, leaving both completeness and trigger coverage weak.

Suggestions

Add concrete actions to the description, e.g., "Diagnoses Claude Code issues by scanning settings and MCP configuration, correlating symptoms, and prescribing step-by-step fixes."

Append explicit trigger guidance in the description, e.g., "Use when Claude Code shows errors, crashes, or unexpected behavior."

Include natural trigger terms users would say, such as "not working", "error", "fix", or "configuration problem", to improve trigger matching.

DimensionReasoningScore

Specificity

The description names the domain ("Claude Code issues") but the only action, "troubleshooting", is generic — no concrete actions like scanning configuration, diagnosing, or prescribing fixes are stated.

2 / 5

Completeness

There is a clear "what" (interactive troubleshooting assistant for Claude Code issues) but the description field contains no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Claude Code", "troubleshooting", and "issues" are relevant keywords, but natural phrases users would actually say ("error", "not working", "fix", "crashes") are missing.

3 / 5

Distinctiveness Conflict Risk

Scoped to Claude Code, but "troubleshooting" is broad enough to overlap with related skills such as update-config or security-review; somewhat specific yet not clearly distinct.

3 / 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.

Validation — 15 / 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

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/diagnose/SKILL.md

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.