How do I install the Babysitter Codex skill?

Run npx skillmds add majiayu000/babysitter-codex in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Babysitter Codex safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Babysitter Codex?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Babysitter Codex free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Babysitter Codex?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Babysitter Codex by majiayu000 — Agent Skill

Name: Babysitter Codex
Rating: 4.2 (5 reviews)
Author: majiayu000

Babysitter Codex

Orchestrate complex, multi-step AI workflows with quality convergence loops, event-sourced state, and human-in-the-loop approval gates. Use when the user wants to babysit a task, orchestrate a workflow, run quality-gated development, resume a previous orchestration run, diagnose run health, plan without executing, set up a project or user profile for babysitter, or assimilate an external methodology. Also use when the user mentions "babysitter", "orchestrate", "babysit", "quality loop", or "convergence loop".

majiayu000 a6429da 2 files · 4.2 KB Updated Sep 9, 2026 567 repo stars

File contents

Babysitter for Codex CLI

Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval gates.

Choosing a Mode

Based on the user's request, read the appropriate sub-skill from .codex/skills/babysitter/<mode>/SKILL.md (relative to this skill's install directory) and follow its instructions.

User intent	Mode	Sub-skill to read
Start an orchestration run (default)	call	`call/SKILL.md`
Run autonomously, no interaction	yolo	`yolo/SKILL.md`
Resume an existing run	resume	`resume/SKILL.md`
Plan a workflow without executing	plan	`plan/SKILL.md`
Start a never-ending periodic run	forever	`forever/SKILL.md`
Diagnose run health	doctor	`doctor/SKILL.md`
Launch observer dashboard	observe	`observe/SKILL.md`
Analyze previous run improvements	retrospect	`retrospect/SKILL.md`
Set or view model routing policy	model	`model/SKILL.md`
Work directly from a GitHub issue	issue	`issue/SKILL.md`
Help and documentation	help	`help/SKILL.md`
Onboard a project	project-install	`project-install/SKILL.md`
Install team-pinned setup	team-install	`team-install/SKILL.md`
Set up user profile	user-install	`user-install/SKILL.md`
Assimilate external methodology	assimilate	`assimilate/SKILL.md`

If unclear, default to call/SKILL.md.

SDK CLI Quick Reference

The babysitter SDK CLI (babysitter or npx @a5c-ai/babysitter-sdk) drives all orchestration:

babysitter run:create   --process-id <id> --entry <path>#<export> ...
babysitter run:iterate  <runDir> --json --iteration <n>
babysitter run:status   <runDir> --json
babysitter task:list    <runDir> --pending --json
babysitter task:post    <runDir> <effectId> --status ok --value <file> --json

Compatibility levels:

Core required: run:create, run:iterate, run:status, task:list, task:post
Optional advanced: session:*, profile:*, skill:*, health

If advanced commands are missing, continue in compat-core mode and do not block orchestration.

Canonical argument shapes (current Babysitter SDK)

run:status <runDir> --json
task:list <runDir> --json
session:init --session-id <id> --state-dir .a5c --json
session:associate --session-id <id> --state-dir .a5c --run-id <runId> --json
hook:log --hook-type <type> --log-file .a5c/logs/hooks.jsonl --json

Result Posting Protocol

Write result value to tasks/<effectId>/output.json
Post: babysitter task:post <runDir> <effectId> --status ok --value tasks/<effectId>/output.json
Never write result.json directly -- the SDK owns that file.

Hook-Driven Loop

After each effect is posted, stop the session. The stop hook re-invokes Codex to continue the next iteration. Do not loop within a single session.

---name: babysitter-codexdescription: Orchestrate complex, multi-step AI workflows with quality convergence loops, event-sourced state, and human-in-the-loop approval gates. Use when the user wants to babysit a task, orchestrate a workflow, run quality-gated development, resume a previous orchestration run, diagnose run health, plan without executing, set up a project or user profile for babysitter, or assimilate an external methodology. Also use when the user mentions "babysitter", "orchestrate", "babysit", "quality loop", or "convergence loop".--- # Babysitter for Codex CLI Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval gates. ## Choosing a Mode Based on the user's request, read the appropriate sub-skill from `.codex/skills/babysitter/<mode>/SKILL.md` (relative to this skill's install directory) and follow its instructions. | User intent | Mode | Sub-skill to read | |-------------|------|-------------------| | Start an orchestration run (default) | call | `call/SKILL.md` | | Run autonomously, no interaction | yolo | `yolo/SKILL.md` | | Resume an existing run | resume | `resume/SKILL.md` | | Plan a workflow without executing | plan | `plan/SKILL.md` | | Start a never-ending periodic run | forever | `forever/SKILL.md` | | Diagnose run health | doctor | `doctor/SKILL.md` | | Launch observer dashboard | observe | `observe/SKILL.md` | | Analyze previous run improvements | retrospect | `retrospect/SKILL.md` | | Set or view model routing policy | model | `model/SKILL.md` | | Work directly from a GitHub issue | issue | `issue/SKILL.md` | | Help and documentation | help | `help/SKILL.md` | | Onboard a project | project-install | `project-install/SKILL.md` | | Install team-pinned setup | team-install | `team-install/SKILL.md` | | Set up user profile | user-install | `user-install/SKILL.md` | | Assimilate external methodology | assimilate | `assimilate/SKILL.md` | If unclear, default to `call/SKILL.md`. ## SDK CLI Quick Reference The babysitter SDK CLI (`babysitter` or `npx @a5c-ai/babysitter-sdk`) drives all orchestration: ``` babysitter run:create --process-id <id> --entry <path>#<export> ... babysitter run:iterate <runDir> --json --iteration <n> babysitter run:status <runDir> --json babysitter task:list <runDir> --pending --json babysitter task:post <runDir> <effectId> --status ok --value <file> --json ``` Compatibility levels: - Core required: `run:create`, `run:iterate`, `run:status`, `task:list`, `task:post` - Optional advanced: `session:*`, `profile:*`, `skill:*`, `health` If advanced commands are missing, continue in `compat-core` mode and do not block orchestration. ### Canonical argument shapes (current Babysitter SDK) - `run:status <runDir> --json` - `task:list <runDir> --json` - `session:init --session-id <id> --state-dir .a5c --json` - `session:associate --session-id <id> --state-dir .a5c --run-id <runId> --json` - `hook:log --hook-type <type> --log-file .a5c/logs/hooks.jsonl --json` ## Result Posting Protocol 1. Write result value to `tasks/<effectId>/output.json` 2. Post: `babysitter task:post <runDir> <effectId> --status ok --value tasks/<effectId>/output.json` 3. Never write `result.json` directly -- the SDK owns that file. ## Hook-Driven Loop After each effect is posted, stop the session. The stop hook re-invokes Codex to continue the next iteration. Do not loop within a single session.

Frequently asked questions