post-merger-tax-integration 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
• SKILL.md does not include an explicit limitations section, such as a note that tax outcomes depend on specific facts and regulations may change.
• There is no setup or usage-bounds section clarifying that this is a knowledge/analysis skill and should not be used to file tax documents without qualified professional review.
• Legal citations are high-level and lack effective-date or jurisdiction details, which could lead to stale application if regulations change.