com um clique
implement-evaluation-steps
Use when defining or updating Eve evaluation steps.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Use when defining or updating Eve evaluation steps.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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 sanity check subagent for the phase 2 optimization in Eve loop.
Use when implementing a subagent.
| name | implement-evaluation-steps |
| description | Use when defining or updating Eve evaluation steps. |
Evaluation is a first-class config tree: configs/eve/evaluation/<app>.yaml composed via the
run config's defaults: list (e.g. - evaluation: circle_packing). The file
declares an ordered evaluation.steps pipeline plus an evaluation.failure_score. Every run
config MUST compose an evaluation: group; there is no implicit fallback.
evaluation.steps is an ordered, arbitrarily-long pipeline. Dispatch is by FORM, not a kind
field:
.sh path string -> programmatic (deterministic) step{prompt, immutable?} mapping -> LLM judge step (a first-class worker: its own prompt +
budget, plus an OPTIONAL immutable rubric + score-check subagent). Omit immutable for a
lightweight judge that runs from its ENTRYPOINT alone.# @package _global_
evaluation:
steps:
- configs/eve/evaluation/<app>/evaluation.sh # programmatic step
# - { prompt: configs/eve/evaluation/<app>/prompt_assess,
# immutable: configs/eve/evaluation/<app>/immutable_assess } # judge step
failure_score:
score: 0.0
summary: evaluation failed
seed_solver_score: null
seed_solver_skip_evaluation: false
Shell evaluators receive these environment variables:
EVE_WORKSPACE_ROOT: workspace rootEVE_SOLVER_ROOT: solver candidate repo root, that is EVE_WORKSPACE_ROOT/solverEVE_EVAL_LOG_ROOT: formal evaluation log root, that is EVE_WORKSPACE_ROOT/logs/evaluateUse these paths directly in the shell file instead of reconstructing ad hoc paths.
EVE_WORKSPACE_ROOT, not EVE_SOLVER_ROOT or the downstream repo.EVE_EVAL_LOG_ROOT. This is the only interface that will be extracted.EVE_EVAL_LOG_ROOT/score.yaml is required.score.yaml rules:
score.yaml must always exist.score: 0.0
summary: evaluation failed
You can store files of any format within the EVE_EVAL_LOG_ROOT directory, including multimedia
like images and videos. If your logging structure is complex, it is recommended to include a
README.md inside EVE_EVAL_LOG_ROOT to document the file organization and contents.
circle_packing ships both forms:
configs/eve/evaluation/circle_packing.yaml
pointing at configs/eve/evaluation/circle_packing/evaluation.sh.configs/eve/evaluation/circle_packing.judge.yaml
(performance.sh -> assess -> aggregate), with prompt/immutable dirs under
configs/eve/evaluation/circle_packing/.