monitor-experiment

Featured

Monitor running experiments, check progress, collect results. Use when user says "check results", "is it done", "monitor", or wants experiment output.

AI & Automation 16,018 stars 1375 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Monitor Experiment Results > ⏱ **External cadence is appropriate here.** This skill waits on an external > fact (job completion / progress), so it is a natural `/loop` / `CronCreate` > surface: the wake reads status and self-judges only **machine-checkable** > completion (exit code, file exists, epoch logged) — never quality. This is > the additive external-wait shape in > [`shared-references/external-cadence.md`](../shared-references/external-cadence.md). > If a scheduled wait here ends in a verdict step (e.g. then audit results), > run that verdict **once** after the wait clears — not re-entered per tick. Monitor: $ARGUMENTS ## Workflow ### Step 1: Check What's Running **SSH server:** ```bash ssh <server> "screen -ls" ``` **Vast.ai instance** (read `ssh_host`, `ssh_port` from `vast-instances.json`): ```bash ssh -p <PORT> root@<HOST> "screen -ls" ``` Also check vast.ai instance status: ```bash vastai show instances ``` **Modal** (when `gpu: modal` in CLAUDE.md): ```bash modal app list # List running/recent apps modal app logs <app> # Stream logs from a running app ``` Modal apps auto-terminate when done — if it's not in the list, it already finished. Check results via `modal volume ls <volume>` or local output. ### Step 2: Collect Output from Each Screen For each screen session, capture the last N lines: ```bash ssh <server> "screen -S <name> -X hardcopy /tmp/screen_<name>.txt && tail -50 /tmp/screen_<name>.txt" ``` If hardcopy fails, check for log file...

Details

Author
wanshuiyin
Repository
wanshuiyin/Auto-claude-code-research-in-sleep
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

monitor-experiment

Monitor running experiments, check progress, collect results. Use when user says "check results", "is it done", "monitor", or wants experiment output.

2 Updated 1 months ago
wookat
Data & Documents Listed

monitor-ci

Drive a long-running GitHub Actions run to a trustworthy conclusion without burning the session on polling. Use when asked to wait for a pipeline, watch a build, babysit a release or deploy run, restart it if it fails, or report whether it went green. Also use when a run must finish before a follow-up step such as a push, a tag, or a dependent job in another repository. Covers confirming the run is the intended one, bounded waiting instead of open-ended blocking, reading the real per-job outcome rather than the summary icon, extracting facts from logs without matching the workflow's own echoed source, and deciding between a re-run of failed jobs and a fresh dispatch. Do NOT use for authoring or debugging workflow YAML, for proving that a green result was capable of failing (that is prove-checks), or for reviewing pull request feedback (that is babysit-pr).

5 Updated today
sergeyklay
AI & Automation Listed

monitor-agent-thread

Monitor a live or recent Claude Code or Codex thread from the other product using local append-only session logs, safe event extraction, Git/worktree evidence, and recurring heartbeats. Use when the user asks to watch, babysit, follow, monitor, check progress on, or notify them about another Claude Code/Codex session, including Claude-to-Codex and Codex-to-Claude monitoring.

0 Updated 4 days ago
BryceEWatson