CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

84

1.16x
Quality

76%

Does it follow best practices?

Impact

98%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/config-consistency-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and gives concrete detection guidance, but it is padded with common-knowledge sections, lacks executable tooling, and omits validation checkpoints for a batch operation. Moderate quality with room to tighten and add a verification step.

Suggestions

Remove or merge the 'Best Practices', 'Tips', and 'Common Scenarios' sections, whose bullets restate knowledge Claude already has, to tighten conciseness.

Add an explicit validation/verification step to the workflow (e.g. re-check that every flagged missing key is genuinely required before reporting) since this is a batch analysis operation.

Provide at least one concrete mechanism for comparing configs (a small script snippet or a specific diff procedure) to move actionability from illustrative examples toward executable guidance.

DimensionReasoningScore

Conciseness

The core workflow, examples, and report format are efficient, but 'Best Practices', 'Tips', and 'Common Scenarios' restate common knowledge and 'Detection Patterns' duplicates the Quick Examples, so it could be tightened.

3 / 5

Actionability

Concrete detection patterns (e.g. 'password, secret, key with hardcoded values', 'ssl: false, debug: true in production') and a structured report template are provided, but there is no executable code, command, or concrete method for programmatically comparing configs.

3 / 5

Workflow Clarity

A clear five-step sequence (Parse, Extract, Compare, Detect, Report) is present, but this batch analysis operation has no validation or verification checkpoint, capping the score at 3 per the rubric.

3 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references, but the ~220-line body is entirely inline (the long report-format template and detection patterns could live in separate reference files).

4 / 5

Total

13

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 is exemplary: third-person voice, concrete capabilities, explicit 'Use when' triggers with natural phrasing, and a distinct niche. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'detect inconsistencies, conflicts, missing keys, and divergent values', 'Identifies security issues like hardcoded secrets and provides actionable resolution guidance' — with comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (analyzes configuration files to detect inconsistencies/conflicts/missing keys/divergent values) and 'when' via a clear 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say — 'managing multi-environment configurations, detecting config drift, validating configuration changes, or ensuring consistency across microservices' — plus the full set of file extensions (JSON, YAML, TOML, INI, XML, .env, properties).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (config drift and consistency checking across environments/versions/modules) with distinct triggers and enumerated formats, minimizing overlap with other skills.

5 / 5

Total

20

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ArabelaTso/Skills-4-SE
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.