troubleshooting-guide-creator
Troubleshooting Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: troubleshooting guide creator, troubleshooting guide creator Part of the Technical Documentation skill category.
33
0%
Does it follow best practices?
Impact
94%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/troubleshooting-guide-creator/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title and category label with no substantive content. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and any distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates structured troubleshooting guides with symptom-cause-resolution tables, decision trees, and step-by-step diagnostic workflows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a troubleshooting guide, debug documentation, error resolution steps, diagnostic flowchart, or FAQ for technical issues.'
Remove the duplicate trigger term and expand with natural keyword variations users might say, such as 'troubleshooting doc', 'debug guide', 'fix instructions', 'error handling documentation', 'support runbook'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Technical Documentation') and a label ('Troubleshooting Guide Creator') but does not describe any concrete actions. There are no specific capabilities listed such as 'diagnose errors', 'create step-by-step resolution steps', or 'organize symptoms and solutions'. | 1 / 3 |
Completeness | The description barely addresses 'what' (it's a troubleshooting guide creator) and does not address 'when' at all. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the exact skill name repeated twice ('troubleshooting guide creator'). There are no natural user keywords like 'troubleshooting', 'debug guide', 'fix instructions', 'error resolution', 'diagnostic steps', or 'FAQ'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Technical Documentation' could overlap with many other documentation skills. Without specific actions or distinct triggers, it would be difficult to distinguish this from other documentation or guide-creation skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no substantive content. It contains only meta-descriptions of what the skill would do without any actual instructions, templates, examples, or actionable guidance for creating troubleshooting guides. It fails on every dimension of the rubric.
Suggestions
Add a concrete troubleshooting guide template with sections (e.g., Problem Description, Symptoms, Root Cause Analysis, Resolution Steps, Verification) and a filled-out example.
Provide a step-by-step workflow for creating a troubleshooting guide: gather symptoms → identify root causes → write resolution steps → add verification checks → review for completeness.
Include at least one complete, copy-paste-ready example of a finished troubleshooting guide entry so Claude knows the expected output format.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that describe the skill abstractly and replace them with actionable content that teaches how to create troubleshooting guides.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual troubleshooting guide creation instructions. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no templates, no examples of troubleshooting guide structure, no specific steps Claude should follow. It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section mentions 'step-by-step guidance' but never provides any. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no linked resources, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.