Menu
Use when implementing a sanity check subagent for the phase 2 optimization in Eve loop.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when creating new subagents, editing existing subagents, or verifying subagents work before deployment
Use when choosing, editing, or overriding EvE driver settings for codex_smoke, codex_max, or interactive/debug runs.
Use when an Eve agent is behaving wrong (stuck, gaming the score, bad reasoning) and you need to read its own rollout to find out why
Use when implementing a subagent.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
| name | implement-check-subagent |
| description | Use when implementing a sanity check subagent for the phase 2 optimization in Eve loop. |
check is a sanity check, not formal evaluation.
Implement a check subagent. For the subagent file format, refer to the implement-subagent skill.
For a concrete application example, refer to:
configs/eve/application/circle_packing/check_codex.tomlKeep in mind that the check subagent is expected to run from workspace/solver/, i.e. the downstream task repository.
The implemented subagent file should in general provide:
A sanity check command sequence that runs inside workspace/solver/. Follow the application pattern from the examples, for example:
A boundary check command.
You do not need to provide the command, following the {{BOUNDARY_CHECK_COMMAND}} pattern used in the examples.