troubleshooting-guide-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill troubleshooting-guide-creatorTroubleshooting Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: troubleshooting guide creator, troubleshooting guide creator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it actually does or when to use it. It lacks any concrete actions, meaningful trigger terms, or explicit usage guidance. The description would fail to help Claude distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates structured troubleshooting guides with symptom identification, diagnostic steps, root cause analysis, and resolution procedures'
Include a 'Use when...' clause with natural trigger terms like 'troubleshooting documentation', 'debug guide', 'error resolution steps', 'support docs', 'problem diagnosis', 'fix instructions'
Specify the types of troubleshooting guides supported (software errors, hardware issues, configuration problems) to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Troubleshooting Guide Creator') without describing any concrete actions. There are no specific capabilities listed like 'diagnose errors', 'create step-by-step solutions', or 'document common issues'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and the 'when' clause is just a circular reference to the skill name. There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the exact skill name repeated twice ('troubleshooting guide creator'). This misses natural variations users would say like 'debug guide', 'error documentation', 'fix instructions', 'problem-solving docs', or 'support documentation'. | 1 / 3 |
Distinctiveness Conflict Risk | Being in the 'Technical Documentation' category provides some context, and 'troubleshooting' is a somewhat specific domain. However, without concrete actions described, it could overlap with general documentation or support skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template that provides no actual guidance for creating troubleshooting guides. It consists entirely of meta-description about what the skill supposedly does without any actionable content, concrete examples, or workflows. The skill would need to be completely rewritten with actual troubleshooting guide creation instructions.
Suggestions
Add a concrete troubleshooting guide template with sections like 'Problem Description', 'Symptoms', 'Diagnostic Steps', 'Solutions', and 'Prevention'
Include at least one complete example of a troubleshooting guide entry showing the expected format and level of detail
Provide a step-by-step workflow for gathering information and structuring a troubleshooting guide (e.g., 1. Identify common issues, 2. Document symptoms, 3. Create decision trees, 4. Validate with users)
Remove all generic boilerplate text about 'automated assistance' and 'best practices' - replace with specific, actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'automated assistance' and 'industry best practices' are vague filler that Claude doesn't need explained. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no examples of actual troubleshooting guide structure or content. The skill describes what it does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for creating a troubleshooting guide, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no actual substance to organize. There are no references to detailed materials, templates, or examples that would help with the task. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.