CtrlK
CommunityDocumentationLog inGet started
Tessl Logo

configuration-reference-generator

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill configuration-reference-generator
What are skills?

Configuration Reference Generator - Auto-activating skill for Technical Documentation. Triggers on: configuration reference generator, configuration reference generator Part of the Technical Documentation skill category.

Overall
score

19%

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Activation

7%

This description is severely underdeveloped, consisting only of a title, redundant trigger terms, and a category label. It provides no information about what the skill actually does, what outputs it produces, or when Claude should select it. The description would be nearly useless for skill selection among multiple options.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Generates structured 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', 'parameter descriptions', '.yaml docs', '.json schema'.

Specify the types of configuration files supported (YAML, JSON, TOML, INI, etc.) to improve distinctiveness and help Claude match user requests accurately.

DimensionReasoningScore

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, formatting, parsing, or any specific operations.

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 'Use when...' clause or equivalent guidance for when to select this skill.

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', 'settings reference', etc.

1 / 3

Distinctiveness Conflict Risk

While 'Configuration Reference Generator' is somewhat specific to a niche (config documentation), the lack of detail about what distinguishes it from general documentation skills or other reference generators creates moderate overlap risk.

2 / 3

Total

5

/

12

Passed

Implementation

0%

This skill is an empty template with no substantive content. It describes what a configuration reference generator skill would do in abstract terms but provides absolutely no actionable guidance, code examples, or concrete instructions for actually generating configuration references. The content appears to be auto-generated boilerplate that would be useless in practice.

Suggestions

Add concrete examples of configuration reference output formats (e.g., YAML schema documentation, environment variable tables, CLI flag references)

Include executable code or templates for extracting configuration from source files and generating documentation

Define a clear workflow: 1) identify config sources, 2) extract parameters, 3) generate reference format, 4) validate completeness

Remove all generic boilerplate text and replace with specific, actionable instructions for configuration documentation generation

DimensionReasoningScore

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, no commands, no specific steps, no examples of actual configuration reference generation. The content only describes what the skill supposedly does without showing how to do anything.

1 / 3

Workflow Clarity

No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for generating configuration references.

1 / 3

Progressive Disclosure

The content is a monolithic block of generic placeholder text with no meaningful structure. There are no references to detailed materials, examples, or related documentation that would help with actual configuration reference generation.

1 / 3

Total

4

/

12

Passed

Validation

69%

Validation11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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.