installation-guide-creator
Installation Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: installation guide creator, installation guide creator Part of the Technical Documentation skill category.
33
0%
Does it follow best practices?
Impact
94%
1.01xAverage 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/installation-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 detail that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates step-by-step installation guides including prerequisites, platform-specific instructions, dependency lists, and troubleshooting sections.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for installation instructions, setup guides, install steps, deployment documentation, getting started guides, or onboarding docs.'
Remove the duplicate trigger term ('installation guide creator' is listed twice) and replace with varied natural phrases users would actually say, such as 'install docs', 'setup tutorial', 'how to install', 'deployment steps'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Installation Guide Creator') and its category ('Technical Documentation') but lists no concrete actions like 'generate step-by-step install instructions', 'create dependency lists', or 'produce platform-specific setup guides'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions) and 'when should Claude use it' (no 'Use when...' clause or equivalent explicit trigger guidance). It is essentially a label with no substance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('installation guide creator'). There are no natural user phrases like 'setup instructions', 'install steps', 'how to install', 'deployment guide', or 'getting started guide'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'Technical Documentation' is extremely broad and could overlap with any documentation-related skill. Without specific actions or file types, there is nothing to distinguish this from a general docs skill, a README generator, an API reference writer, etc. | 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 an empty shell with no actual content. It consists entirely of generic boilerplate describing what the skill would do without providing any actual guidance, templates, examples, or instructions for creating installation guides. It adds zero value beyond what Claude already knows.
Suggestions
Add a concrete installation guide template with sections (prerequisites, system requirements, installation steps, verification, troubleshooting) and example content for each section.
Include at least one complete, copy-paste-ready example of a generated installation guide for a specific technology (e.g., a Python package or a CLI tool).
Define a clear workflow: 1. Gather requirements from user, 2. Determine target platforms, 3. Draft guide using template, 4. Validate completeness against checklist, 5. Output final guide.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content like formatting conventions, common pitfalls, and platform-specific patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains nothing Claude doesn't already know and provides zero actual guidance on creating installation guides. Every section is generic boilerplate that could apply to any skill. | 1 / 3 |
Actionability | There are no concrete steps, code examples, templates, commands, or specific instructions for creating installation guides. The content only describes what the skill supposedly does in vague, abstract terms without any executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed materials, and no navigation structure. The sections are just meta-descriptions of the skill rather than actual instructional 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
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.