tax-dispute-response Eval report.

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
• Low GitHub adoption signal
• No explicit setup/requirements section and no dedicated limitations/disclaimer; users may not know operational prerequisites or that the output should be validated by a tax professional.
• High-risk permission hints: Shell or command execution
• Some legal references appear outdated or superseded (e.g., 国税发〔2009〕157号 and 国税发〔2009〕2号 may have been replaced by newer rules; 《行政处罚法》 article numbers reflect the old law).