Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →human-agent-society/running-coral-experiments
Run and manage CORAL experiments from the operator side — launch agents with `coral start` (dotlist overrides, model/count, tmux vs local), monitor with `coral status` / `coral log` / `coral show` / the web dashboard, and drive the loop with `coral resume` (inject instructions, fork from an attempt), `coral heartbeat` (tune reflection cadence), and `coral stop`.
Passed 20 of 22 test cases with the skill, and 5 of 22 without it.
and 20 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to open the web dashboard for my CORAL experiment to view the live leaderboard and DAG. However, the default port is in use, so I need it to run specifically on port 8420. What is the command?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the `coral ui` command. | Missed | Passed |
The instructions your model reads when the skill loads.
You drive a run with five verbs: start → status → log/show → resume → stop. Everything else is a flag on those or a deeper topic in the references. Prefer coral <cmd> --help over guessing flags.
Prereq: a task (task.yaml + seed/ + grader package) that passes coral validate .. No task yet → that's the creating-a-coral-task skill. Each runtime CLI must be installed and authenticated → the setting-up-coral skill.
coral start -c task.yaml # auto-tmux session
coral start -c task.yaml agents.count=4 agents.model=opus # dotlist overrides (no quotes needed)
coral start -c task.yaml run.verbose=true run.ui=true # verbose logs + web dashboard
coral start -c task.yaml run.session=local # foreground, no tmux
key.subkey=value) beat task.yaml for this run only — the clean way to sweep count/model without editing the file.run.session: tmux (default, detachable) · local (foreground) · docker.results/<task-slug>/<timestamp>/; agents work in isolated git worktrees and the grader daemon scores their commits.coral status # agent health + leaderboard snapshot (the quick pulse)
coral runs # active runs across tasks; --all includes finished
coral ui --port 8420 # web dashboard: live leaderboard, logs, DAG
coral status answers "who's alive, how many evals, current best". If it looks healthy but scores never move, jump to budget classes + troubleshooting in references/scaling-and-ops.md.
coral log # top 20 real attempts by score
coral log -n 5 --recent # most recent instead of best
coral log --search "kernel" --agent agent-1
coral log --class grader_error # surface crashing graders (first stop when unhealthy)
coral show <hash> # one attempt: score, explanation, files changed
coral show <hash> --diff # full diff — see exactly what the leader did
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.