config-consistency-checker
Automatically analyzes configuration files to detect inconsistencies, conflicts, missing keys, and divergent values across environments, versions, or modules. Use when managing multi-environment configurations, detecting config drift, validating configuration changes, or ensuring consistency across microservices. Supports JSON, YAML, TOML, INI, XML, .env, and properties files. Identifies security issues like hardcoded secrets and provides actionable resolution guidance.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill config-consistency-checker80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 is an excellent skill description that hits all the key criteria. It provides specific concrete actions, includes a comprehensive 'Use when...' clause with natural trigger terms, lists supported file formats, and carves out a distinct niche around configuration analysis and drift detection. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'detect inconsistencies, conflicts, missing keys, and divergent values', 'identifies security issues like hardcoded secrets', 'provides actionable resolution guidance'. Also specifies supported formats (JSON, YAML, TOML, INI, XML, .env, properties). | 3 / 3 |
Completeness | Clearly answers both what ('analyzes configuration files to detect inconsistencies, conflicts, missing keys...') AND when ('Use when managing multi-environment configurations, detecting config drift, validating configuration changes, or ensuring consistency across microservices'). Explicit 'Use when...' clause present. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'configuration files', 'config drift', 'multi-environment', 'microservices', 'JSON', 'YAML', 'TOML', 'INI', 'XML', '.env', 'hardcoded secrets'. Good coverage of both general terms and specific file formats. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on configuration file analysis across environments. The combination of 'config drift', 'multi-environment', 'microservices', and specific file formats creates distinct triggers unlikely to conflict with general file processing or code analysis skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid conceptual framework for configuration consistency checking with good examples of issue types and report formats. However, it lacks executable code for performing the actual analysis, includes some verbose sections with generic advice, and could benefit from clearer validation workflows and better content organization across files.
Suggestions
Add executable code snippets showing how to actually parse and compare configuration files (e.g., Python using json/yaml libraries with diff logic)
Remove or significantly condense 'Best Practices' and 'Tips' sections - these contain generic advice Claude already knows
Add explicit validation steps: after applying a fix, re-run the check to confirm the issue is resolved
Move 'Detection Patterns' and 'Report Format' to separate reference files, keeping SKILL.md as a concise overview with quick examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'Best Practices' and 'Tips' that contain generic advice Claude already knows. The workflow steps 1-2 (Parse/Extract) describe obvious operations without adding value. | 2 / 3 |
Actionability | Provides good examples of what issues look like and how to resolve them, but lacks executable code for actually performing the analysis. The examples show input/output but not the actual detection logic or commands to run. | 2 / 3 |
Workflow Clarity | The 5-step workflow is listed but lacks validation checkpoints or feedback loops. For a tool that detects configuration issues, there's no guidance on verifying fixes were applied correctly or iterating on complex multi-file scenarios. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Detection Patterns', 'Common Scenarios', and detailed examples could be split into reference files, with SKILL.md serving as a leaner overview. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.