Detects inconsistencies across configuration files, environments, and deployment manifests — missing keys, drifted values, type mismatches. Use when debugging why staging behaves differently from production, before a deploy to catch config drift, or when auditing multi-environment configs.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill config-consistency-checker100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 clearly articulates specific capabilities (detecting configuration inconsistencies with concrete examples like missing keys and type mismatches) and provides explicit, scenario-based triggers for when to use it. The description uses appropriate third-person voice and includes natural developer terminology that would match real user queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Detects inconsistencies across configuration files, environments, and deployment manifests' with specific types of issues: 'missing keys, drifted values, type mismatches'. | 3 / 3 |
Completeness | Clearly answers both what (detects inconsistencies, missing keys, drifted values, type mismatches) AND when with explicit triggers ('Use when debugging why staging behaves differently from production, before a deploy to catch config drift, or when auditing multi-environment configs'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'staging', 'production', 'deploy', 'config drift', 'multi-environment configs', 'configuration files', 'deployment manifests'. These are terms developers naturally use when facing these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on configuration consistency across environments with distinct triggers like 'config drift', 'staging vs production', and 'multi-environment configs' that are unlikely to conflict with general code or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently teaches config consistency checking with concrete algorithms, actionable classification criteria, and a complete worked example. The content respects Claude's intelligence while providing genuinely useful domain knowledge about distinguishing intentional differences from drift. The 'Do not' section provides important guardrails, and the output format gives clear structure for results.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with actionable tables, concrete examples, and no explanation of concepts Claude already knows. The content is dense with useful information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete algorithms (key-diff), executable grep commands, specific classification criteria, and a complete worked example with real config snippets. The output format is copy-paste ready. | 3 / 3 |
Workflow Clarity | The key-diff algorithm is clearly sequenced (flatten → set-diff → value-diff → classify). The classification tables provide explicit decision criteria, and the 'Do not' section acts as validation guardrails. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (what to compare, algorithm, classification, worked example, edge cases, output format). For a skill of this scope, the single-file structure is appropriate with logical progression from concept to execution. | 3 / 3 |
Total | 12 / 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.
Table of Contents
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.