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.
35
3%
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
7%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 extremely thin—it essentially restates the skill's name and category without describing any concrete capabilities or providing meaningful trigger guidance. It lacks specific actions, natural user keywords, and an explicit 'Use when…' clause, making it nearly useless for skill selection among multiple options.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates step-by-step installation guides including prerequisites, dependency lists, platform-specific instructions, and troubleshooting sections.'
Add an explicit 'Use when…' clause with natural trigger terms, e.g., 'Use when the user asks for install instructions, setup guides, deployment steps, getting started documentation, or README installation sections.'
Remove the redundant duplicate trigger term and instead diversify with synonyms and variations users would naturally use, such as 'setup guide', 'install docs', 'deployment instructions', 'onboarding 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 'generates step-by-step install instructions, creates dependency lists, documents prerequisites.' It is entirely abstract. | 1 / 3 |
Completeness | The 'what' is barely stated (just the name) and there is no explicit 'when' clause. The 'Triggers on' line merely repeats the skill name and provides no meaningful guidance on when Claude should select this skill. | 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 'installation guide' does narrow the domain somewhat compared to generic 'technical documentation,' but without specific actions or file types it could overlap with other documentation or README-generation skills. | 2 / 3 |
Total | 5 / 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 substantive content. It consists entirely of self-referential meta-descriptions ('this skill provides assistance for installation guide creator') without any actual guidance, templates, examples, or actionable instructions for creating installation guides. It fails on every dimension of the rubric.
Suggestions
Add a concrete installation guide template with sections (prerequisites, system requirements, installation steps, verification, troubleshooting) that Claude can use as a starting framework.
Include at least one complete example of a generated installation guide for a specific type of software (e.g., CLI tool, web application, library) with executable verification commands.
Define a clear workflow: 1) Gather requirements from user, 2) Determine installation type, 3) Generate guide using template, 4) Validate completeness against a checklist of required sections.
Add concrete formatting rules and best practices specific to installation guides (e.g., always include OS-specific instructions, always add a verification step after each major installation action).
| 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 installation guide creation guidance. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no templates, no specific commands, no actual instructions for creating installation guides. It only describes itself in abstract terms. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The 'step-by-step guidance' mentioned in capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no references to detailed materials, no links to examples or templates, and no meaningful structural organization of actual 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.