Monitor Beaker Experiment

VerifiedSafe

Poll the status of a Beaker experiment at regular intervals until it finishes. Reports success on exit code 0, otherwise fetches and displays the experiment logs for debugging.

Sby Skills Guide Bot
Data & AIIntermediate
706/2/2026
Claude Code
#beaker#experiment-monitoring#status-checking#log-retrieval

Recommended for

Our review

Monitor Beaker experiments until they finish, checking status and retrieving logs on failure.

Strengths

  • Automates periodic status checks of experiments.
  • Automatically fetches logs when an experiment fails.
  • Integrates seamlessly with Beaker CLI.

Limitations

  • Requires Beaker CLI installed and configured.
  • Does not handle parallel or complex experiment workflows.
  • Monitoring loop can be time-consuming without real-time updates.
When to use it

When you want to wait for a Beaker experiment to complete and need to be notified of its result without manual checks.

When not to use it

When you need to monitor multiple experiments concurrently or require real-time streaming of logs for active debugging.

Security analysis

Safe
Quality score90/100

The skill only uses read-only Beaker commands to monitor experiment status and retrieve logs. No destructive actions, exfiltration, or obfuscation. The allowed tool 'Bash(beaker:*)' limits execution to Beaker CLI, which is safe for this purpose.

No concerns found

Examples

Monitor until completion
Monitor experiment 01KCW39T5JBZTYV69BXHWJJ83P and tell me when it's done, including its exit status and logs if it failed.
Check status and logs on failure
Check the status of experiment 01KCW39T5JBZTYV69BXHWJJ83P. If it has failed, retrieve the logs and show them to me.
Stream logs in real-time
Stream the logs for experiment 01KCW39T5JBZTYV69BXHWJJ83P while it's running, and notify me when it completes.

category: Research id: monitor-experiment name: Monitor Experiment description: Monitor Beaker experiments until completion. allowed-tools: Bash(beaker:*)

Monitor Beaker Experiment

Instructions

When monitoring a Beaker experiment:

  1. Get the experiment status using beaker experiment get <experiment-id>
  2. Check if the experiment has completed by looking at status.exited
  3. If still running, wait 30 seconds and check again
  4. When complete:
    • If exitCode is 0: Report success
    • If exitCode is non-zero: Fetch and display logs with beaker experiment logs <experiment-id>
  5. Continue monitoring until the experiment finishes or the user asks you to stop

Examples

Check experiment status:

beaker experiment get 01KCW39T5JBZTYV69BXHWJJ83P

Get experiment logs on failure:

beaker experiment logs 01KCW39T5JBZTYV69BXHWJJ83P

Stream logs in real-time for running experiments:

beaker experiment logs --follow 01KCW39T5JBZTYV69BXHWJJ83P
Related skills