watch-run
Skill3 starsChanged 17 days agoMITView on GitHub
Monitor a Coval run's progress with live updates. Use when user wants to check run status or wait for completion.
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
- download-audioSkill
- get-resultsSkill
- consult-sofiaSkill
- build-test-suiteSkill
- distill-test-setSkill
- huggingface-importSkill
- configure-trace-metricsSkill
- debug-tracesSkill
- optimize-trace-observabilitySkill
- setup-tracingSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If no run ID provided, list recent runs:
- Distinctive: line 21
Ask user to select a run to watch.
- Distinctive: line 36
When the run completes, summarize:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Watch Coval Run Progress
Monitor the progress of run $ARGUMENTS.
Workflow
Step 1: Identify Run
If no run ID provided, list recent runs:
coval runs list --page-size 10Ask user to select a run to watch.
Step 2: Watch Progress
coval runs watch <run_id> --interval 2This displays a live progress bar showing:
- Completed / Total test cases
- Current status (PENDING, IN QUEUE, IN PROGRESS, COMPLETED, FAILED)
- Percentage complete
Step 3: Report Results
When the run completes, summarize:
coval runs get <run_id> --format jsonReport:
- Total simulations completed
- Pass/fail counts (if available)
- Duration
- Link to results
Options
| Flag | Description | Default |
--interval | Refresh rate in seconds | 2 |
Statuses
| Status | Meaning |
| PENDING | Run created, not yet queued |
| IN QUEUE | Waiting for capacity |
| IN PROGRESS | Simulations running |
| COMPLETED | All simulations finished |
| FAILED | Run encountered an error |
| CANCELLED | User cancelled the run |
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
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.