validate-skill-functionality

Invoke the validation workflow after the skill completes by saying "validate skill" or "check skill". It reviews the conversation history, confirms all required files were loaded, verifies nested skills ran, and reports findings in five lines or fewer.

The validation workflow reviews all Read tool calls in the conversation and cross-checks them against files referenced in SKILL.md, such as references/, scripts/, and assets/. It flags missing files, "File not found" errors, and truncated reads.

A nested skill is one skill invoked by another during execution, such as execute-project calling create-skill. Validation confirms the nested skill was loaded via the loader or explicit Read, its workflow was followed, and context passed correctly between skills.

Run it at the end of a skill's full execution workflow, not mid-execution. It is designed as a post-execution review to catch issues like skipped steps, unloaded references, or incorrect outputs after the skill has finished.

No. The workflow explicitly reports findings verbally in five lines or fewer, covering what worked, issues found, and recommendations. It follows the orchestrator rule prohibiting documentation file creation.