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

46%

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

42%

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

The content is highly actionable with complete executable code, but it is a verbose monolith that teaches library basics Claude already knows and lacks both validation checkpoints and any progressive-disclosure structure. It would improve dramatically by trimming inline implementations and splitting detailed references into bundle files.

Suggestions

Replace the full inline class implementations with concise snippets and move exhaustive reference code into files under references/ or scripts/, keeping SKILL.md a lean overview.

Add explicit validation/verification checkpoints (e.g. run the test suite and re-validate after migration or encryption changes) with fix-retry loops for the destructive and batch operations.

Remove or compress explanations of how standard libraries (Ajv, chokidar, crypto) work, keeping only what is non-obvious or skill-specific.

Dimension	Reasoning	Score
Conciseness	The body is a ~470-line monolith of full inline class implementations that effectively teaches library usage Claude already knows (Ajv, chokidar, crypto, semver), padding the context with executable-but-unnecessary reference implementations rather than lean guidance.	1 / 3
Actionability	Each section provides complete, executable code in real languages (Python/TypeScript) with concrete classes, imports, and worked examples such as the Ajv validator and Jest test cases, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	Eight numbered sections give a recognizable sequence, but there are no explicit validation checkpoints or fix-retry feedback loops for risky batch operations (secret scanning, config migration, encryption), which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	It is a monolithic wall of text with all detail inline and no external references or navigation; since it far exceeds the under-50-line simple-skill exception and no bundle files exist, there is no progressive disclosure structure to reward.	1 / 3
	Total	7 / 12 Passed

Description

50%

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 recognizable domain and several concrete actions, but it is truncated, uses second-person voice, and lacks an explicit "Use when" trigger, leaving it solidly mid-tier across all dimensions. Adding a trigger clause and switching to third person would lift it substantially.

Suggestions

Rewrite in third person and complete the truncated sentence, e.g. "Validates, tests, and ensures the correctness of application configurations; creates validation schemas and implements configuration testing strategies."

Add an explicit trigger clause such as "Use when validating config files (.env, YAML, JSON, TOML), defining JSON schemas, or enforcing environment-specific configuration rules."

Include natural trigger terms users would actually say ("config validation", "validate schema", "check config files") to improve trigger term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	It lists several concrete actions ("validating, testing, and ensuring the correctness", "Create comprehensive validation schemas, implement configurat[ion ...]"), but the description is truncated mid-sentence and uses second-person voice ("You are a configuration management expert"), which per the guidelines reduces specificity by one from a would-be 3.	2 / 3
Completeness	It answers "what" (validate/test/ensure correctness of configurations, create schemas) but provides no "Use when..." trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "configuration management", "validating", and "validation schemas" are relevant, but the coverage is generic and omits common natural variations a user would say (e.g. "config files", ".env", "schema validation", "validate YAML/JSON").	2 / 3
Distinctiveness Conflict Risk	"Configuration management / validation" is a recognizable niche but is broad enough to overlap with general coding, security, and DevOps skills, so it could trigger for adjacent tasks.	2 / 3
	Total	8 / 12 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: e63f7dd

Reviewed: about 3 hours 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.