crisis-monitor 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
• Missing explicit setup/configuration instructions (e.g., how to obtain and use SandBase credentials or environment variables).
• Limited documentation on tool parameters; the API map defers entirely to sandbase_describe_tool, which could be more informative for initial selection.
• No dedicated limitations section (e.g., rate limits, data coverage, potential biases, or legal considerations for monitoring social platforms).
• Quality score needs review