monitor-experiment

Monitor Beaker experiments until completion with status, progress, and logs.

Updated Jan 13, 2014
One-click install
npx skills add https://github.com/finbarrtimbers/DotFiles --skill monitor-experiment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-experiment
Source: https://github.com/finbarrtimbers/DotFiles/tree/main/claude/skills/monitor-experiment
Command: npx skills add https://github.com/finbarrtimbers/DotFiles --skill monitor-experiment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps researchers and operators monitor Beaker experiments in real time, alerting you when status changes or completes.

Core Features & Use Cases

  • Real-time status: Retrieve and track current status, progress, and exit conditions.
  • Log access: Fetch and review logs on completion or failure to diagnose issues.
  • Cross-workspace monitoring: Apply checks across development and evaluation workspaces.

Quick Start

Use the monitor-experiment skill to start monitoring a Beaker experiment by ID (e.g., monitor-experiment <id>).

Frequently Asked Questions about monitor-experiment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track Beaker experiments to completion?

To track Beaker experiments, you use a monitoring Skill that retrieves real-time status, progress, and exit conditions via the Beaker CLI. It applies checks across development and evaluation workspaces until the experiment finishes.

What is the best way to monitor Beaker experiment status in real time?

Monitoring Beaker experiment status in real time involves extracting current status and exit conditions through JSON processing. This allows researchers and operators to receive alerts when an experiment changes state or completes.

Can I fetch Beaker logs on completion to diagnose experiment failures?

Yes, you can fetch and review Beaker logs on completion or failure to diagnose issues. The monitoring process extracts logs using JSON processing to help researchers identify what went wrong during the experiment.

Do I need the Beaker CLI to monitor experiments across workspaces?

Yes, the Beaker CLI is required to monitor experiments across common workspaces. The Skill relies on the CLI and JSON processing to extract status, progress, and logs from development and evaluation environments.

Does cross-workspace monitoring work for both development and evaluation Beaker experiments?

Cross-workspace monitoring works for both development and evaluation Beaker experiments. The Skill applies checks across these common workspaces to track status changes and alert you when experiments complete.