CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deployment-validation-config-validate

Validate application configuration with schemas, environment checks, and runtime tests. Use when preventing configuration errors, checking deployment settings, or detecting configuration drift.

55

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/deployment-validation-config-validate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 body delivers a readable high-level structure (persona, use/do-not-use sections, numbered instruction phases, output format) but buries it under ~450 lines of generic, partially non-executable boilerplate in a single monolithic file. Executability gaps (missing imports, undefined helpers, mixed languages) and absent validation feedback loops keep the actionable and workflow dimensions at mid-scale.

Suggestions

Move the full class implementations (schema validator, environment validator, migrator, secure config manager, doc generator) into files under references/ and keep only short, decision-oriented summaries in SKILL.md (e.g., 'Schema validation: see references/schema-validation.md').

Fix executability: add the missing 'import re', define or remove the undefined helpers (_should_ignore, _looks_like_real_secret, _extract_urls, loadConfig, detectEnvironment, isDevelopment), initialize 'this.validator', and state when to use the Python vs TypeScript variants.

Add explicit validation checkpoints and recovery loops, especially for config migration — verify the migrated config still validates against the target schema before writing it back.

DimensionReasoningScore

Conciseness

The body is ~490 lines of complete, generic class implementations (validators, migrators, encryption managers, doc generators) that restate boilerplate Claude can already write, adding no project-specific rules or novel knowledge. This matches the anchor for noticeably verbose, padded sections; it is not a 3 because nearly every section is generic boilerplate rather than just a few.

2 / 5

Actionability

Concrete code exists, but much of it is not executable as written: 're.search' is used without importing 're', and helpers like '_should_ignore', '_looks_like_real_secret', '_extract_urls', 'loadConfig', 'detectEnvironment', 'isDevelopment' are never defined, while 'this.validator' is never initialized. Python and TypeScript examples are also mixed with no guidance on which applies. This fits the anchor for incomplete guidance with missing key details.

3 / 5

Workflow Clarity

The numbered sections (1-8) plus an Output Format list provide a sequence, but there are no validation checkpoints or error-recovery loops, and section 6 mutates configs via migration with no post-migration verification. Per the destructive/batch-operations cap, this cannot exceed 3 even though the sequence itself is legible.

3 / 5

Progressive Disclosure

No bundle files exist and everything — eight large class implementations that clearly belong in separate reference files — is inlined monolithically in one SKILL.md with no references at all. This matches the anchor for content that belongs in separate files being inlined; section headers alone do not lift it to a 3 since no reference structure is present or signaled.

2 / 5

Total

10

/

20

Passed

Description

83%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.

A strong description: third-person, concrete about capabilities, and equipped with an explicit, multi-phrase 'Use when...' trigger clause. Its only weaknesses are slightly incomplete coverage of the skill's actual scope and a small overlap risk around deployment-settings language.

DimensionReasoningScore

Specificity

The description names three concrete action areas — 'validate application configuration with schemas, environment checks, and runtime tests' — matching the anchor for several specific actions with minor gaps. It falls short of a 5 because it omits capabilities the skill body actually covers (secure configuration, migration, documentation generation).

4 / 5

Completeness

It clearly answers both 'what' ('Validate application configuration with schemas, environment checks, and runtime tests') and 'when' with an explicit 'Use when...' clause listing concrete triggers, in third-person voice — a direct match for the top anchor.

5 / 5

Trigger Term Quality

Natural phrases like 'preventing configuration errors', 'checking deployment settings', and 'detecting configuration drift' give good keyword coverage. A few common terms are missing — the 'config' shorthand, file types (.env, .yaml, .json), and 'schema validation' — so it fits anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Configuration validation and drift detection form a distinct niche with specific triggers. However, 'checking deployment settings' creates minor overlap risk with deployment/CI-related skills, fitting anchor 4 rather than 5.

4 / 5

Total

17

/

20

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

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/deployment-validation-config-validate/SKILL.md

Reviewed

Table of Contents

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.