installation-guide-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill installation-guide-creatorInstallation Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: installation guide creator, installation 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 essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining what the skill actually does or when Claude should choose it. The redundant trigger terms and lack of concrete actions make this description ineffective for distinguishing this skill from others.
Suggestions
Add specific actions the skill performs, e.g., 'Creates step-by-step installation guides with prerequisites, system requirements, dependency lists, and troubleshooting sections'
Include a 'Use when...' clause with natural trigger terms like 'setup instructions', 'install documentation', 'getting started guide', 'deployment steps', 'how to install'
Specify the types of software/projects this applies to (e.g., 'for software packages, libraries, applications, or developer tools')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Installation Guide Creator') without describing any concrete actions. There are no specific capabilities listed like 'writes step-by-step instructions', 'generates dependency lists', or 'creates troubleshooting sections'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('installation guide creator' repeated twice) and overly specific to the exact skill name. Missing natural variations users would say like 'setup instructions', 'install docs', 'how to install', 'getting started guide'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'installation guide' is somewhat specific to a documentation type, the lack of detail means it could overlap with general documentation skills. The category mention ('Technical Documentation') provides some context but doesn't clearly distinguish it. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about creating installation guides. It contains only generic boilerplate text that could apply to any skill, with no specific guidance, examples, templates, or workflows for installation documentation. The skill fails to teach Claude anything actionable.
Suggestions
Add a concrete installation guide template with sections (prerequisites, steps, verification, troubleshooting) and example content
Include executable examples showing how to generate installation commands for different platforms (Linux, macOS, Windows)
Define a clear workflow: 1) Identify prerequisites, 2) Write step-by-step instructions, 3) Add verification commands, 4) Include troubleshooting section
Remove all generic boilerplate ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual installation guide patterns and examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about installation guide creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no examples of installation guide structure, no templates, no specific commands or code. The content describes rather than instructs, with vague statements like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating an installation guide, no validation checkpoints, and no process to follow. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, templates, or examples. The content is a shallow placeholder with no depth or navigation to additional resources. | 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.