!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation

Automation mode: Resolve modes.automation (project.local.yaml → project.yaml → default collaborative). Every AskUserQuestion call and every file write follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

Skill Test

Validates skills (.claude/skills/*/SKILL.md) and agents (.claude/agents/*.md) for structural compliance and behavioral correctness. No external dependencies, runs entirely within the existing skill/hook/template architecture.

Four modes:

Mode	Command	Purpose	Token Cost
static	/skill-test static [name|all]	Structural linter, 7 compliance checks per skill, plus agent, delegation and compatibility observations	Low (~1k/skill)
spec	/skill-test spec [name]	Behavioral verifier, evaluates assertions in a skill's or agent's test spec	Medium (~5k each)
category	/skill-test category [name|all]	Category rubric, checks a skill or agent against its category-specific metrics	Low (~2k each)
audit	/skill-test audit	Coverage report, skills, agent specs, last test dates	Low (~3k total)

What a pass proves. Every mode reads files; none runs the skill. static: the file has the structure a skill needs, not that it behaves. spec: read closely, the instructions cover each case, not that Claude follows them when it runs. category: the skill meets its category's rubric as written. audit: which skills and agents have specs, and when each was last checked. What a skill does shows only when it runs: a real request in a throwaway copy of the project, on each model you use, with and without the skill (Anthropic's Agent Skills best practices, "Build evaluations first").

---

Phase 1: Parse Arguments