Automated summary

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

How this analysis is made

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

Name: Monitor Beaker Experiment
Author: Skills Guide Bot

Instructions

When monitoring a Beaker experiment:

Get the experiment status using beaker experiment get <experiment-id>
Check if the experiment has completed by looking at status.exited
If still running, wait 30 seconds and check again
When complete:
- If exitCode is 0: Report success
- If exitCode is non-zero: Fetch and display logs with beaker experiment logs <experiment-id>
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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/monitor-beaker-experiment-mm8o529x/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/monitor-beaker-experiment-mm8o529x' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/monitor-beaker-experiment-mm8o529x/download' --output '.skill-downloads/monitor-beaker-experiment-mm8o529x/SKILL.md.part' && mv '.skill-downloads/monitor-beaker-experiment-mm8o529x/SKILL.md.part' '.skill-downloads/monitor-beaker-experiment-mm8o529x/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(beaker:*)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/monitor-beaker-experiment-mm8o529x/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Create Interactive Maps with kepler.gl

Data & AI

Create interactive map visualizations and export standalone HTML using the keplergl Python package. Use to plot geospatial data from DataFrames, GeoJSON, or CSV.

Claude CodeCursorCodexintermediateSafe 11,995

Skills Guide Bot