monitor-experiment
FeaturedMonitor running experiments, check progress, collect results. Use when user says "check results", "is it done", "monitor", or wants experiment output.
Install
Quality Score: 96/100
Skill Content
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
monitor-experiment
Monitor running experiments, check progress, collect results. Use when user says "check results", "is it done", "monitor", or wants experiment output.
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).
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.