Skill Copy Contract Review
When to Use
- Need to review Skill, Prompt, metadata, examples, or output format.
- Need to determine whether the copy is executable, independently installable, and verifiable.
Execution Flow
- Confirm the review scope and document role.
- Establish the contract chain of "trigger conditions → input → execution rules → output → constraints → verification".
- Report issues, locations, impacts, and evidence by blocking issues, important suggestions, and general suggestions.
- List missing information and explain which conclusions have not yet been verified.
Core Constraints
- Do not add behaviors or tool capabilities that the user did not provide out of thin air.
- Do not present static reading as runtime verification.
- Do not conceal genuine contract gaps due to stylistic preferences.
- Do not directly rewrite files unless the user explicitly requests it.
Load on Demand
- Must read before producing
prompts/skill-prose-review.md。
- Use when evaluation is needed
evals/; report static verification and runtime verification separately.
Pre-delivery Self-check
- Scope and document role are clear
- Input, output, constraints, and verification chain are complete
- Information gaps and evidence levels are indicated
- No unauthorized file modifications
