Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• SKILL.md opens with a lengthy version changelog (v1.5 변경 고지 with prior v1.2–v1.4 failures) instead of a quick-start; new users must read through historical rollout notes before reaching usage instructions.
• High-risk permission hints: Shell or command execution
• Workflow inconsistency: the fast-mode Phase 2 states the monolith agent '메모리에서 패턴 탐지 + 윤문 + 자체검증' and does not mention running metrics.py, but references/metrics.py documents itself as an 'external pre-processor for the monolith fast path' with a CLI designed to run BEFORE the monolith. It is unclear whether metrics.py is actually invoked in the default path.
• The six referenced agents (humanize-monolith, ai-tell-detector, korean-style-rewriter, content-fidelity-auditor, naturalness-reviewer, taxonomist) are not defined in the provided excerpt — if their definitions (SKILL/agent files) are missing from the repository, neither fast nor strict mode can execute.