evidence-catalog-generator 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
• The script does not validate that the input data contains required fields before normalization, though it does substitute placeholders for missing values.
• High-risk permission hints: Shell or command execution
• Permission surface may require sandboxing
• If a user-supplied DOCX template contains no recognizable catalog table, the script will write to the first available table or append a new generic table, which may surprise advanced template users.