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 underlying Python scripts (goal_router.py, loop_compiler.py, goal_state.py) are not included in the submission, so their behavior cannot be fully audited; ensure they do not execute untrusted content from goal.json or make unintended network calls.
• High-risk permission hints: Shell or command execution
• Permission surface may require sandboxing
• The SKILL.md excerpt ends mid-sentence in the forcing-question library, which may indicate truncation in the submitted documentation; verify the full file is present and complete.

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 underlying Python scripts (goal_router.py, loop_compiler.py, goal_state.py) are not included in the submission, so their behavior cannot be fully audited; ensure they do not execute untrusted content from goal.json or make unintended network calls.
• High-risk permission hints: Shell or command execution
• Permission surface may require sandboxing
• The SKILL.md excerpt ends mid-sentence in the forcing-question library, which may indicate truncation in the submitted documentation; verify the full file is present and complete.

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 underlying Python scripts (goal_router.py, loop_compiler.py, goal_state.py) are not included in the submission, so their behavior cannot be fully audited; ensure they do not execute untrusted content from goal.json or make unintended network calls.
• High-risk permission hints: Shell or command execution
• Permission surface may require sandboxing
• The SKILL.md excerpt ends mid-sentence in the forcing-question library, which may indicate truncation in the submitted documentation; verify the full file is present and complete.

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 underlying Python scripts (goal_router.py, loop_compiler.py, goal_state.py) are not included in the submission, so their behavior cannot be fully audited; ensure they do not execute untrusted content from goal.json or make unintended network calls.
• High-risk permission hints: Shell or command execution
• Permission surface may require sandboxing
• The SKILL.md excerpt ends mid-sentence in the forcing-question library, which may indicate truncation in the submitted documentation; verify the full file is present and complete.