deployment-validation-config-validate

You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/deployment-validation-config-validate/SKILL.md

The canonical home for this skill is deployment-validation-config-validate in rmyndharis/antigravity-skills

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 skill is highly code-rich and broadly actionable across the configuration-validation domain, but it inlines a large volume of full implementations with no progressive disclosure to reference files and lacks explicit validation/feedback checkpoints in its workflow. It would benefit from splitting code into referenced bundle files and adding validation gates.

Suggestions

Move the full class implementations into scripts/ or references/ files and keep SKILL.md as an overview with one-level-deep, clearly signaled links (e.g., 'See references/schema-validation.ts').

Add explicit validation checkpoints and a fix->retry feedback loop in the workflow (e.g., after analysis, validate findings, fix, re-run) since this is a batch operation over many config files.

Remove the verbatim repeat of the frontmatter description in the body intro and fix the small code gaps (missing 'import re', undefined 'List') so examples are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable code, but the opening paragraph repeats the frontmatter description verbatim and ~500 lines of full class implementations are inlined where tighter prose or offloaded references would do; it is not score 4 because of this repeated prose and bulk.	3 / 5
Actionability	Provides concrete, largely executable Python and TypeScript class implementations across all eight sub-tasks; minor gaps (e.g., missing 'import re' in the analyzer, 'List' undefined in the migrator) keep it just below fully copy-paste-ready at 5.	4 / 5
Workflow Clarity	The eight numbered sections give a rough sequence and the Output Format lists deliverables, but there are no explicit validation checkpoints or fix->retry feedback loops for a batch operation that scans many config files, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No references/, scripts/, or assets/ bundle files exist, yet ~500 lines of full implementations are inlined in SKILL.md with no signaled one-level-deep references; content that clearly belongs in separate files is inlined, fitting the score-2 anchor despite the section headers.	2 / 5
	Total	12 / 20 Passed

Description

53%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 conveys a clear domain and several concrete actions but is truncated, uses second-person voice, and omits any explicit 'when to use' trigger guidance. It is functional but needs a third-person rewrite, completion of the cut-off sentence, and an explicit trigger clause.

Suggestions

Complete the truncated sentence ("implement configurat...") and rewrite in third person (e.g., 'Validates, tests, and ensures correctness of application configurations...') to avoid the second-person penalty.

Add an explicit 'Use when...' clause with concrete natural triggers (e.g., 'Use when validating config files, building JSON Schema validation, or checking for secrets in .env/.yaml/.json configs').

Include natural synonyms and file extensions users actually say (config files, .env, .yaml, .yml, .json, secrets, schema validation) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('validating, testing, and ensuring the correctness', 'Create comprehensive validation schemas, implement configurat[ion...]'), but the text is truncated and the second-person opener ('You are a configuration management expert') triggers the -1 specificity penalty, pulling a base-4 down to 3.	3 / 5
Completeness	There is a clear 'what' (validate/test/ensure correctness of configs, create schemas) but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant domain keywords ('configuration management', 'validating', 'testing', 'validation schemas') are present, but common natural variations, synonyms, and file extensions a user would actually say are missing.	3 / 5
Distinctiveness Conflict Risk	The configuration-validation niche is mostly distinct from other skills with only minor overlap risk against general dev-tooling skills; it is not score 5 because 'configuration' is still a relatively broad term.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/deployment-validation-config-validate/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.