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

38%

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

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

Quality

Content

32%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 supplies extensive code across many configuration-validation concerns, but it is verbose, references undefined methods so examples don't run, lacks a real sequenced workflow with validation checkpoints, and inlines everything rather than splitting into reference files.

Suggestions

Slim the body to an overview plus 1-2 short executable snippets, moving the full modules into separate reference files under references/.

Fix the examples so they run: add missing imports ('re', 'List') and define or stub the referenced helper methods.

Turn the numbered sections into an actual sequenced workflow with explicit validate-fix-retry checkpoints for the destructive/batch operations (security scans, migrations).

Dimension	Reasoning	Score
Conciseness	The body is ~490 lines dominated by eight large boilerplate classes (ConfigurationAnalyzer, ConfigValidator, EnvironmentValidator, SecureConfigManager, ConfigDocGenerator, etc.) that Claude could write itself; noticeably verbose with several padded sections.	2 / 5
Actionability	Concrete code is provided, but it is not runnable as-is: many referenced methods are undefined (_should_ignore, _detect_config_type, _looks_like_real_secret, _extract_urls, loadConfig, detectEnvironment, isDevelopment, isEncryptedValue), 're' and 'List' are used without import, making guidance incomplete with missing key details.	3 / 5
Workflow Clarity	Numbered sections (1-8) read as a capability catalog rather than a sequenced workflow, and there are no validation checkpoints or feedback loops despite config validation being a batch/risky context; the cap-at-3 rule applies and the lack of any sequence places it at 2.	2 / 5
Progressive Disclosure	No bundle files exist and all eight code modules are inlined in SKILL.md; content that clearly belongs in separate reference files is inlined, fitting the 'minimal structure' anchor.	2 / 5
	Total	9 / 20 Passed

Description

45%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 the skill's domain and a few actions but is truncated, uses second-person voice, and omits any 'Use when' trigger guidance, capping completeness. It is recognizable but not crisp.

Suggestions

Rewrite in third person ('Validates and tests application configurations...') and complete the truncated sentence so the full scope reads cleanly.

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'when validating config files, schemas, or environment consistency').

Include natural synonyms and file extensions users say (e.g., JSON Schema, YAML, .env, config validation) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations') and a couple actions ('Create comprehensive validation schemas, implement configurat...') but coverage is thin and the text is truncated; the second-person 'You are' voice triggers a -1 specificity penalty per the rubric.	2 / 5
Completeness	It states a clear 'what' but has no 'Use when...' trigger clause, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Relevant keywords appear ('validating', 'testing', 'configuration', 'validation schemas') that a user might say, but common variations/synonyms and file extensions are missing.	3 / 5
Distinctiveness Conflict Risk	'Configuration validation' is a somewhat specific niche, but the broader 'configuration management' framing could overlap with related skills.	3 / 5
	Total	11 / 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-claude/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.