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

50%

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 ./skills/deployment-validation-config-validate/SKILL.md

Quality

Content

46%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 rich with concrete, executable code across eight configuration-validation concerns, but it is a monolithic single-file dump with undefined helper methods, no validation checkpoints on destructive migration, and no progressive disclosure to reference files.

Suggestions

Move the bulk implementations into reference files (e.g. references/analyzer.py, references/validator.ts) and keep SKILL.md as a lean overview with one short example per concern.

Complete the code so it runs as written: import `re`/`List` where used and implement the referenced helper methods (_should_ignore, _detect_environment, _looks_like_real_secret, _extract_urls, loadConfig, detectEnvironment, isDevelopment, isEncryptedValue).

Add explicit validation checkpoints to the migration/runtime workflows (validate config → on failure, fix and re-validate → only then apply migration), since migration mutates config versions.

Dimension	Reasoning	Score
Conciseness	The body inlines ~450 lines of code across 8 full implementation classes plus a repeated description sentence and a restating 'Context' section; it is mostly actionable but could be tightened considerably by moving implementations to reference files.	3 / 5
Actionability	Provides substantial concrete code using real APIs (Ajv, crypto, chokidar, semver), but many referenced helpers are undefined (_should_ignore, _detect_config_type, _looks_like_real_secret, _extract_urls, loadConfig, detectEnvironment) and `re`/`List` are unimported, leaving the code incomplete rather than copy-paste ready.	3 / 5
Workflow Clarity	The eight numbered sections give a clear sequence, but there are no validation/verification checkpoints, and the configuration-migration step is destructive (mutates config versions) — missing feedback loops cap workflow clarity at 3.	3 / 5
Progressive Disclosure	No references/scripts/assets bundle exists and all eight full implementations are inlined directly in SKILL.md; content that clearly belongs in separate reference files is inlined with only section headers for structure.	2 / 5
	Total	11 / 20 Passed

Description

55%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 states a clear domain and several concrete actions but is truncated mid-word and entirely lacks a 'Use when...' trigger clause, capping completeness. Trigger terms are relevant but miss natural user phrasings.

Suggestions

Complete the truncated description ('implement configurat' → 'implement configuration testing strategies, and ensure configurations are secure and error-free').

Add an explicit trigger clause, e.g. 'Use when validating configuration files, defining JSON/YAML schemas, or checking config consistency across environments.'

Include natural user-facing keywords and file extensions ('config files', '.env', 'YAML', 'JSON Schema') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('validating, testing, and ensuring the correctness', 'Create comprehensive validation schemas', 'implement configuration testing strategies'), though the sentence is truncated mid-word ('implement configurat'), leaving coverage slightly incomplete.	4 / 5
Completeness	Has a clear 'what' (validate/test configs, create schemas) but no 'when' clause — there is no 'Use when...' trigger guidance, which caps completeness at 3 per the rubric; truncation further weakens the what.	3 / 5
Trigger Term Quality	Contains relevant terms ('configuration validation', 'validation schemas', 'configuration testing') but leans technical and misses common natural variations a user might say ('config files', 'env files', 'schema validation').	3 / 5
Distinctiveness Conflict Risk	Focused on configuration validation/testing which is somewhat specific, but 'configuration management' is broad and the skill name ('deployment-validation-config-validate') signals overlap risk with deployment/infra-validation skills.	3 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/deployment-validation-config-validate/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.