Agent check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.From its SKILL.md
npx -y skills add claude-world/director-mode-lite --skill agent-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
4.9 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it
Agent File Validator
Validate agent files in .claude/agents/ for correct format against the
official Claude Code spec (plus Director Mode conventions).
Validation Target
- With argument: validate specific file
- Without: validate all
.claude/agents/*.md
Required Frontmatter
---
name: agent-name # Required: lowercase, hyphenated, 3-50 chars
description: > # Required: 10-5000 chars, include triggering conditions + <example> blocks
Use this agent when [conditions]. Examples:
<example>
Context: [situation]
user: "[request]"
assistant: "[response using this agent]"
</example>
color: cyan # Required by Director Mode convention (CI-enforced); OPTIONAL per official spec
model: sonnet # Required by Director Mode convention (CI-enforced); OPTIONAL per official spec.
# Valid: fable, opus, sonnet, haiku, inherit, default, best, sonnet[1m], opus[1m]
# (or a full model ID). inherit is the recommended default. NOT opusplan.
effort: medium # Optional: low, medium, high, xhigh, max
tools: # Optional: YAML list (omit = all tools available)
- Read
- Write
- Grep
disallowedTools: # Optional: explicit tool blocking
- NotebookEdit
maxTurns: 20 # Optional: max agentic turns (positive integer)
skills: # Optional: preloaded skill names (list)
- linked-skill
memory: project # Optional: one of user, project, local
background: false # Optional: run the agent in the background (boolean)
isolation: worktree # Optional: run the agent in an isolated git worktree
---
Valid Tools
Read, Write, Edit, Bash, Grep, Glob, Agent (Task = legacy alias),
Skill, WebFetch, WebSearch, TodoWrite, NotebookEdit, AskUserQuestion
Valid Colors
yellow, red, green, blue, magenta, cyan
Valid Models
fable, opus, sonnet, haiku, inherit, default, best, sonnet[1m], opus[1m]
(or a full model ID). inherit recommended. NOT opusplan (session-only, invalid for agents).
NOT supported in filesystem/plugin agent frontmatter (WARN if present)
hooks # Root/skill-scoped only; ignored on filesystem/plugin agents
mcpServers # Not supported on filesystem/plugin agents
permissionMode # Security restriction — not honored from agent frontmatter
forkContext # Not an official field (agents fork automatically when dispatched)
Validation Checklist
Required Fields
-
nameexists (lowercase, hyphenated, 3-50 chars) -
descriptionexists (10-5000 chars, recommend 200-1000 with<example>blocks) -
coloris set (valid color name) — required by Director Mode convention, optional per spec -
modelis set (valid value below) — required by Director Mode convention, optional per spec
Optional Fields (official)
-
toolsare valid tool names, YAML list format (omit = all tools available) -
disallowedToolsare valid tool names -
effortis one of: low, medium, high, xhigh, max -
maxTurnsis a positive integer -
skillsis a list of skill names (references existing skills) -
memoryis one of: user, project, local -
backgroundis boolean -
isolationisworktree -
modelis valid: fable, opus, sonnet, haiku, inherit, default, best, sonnet[1m], opus[1m], or a full model ID (NOT opusplan)
Unsupported / Unknown Fields (WARN, do not silently accept)
- Warn on
hooks,mcpServers,permissionMode— not supported in filesystem/plugin agent frontmatter - Warn on
forkContext— not an official field
Content Structure
-
# Agent Nameheading -
## Activationsection - Process/workflow description
- Output format definition
Format Rules
-
toolsuses YAML list format (not[Read, Write]bracket array) — Director Mode / CI house rule - No duplicate tools in list
- All tools are valid tool names
Output Format
## Agent Validation Report
### Files Checked
| File | Status | Issues |
|------|--------|--------|
| code-reviewer.md | OK | None |
| my-agent.md | WARN | Missing color, model |
### Summary
- Total: [N]
- Valid: [N]
- Needs fixes: [N]
Auto-Fix
- Convert bracket array tools to YAML list format
- Convert string
skillsto YAML list - Add missing
colorfield (default: cyan) - Add missing
modelfield (default: inherit) - Remove unsupported fields (
hooks,mcpServers,permissionMode) or flag for review - Remove
forkContext(not an official field) - Replace
opusplanmodel with a supported value - Remove invalid tools
- Add recommended sections
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most quality gates skills give in ~1.2k tokens
Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06
- Read full output and check exit codein 45 of 1524, across 40 files
- Verify output confirms the claimin 44 of 1524, across 39 files
- Identify the command that proves the claimin 43 of 1524, across 39 files
- Execute the full verification commandin 36 of 1524, across 30 files
- Produce a verification reportin 34 of 1524, across 18 files
- Review git diff changesin 30 of 1524, across 16 files
- Fix build failures immediatelyin 29 of 1524, across 9 files
- Group findings by severityin 28 of 1524
- State claim only with evidencein 27 of 1524, across 22 files
- Verify regression tests with red-green cyclein 26 of 1524, across 22 files
- Run the full test suitein 26 of 1524, across 25 files
- Run test suite with coveragein 25 of 1524, across 10 files
Said here and by no other author read
- Validate agent files against official spec
- Verify tool names are valid
- Warn on unsupported frontmatter fields
- Convert bracket array tools to YAML list
- Add missing color and model fields
- Replace invalid model values
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.