check-environment 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 SKILL.md does not explicitly describe its own limitations or the environments where it is not applicable.
• No OpenAgentSkill engagement data yet
• High-risk permission hints: Shell or command execution
• The skill checks for optional tools like jq but does not provide a clear runtime flag or metadata field to enable the optional-hook audit; it relies on the user's pre-existing selection.