Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/monitor-experiment
Monitor running experiments, check progress, collect results.
Passed 12 of 18 test cases with the skill, and 10 of 18 without it.
and 1 more in the full report
4 fixed11 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
When presenting the evaluation summary of our new model against the reference model, what exact status string is assigned to completed runs in the summary comparison table?
| Checked | Without skill | With skill |
|---|---|---|
| Uses 'done' in the status column for completed experiment runs | Missed | Passed |
The instructions your model reads when the skill loads.
Monitor: $ARGUMENTS
ssh <server> "screen -ls"
For each screen session, capture the last N lines:
ssh <server> "screen -S <name> -X hardcopy /tmp/screen_<name>.txt && tail -50 /tmp/screen_<name>.txt"
If hardcopy fails, check for log files or tee output.
ssh <server> "ls -lt <results_dir>/*.json 2>/dev/null | head -20"
If JSON results exist, fetch and parse them:
ssh <server> "cat <results_dir>/<latest>.json"
Present results in a comparison table:
| Experiment | Metric | Delta vs Baseline | Status |
|-----------|--------|-------------------|--------|
| Baseline | X.XX | — | done |
| Method A | X.XX | +Y.Y | done |
test cases passed, vs 10 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.