skills-validate

Validate the skill named in the invocation arguments by having a fresh agent do real work with it, then report where that agent got stuck. A defect here is a defect in the skill text, never in the agent. Flags: `--pr <number>` targets a PR instead of detecting one, `--plan-only` runs the zero-cost planning protocol from AGENTS.md instead of live generation, `--task "..."` supplies the use case instead of writing one, `--no-post` stops before publishing anything, `--keep` keeps the run directory. Live runs spend Scenario credits. Keep every generation the smallest one that still proves the point. ## 1. Review the objective Read the skill's `SKILL.md` and every file it links; `node scripts/lib/skills.mjs --dir <name>` prints its folder, nested under `skills/dcc/` or `skills/game-engines/` for an expert tool. If no skill has that name, list the close ones and stop. State, in your own words: the objective (one sentence), the triggering conditions the `description` claims, and the three to six non-obvious facts the skill exists to teach, the ones an agent would otherwise guess wrong (upload flow, `jobs_wait` re-calls, `runs_as` wiring, dry runs, launch semantics). Those facts are the traps the run has to spring. ## 2. Write a concrete use case One realistic task, in the words a user would actually use, that forces at least three of those traps and cannot be satisfied by generic MCP intuition (for an expert tool, generic knowledge of the application; its budget counts applic...