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 placeholder that provides no meaningful information beyond the skill's name. It lacks concrete actions, natural trigger terms, explicit usage 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 descriptions, diagnostic steps, root cause analysis, and resolution procedures.'
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 replace with varied natural language terms 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 fails to clearly answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name and does not provide meaningful 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 nearly impossible to distinguish this from other documentation-related 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 it claims to do without any actual instructions, templates, examples, or concrete guidance for creating troubleshooting guides. It provides zero value to Claude beyond what the skill's title already conveys.
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.
Include a step-by-step workflow for creating a troubleshooting guide: gather symptoms → identify root causes → write resolution steps → add verification checks → review for completeness.
Provide at least one complete, copy-paste-ready example of a troubleshooting guide entry (e.g., for a common API error like 401 Unauthorized).
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that describe the skill itself rather than teaching how to perform the task.
| 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 templates, no code, no commands, no examples of actual troubleshooting guide structure or content. It only describes itself rather than instructing Claude on how to create troubleshooting guides. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims like 'provides step-by-step guidance' without actually providing 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 meaningful structural organization beyond boilerplate headings. | 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
b8a3b3e
- 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.