coval-aicoval-ai/coval-external-skills/skills/simulations/get-results/SKILL.md

get-results

Skill3 starsChanged 17 days agoMITView on GitHub

Retrieve and analyze simulation results from a Coval run. Use when user wants to review evaluation outcomes or debug agent behavior.

In this repository33 other files it gives its agents.
- setup-agentSkill
- build-dashboardSkill
- coval-calibrate-metricSkill
- coval-compare-runsSkill
- coval-discover-failuresSkill
- coval-eval-auditSkill
- coval-evals-as-codeSkill
- coval-eval-startSkill
- review-llm-annotations-and-improve-promptSkill
- configure-metricsSkill
- migrate-bluejaySkill
- onboardSkill
- coval-resourcesSkill
- design-personaSkill
- personas-from-artifactsSkill
- analyze-accent-reportSkill
- analyze-adversarial-reportSkill
- analyze-audio-quality-reportSkill
- launch-runSkill
- quick-evalSkill
- run-accent-testingSkill
- run-adversarial-testingSkill
- run-audio-quality-testingSkill
- watch-runSkill
- download-audioSkill
- consult-sofiaSkill
- build-test-suiteSkill
- distill-test-setSkill
- huggingface-importSkill
- configure-trace-metricsSkill
- debug-tracesSkill
- optimize-trace-observabilitySkill
- setup-tracingSkill

The file

Create a free account to mount

Files

SKILL.md

Get Simulation Results

Retrieve results for $ARGUMENTS.

Workflow

If Run ID Provided

List all simulations for the run:

coval simulations list --run-id <run_id> --format json

If Simulation ID Provided

Get detailed simulation data:

coval simulations get <simulation_id> --format json

This returns:

Status (COMPLETED, FAILED)
Test case ID
Transcript (conversation history)
Timestamps
Error message (if failed)

Step 2: Analyze Results

For each simulation, extract:

Field	Description
`status`	COMPLETED or FAILED
`test_case_id`	Which test case was run
`transcript`	Full conversation
`has_audio`	Whether audio is available
`error_message`	Failure reason (if any)

Step 3: Present Summary

## Results for Run <run_id>

| Simulation | Status | Test Case | Audio |
|------------|--------|-----------|-------|
| sim_abc123 | COMPLETED | tc_xyz | Yes |
| sim_def456 | FAILED | tc_uvw | No |

### Failed Simulations
- sim_def456: "Connection timeout"

### View Details
`coval simulations get <sim_id>`

### Download Audio
`coval simulations audio <sim_id> -o output.wav`

Filtering

List simulations with filters:

coval simulations list --run-id <run_id> --filter "status=FAILED"
coval simulations list --run-id <run_id> --filter "has_audio=true"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free