agent-workflow-playbook 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
• SKILL.md is primarily a methodology guide rather than an executable agent workflow with a clear invocation contract; agents may need additional instructions on how to apply it to a specific task.
• Financial research output is not financial advice; require human review before any live investment decision
• The 'latest' tag is vague and not a meaningful functional category, which may cause confusion in marketplace listings.
• The reported case metrics are self-reported and not independently audited; while the document does label them, users should be reminded to establish their own baselines before relying on the numbers.