CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

validate-plan-file

Validate that orchestrator plan files conform to expected JSON schema. Use before workers read plan files or after orchestrators create them to ensure proper structure and required fields.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced validation guidance with concrete examples and error-recovery loops, scoring at the top of the rubric for actionability and workflow clarity. Its weaknesses are redundancy — schema file contents restated inline, a duplicated naming-convention listing, and a Notes section covering JSON Schema basics — and inlining of detail that duplicates the referenced schema files.

Suggestions

Remove the inline base and domain-specific field specification tables from Step 4 (or the 'Notes' JSON Schema Draft-07 feature list) and rely on the schema files loaded in Step 3, keeping only a short summary of what the validation covers.

Collapse the 'New Naming Convention' 12-file listing into the schema mapping table (e.g., one example per domain plus the {domain}-{phase} pattern) to eliminate duplicated enumeration.

Trim the 10-item 'Validation' checklist to the few checks not already explicit in the Instructions steps, since it currently restates them.

DimensionReasoningScore

Conciseness

The core steps are efficient, but there is tighten-able redundancy: the 'New Naming Convention' block re-lists all 12 file names already covered by the schema mapping, the 'Notes' section explains JSON Schema Draft-07 features (type checking, enums, required properties) Claude already knows, and the Step 4 field tables plus the 10-item 'Validation' checklist duplicate the external schema files loaded in Step 3. This fits anchor 3 (mostly efficient with some unnecessary explanation) rather than anchor 2, since there is no padded explanation of basic concepts.

3 / 5

Actionability

Guidance is fully executable for an instruction skill: an exact schema mapping, field-by-field validation rules with types/enums/defaults, a precise output format, and four complete input/output JSON examples covering the common cases (valid, missing required field, invalid enum, workflow/phase mismatch). This matches anchor 5's 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

Five clearly sequenced steps (read, map schema, load schema, validate, return result) are complemented by an explicit error-handling section, a validation checklist, and an integration snippet showing the fix-and-retry feedback loop ('If errors exist, fix plan file and retry'). This matches anchor 5's explicit validation steps, feedback loops, and checklists; anchor 4's 'minor validation gaps' does not apply.

5 / 5

Progressive Disclosure

The body has good section structure with clearly signaled supporting files ('Located in .claude/schemas/' with per-schema descriptions) and one-level-deep references, so most content is appropriately placed. It falls short of anchor 5 because roughly 25 lines of domain-specific field specifications are inlined despite duplicating the external schema files the skill instructs the reader to load in Step 3.

4 / 5

Total

17

/

20

Passed

Description

78%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 is strong: it clearly and explicitly states both what the skill does and when to use it, with relevant natural trigger terms tied to the orchestrator/worker workflow. Its main limitations are modest action specificity (one core action rather than several) and unmentioned concrete file patterns that would sharpen distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ('orchestrator plan files', 'expected JSON schema') and one concrete action ('Validate that orchestrator plan files conform to expected JSON schema' to 'ensure proper structure and required fields'), matching the anchor for domain plus 1-2 concrete actions. It does not list several distinct actions, so it falls short of anchor 4.

3 / 5

Completeness

It explicitly answers both 'what' ('Validate that orchestrator plan files conform to expected JSON schema... ensure proper structure and required fields') and 'when' ('Use before workers read plan files or after orchestrators create them') with concrete trigger phrases, matching anchor 5. It clearly exceeds anchor 4, where the 'when' would be less explicit.

5 / 5

Trigger Term Quality

Natural terms like 'validate', 'plan files', 'JSON schema', 'workers', and 'orchestrators' give good keyword coverage for this domain. A few natural variations are missing (e.g., specific file patterns like '.bug-detection-plan.json' or synonyms like 'check plan'), keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The 'orchestrator plan files' scoping gives a clear niche with mostly distinct triggers, but there is minor overlap risk with a generic JSON-schema validation skill since no specific file patterns are named. This fits anchor 4 better than anchor 5's 'minimal conflict risk' with distinct file-level triggers.

4 / 5

Total

16

/

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

maslennikov-ig/claude-code-orchestrator-kit

Path

.claude/skills/validate-plan-file/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.