| name | evaluate-agent |
| description | Create the MAPS Evaluate phase artifact for an agent or multi-agent system. Use when designing scenario tests, eval datasets, rubrics, scorecards, regression checks, red-team prompts, safety checks, and release evidence. |
Evaluate Agent
Versioning
Current version: 0.1.0.
Follow semantic versioning for this skill:
- Patch: wording, examples, references, or small workflow clarifications.
- Minor: new outputs, new required steps, new helper behavior, or expanded workflow capability.
- Major: renamed outputs, changed artifact contracts, removed behavior, or incompatible workflow changes.
When changing this skill, update Current version and add a Changelog entry with the date, version, and short summary of behavior changed.
Changelog
- 2026-06-19 - v0.1.0 - Established the initial MAPS skill version baseline and changelog tracking.
Overview
Use this skill to prove agent behavior before release and create evidence for improvement.
Project foundation updates
At the start of every project run, look for project-foundation.md. If it exists, read Persistent Memory Contract and use its configured notes, sources, memory, RAG, and sync rules as the project defaults. If .maps/foundation-preferences.json exists, use it as the structured preference source for automation.
When this skill creates durable knowledge, write it through the shared MAPS memory helper. The helper gives this skill its own named note under the configured notes root, mirrors that note into the configured RAG location when one exists, appends MAPS Skill Run Log, and records a RAG reindex manifest.
At the end of the run, call the helper after creating the primary output artifact:
python "$CODEX_HOME/skills/foundation/scripts/maps_memory.py" complete-run --project . --skill /evaluate-agent --phase A5 --output "<primary artifact path>" --summary-file "<primary artifact path>" --memory-updates "<notes, sources, memory, or RAG updates>"
If the helper is unavailable, manually append the timestamp, skill, phase, output path, memory updates, and short note to project-foundation.md, then update this skill's named note in <notesRoot>/maps-runs/.
Required interview
Before writing evals or scorecards, ask for any missing answers. Do not create generic tests that are detached from the real agent job.
Ask exactly one question at a time. Do not present the user with a multi-question form, checklist, or table to fill out. Use the questions below as the internal interview sequence: ask the next most important missing question, wait for the answer, then continue.
Ask:
- Which agent, role, workflow, or release candidate is being evaluated?
- What success criteria, failure criteria, and release gates already exist?
- What real tasks or customer stories should become eval scenarios?
- What edge cases, unsafe requests, adversarial inputs, and escalation cases matter?
- What tools, memory, RAG, or human approvals need to be tested?
- What rubric or scoring style should be used?
- What minimum score or evidence is needed for release?
- What known failures need regression coverage?
- Should evals be runnable now, specified for later, or both?
- Who reviews the eval results and makes the go/no-go decision?
If the user does not have eval scenarios, draft candidates and ask for approval before treating them as the suite.
Workflow
- Restate the agent's success and failure criteria.
- Create common, edge, adversarial, and unsafe scenarios.
- Define expected behavior and scoring rubrics.
- Add regression cases for known failures.
- Include tool-use and escalation checks.
- Run or specify the evaluation process.
- Produce a scorecard and release recommendation.
Completion report
When the skill is complete, tell the user explicitly. Do not end with only files changed or raw output.
Report:
- Completion status: complete, blocked, or needs more answers.
- Outcome: the concrete artifact, decision, scaffold, implementation, or plan produced.
- Key decisions or changes made.
- Memory update: whether the shared MAPS memory helper ran, what note/run log was updated, and what RAG or notes locations need syncing.
- Next skill:
/deploy-agent when release evidence passes, or /improve-agent when failures need fixes before release.
If the skill is blocked, say what answer, artifact, access, approval, or tool is needed before the next skill can run.
Output
Return:
- Eval scenarios
- Rubric or scoring method
- Scorecard
- Failure categories
- Release recommendation
Use templates/eval-scorecard.md from the MAPS repo when working inside this repository.
Done Criteria
- Evals reflect real tasks.
- Risky behavior is tested.
- Results can guide go/no-go decisions.
- Failures feed the Improve phase.
