configuration-reference-generator
Configuration Reference Generator - Auto-activating skill for Technical Documentation. Triggers on: configuration reference generator, configuration reference generator Part of the Technical Documentation skill category.
33
0%
Does it follow best practices?
Impact
96%
0.97xAverage 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/configuration-reference-generator/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 repeats the skill name and category without providing any substantive information. It lacks concrete actions, natural trigger terms, explicit usage guidance, and distinguishing details. It would be nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured configuration reference documentation from config files, including parameter names, types, default values, and descriptions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to document configuration options, generate a settings reference, create parameter docs, or produce config file documentation (.yaml, .toml, .ini, .json).'
Include varied natural keywords users might say, such as 'config docs', 'settings reference', 'parameter documentation', 'environment variables', 'config schema', to improve trigger term coverage and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Technical Documentation') and a label ('Configuration Reference Generator') but does not describe any concrete actions. There are no verbs indicating what the skill actually does—no 'generates', 'extracts', 'formats', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill's own name repeated twice ('configuration reference generator'). These are not natural keywords a user would say; users are more likely to say things like 'config docs', 'settings reference', 'parameter documentation', or 'generate config reference'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Technical Documentation' could overlap with many other documentation skills. Without specific actions or file types, there is nothing 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 an empty template/placeholder with no actual instructional content. It repeatedly names the skill topic without providing any actionable guidance, concrete examples, code, commands, or workflows. It fails on every dimension because it contains no substantive information that would help Claude perform configuration reference generation tasks.
Suggestions
Add concrete, executable examples showing how to generate a configuration reference document (e.g., a script that parses config files and outputs markdown documentation with parameter names, types, defaults, and descriptions).
Define a clear multi-step workflow: e.g., 1) Identify config source files, 2) Extract parameters and metadata, 3) Generate structured markdown output, 4) Validate completeness against the source.
Include at least one complete input/output example showing a sample configuration file and the expected reference documentation output.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than providing actual instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'configuration reference generator' excessively, and provides zero substantive information about how to actually generate configuration references. | 1 / 3 |
Actionability | There are no concrete steps, no code examples, no commands, no templates, and no executable guidance whatsoever. Every section is vague and abstract, describing what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all—no steps, no sequence, no validation checkpoints. The 'step-by-step guidance' is merely claimed in a bullet point but never provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no meaningful structure, no references to detailed materials, and no navigation to supplementary files or resources. | 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
c8a915c
- 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.