tessl-labs/configuration-management
Production config management for any backend — centralized config module, env vars, no hardcoded secrets, fail-fast validation
86
77%
Does it follow best practices?
Impact
100%
1.88xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates when to apply the skill with explicit trigger conditions and explains the problems it prevents. However, it lacks specific concrete actions (what patterns exactly?) and could benefit from more natural user trigger terms like 'environment variables' or '.env'. The overly broad activation scope may cause unnecessary conflicts with other backend skills.
Suggestions
Add specific concrete actions like 'create .env files', 'implement config validation', 'set up environment-specific settings' to clarify what the skill actually does.
Include common user trigger terms such as 'environment variables', '.env', 'dotenv', 'credentials', 'settings file' that users naturally say when needing config help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (configuration management) and mentions some outcomes (prevent hardcoded secrets, wrong config, scattered config), but doesn't list specific concrete actions like 'create .env files', 'set up environment variables', or 'implement config validation'. | 2 / 3 |
Completeness | Clearly answers both what (configuration management patterns) and when ('Apply whenever building, extending, or scaffolding any server, API, CLI tool, or backend service -- even if the task only asks for routes or business logic'). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'backend application', 'server', 'API', 'CLI tool', 'backend service', 'config', 'secrets', but misses common user phrases like 'environment variables', '.env', 'dotenv', 'settings', 'credentials'. | 2 / 3 |
Distinctiveness Conflict Risk | While focused on configuration management, the broad trigger of 'any backend application' and 'even if the task only asks for routes or business logic' could cause this skill to activate too frequently, potentially conflicting with general backend development skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples across multiple languages and a clear checklist for validation. The main weakness is verbosity in the motivational sections that explain problems Claude already understands, and the monolithic structure that could benefit from splitting language-specific examples into separate files.
Suggestions
Remove or drastically shorten the 'Why This Matters From Day One' section - Claude understands why hardcoded secrets and scattered config are problematic
Move Python and Go examples to separate reference files (e.g., PYTHON.md, GO.md) and link from the main skill, keeping only TypeScript as the primary example
Trim the WRONG examples - one brief example per anti-pattern is sufficient; Claude doesn't need multiple variations to understand the concept
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Why This Matters From Day One' section explains concepts Claude already understands (why hardcoded secrets are bad, why scattered config causes problems). The WRONG/RIGHT examples are valuable but the explanatory prose could be significantly trimmed. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples in TypeScript, Python, and Go. The required() and optional() helper patterns are concrete and immediately usable. Examples show both wrong and right approaches with real code. | 3 / 3 |
Workflow Clarity | The 'Applying to Any New Backend Application' section provides a clear 6-step sequence. The checklist at the end serves as validation. For a configuration skill (not a destructive/batch operation), the workflow is appropriately clear. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one monolithic file. The detailed code examples for three languages could be split into separate reference files, with SKILL.md showing just one language and linking to others. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents