babysitter:observe
Launch the babysitter observer dashboard for real-time run monitoring.
Best use case
babysitter:observe is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Launch the babysitter observer dashboard for real-time run monitoring.
Teams using babysitter:observe should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/observe/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How babysitter:observe Compares
| Feature / Agent | babysitter:observe | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Launch the babysitter observer dashboard for real-time run monitoring.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# babysitter:observe Launch the babysitter observer dashboard — a real-time web UI for monitoring runs, tasks, journal events, and orchestration state. ## Usage ### Start the Dashboard 1. Determine the watch directory (usually the project's container directory or cwd) 2. Launch: ```bash npx -y @yoavmayer/babysitter-observer-dashboard@latest --watch-dir <dir> ``` 3. This is a **blocking process** — it will keep running until stopped 4. Open the browser at the URL printed by the dashboard ### Stop the Dashboard If the argument is `stop`: 1. Find the running dashboard process: ```bash ps aux | grep babysitter-observer-dashboard | grep -v grep ``` 2. Kill it: ```bash kill <pid> ``` 3. Confirm it stopped ### Default Watch Directory If no `--watch-dir` is specified, use the parent of the current project directory. For `/data/repos`, watch `/data`.
Related Skills
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
observe
Observe, inspect, or monitor a Babysitter run.
babysitter:assimilate
Assimilate an external methodology, harness, or specification into babysitter process definitions.
babysitter:forever
Start a never-ending babysitter run with infinite loops and sleep gates.
babysitter:doctor
Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage.
babysitter:team-install
Install or refresh a team-pinned babysitter runtime/content setup from lockfile.
babysitter:call
Start a babysitter orchestration run. Use this command to start babysitting a complex workflow.
babysitter:yolo
Start babysitting in non-interactive mode — no user interaction or breakpoints, fully autonomous execution.
babysitter:resume
Resume orchestrating an existing babysitter run.
babysitter:retrospect
Analyze a completed or in-flight run and propose process improvements for future runs.
babysitter:project-install
Set up a project for babysitting. Research the codebase, build project profile, install tools.
babysitter:user-install
Set up babysitter for yourself. Install deps, build user profile, configure tools.