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 restates the skill name without providing any concrete information about what the skill does, when it should be used, or what distinguishes it from other documentation skills. It lacks specific actions, natural trigger terms, and explicit usage guidance, making it ineffective for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured reference documentation for configuration 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 config options, generate a reference for settings/parameters, or create docs for .yaml/.json/.toml configuration files.'
Include distinct file types or formats to reduce conflict risk, e.g., mention specific config formats (YAML, JSON, TOML, INI) and output formats (Markdown tables, HTML reference pages).
| 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 'what does this do' beyond restating the skill name, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line just repeats the title and does not serve as meaningful 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 phrases a user would say; users are more likely to say things like 'document config options', 'generate reference docs for settings', or 'config file documentation'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any documentation-related skill. 'Technical Documentation' is a broad category, and without specific actions or file types, it is indistinguishable from other documentation 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 shell with no substantive content. It consists entirely of generic boilerplate that could apply to any skill topic, with the phrase 'configuration reference generator' substituted in. It provides no actionable guidance, no examples, no code, and no real information about how to generate configuration references.
Suggestions
Add concrete, executable examples showing how to generate configuration reference documentation (e.g., parsing config files, extracting parameter metadata, and outputting structured markdown tables with parameter names, types, defaults, and descriptions).
Define a clear workflow: e.g., 1) Scan config schema/source files, 2) Extract parameters and metadata, 3) Generate markdown reference tables, 4) Validate completeness against the actual config schema.
Include at least one complete input/output example showing a sample configuration file and the expected reference documentation output.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that contain no specific information and replace them with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific information about configuration reference generation, and every section is padded with generic, non-informative text. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples, no templates, no specific steps for generating configuration references. Every bullet point is vague and abstract (e.g., 'Provides step-by-step guidance' without actually providing any). | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims about capabilities without any actual process described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to reference either, but the skill itself contains nothing worth organizing. | 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
3a2d27d
- 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.