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.
36
Quality
3%
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
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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It provides no information about what the skill actually does, repeats the trigger term redundantly, and lacks any guidance for when Claude should select this skill. The description would be nearly useless 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 descriptions, default values, data types, and usage examples.'
Include a 'Use when...' clause with natural trigger terms like 'document config options', 'config file reference', 'settings documentation', 'YAML/JSON/TOML config docs', or 'parameter reference'.
Specify what types of configuration formats are supported (e.g., YAML, JSON, INI, environment variables) to improve distinctiveness and help Claude match user requests accurately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Configuration Reference Generator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of generating, parsing, documenting, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause, no explanation of capabilities, and no explicit trigger guidance beyond the redundant skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('configuration reference generator, configuration reference generator'). These are not natural keywords users would say - users would more likely say 'document config options', 'generate config docs', or 'reference for settings'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Configuration Reference Generator' is somewhat specific to a niche (configuration documentation), the lack of detail about what types of configurations, formats, or outputs makes it potentially overlap with general documentation or code 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 essentially a placeholder with no substantive content. It describes what a configuration reference generator skill might do in abstract terms but provides no actual instructions, examples, templates, or workflows. The content fails on all dimensions by being both verbose and completely non-actionable.
Suggestions
Add concrete examples showing input configuration files and the expected reference documentation output format
Provide executable code or commands for generating configuration references (e.g., parsing config schemas, extracting documentation from comments)
Define a clear workflow: 1) identify config sources, 2) extract parameters, 3) generate markdown tables, 4) validate completeness
Include a template or schema for the generated configuration reference documentation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no commands, and no specific instructions. The skill describes what it claims to do but never shows how to actually generate configuration references. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only lists vague 'capabilities' without any process for accomplishing them. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to examples, templates, or supporting documentation that would be expected for a documentation generator skill. | 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
0c08951
- 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.