// Assimilate an external methodology, harness, or specification into babysitter process definitions with skills and agents.
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.)
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.)
Clean up .a5c/runs and .a5c/processes directories. Aggregates insights from completed/failed runs into docs/run-history-insights.md, then removes old run data and orphaned process files.
Submit feedback or contribute to babysitter project
manage babysitter plugins. use this command to see the list of installed babysitter plugins, their status, and manage them (install, update, uninstall, list from marketplace, add marketplace, configure plugin, create new plugin, etc).
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.)
| name | assimilate |
| description | Assimilate an external methodology, harness, or specification into babysitter process definitions with skills and agents. |
Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
Use the assimilation domain processes from the active process library to convert external sources into well-defined babysitter process definitions with accompanying skills/ and agents/ directories.
If the workspace does not already have an active process-library binding, initialize it first through the shared global SDK binding:
babysitter process-library:active --json
Run the process after formalizing it.
Available assimilation workflows:
specializations/meta/assimilation/workflows/methodology-assimilation) - Learns an external methodology from its repo and converts procedural instructions, commands, and manual flows into babysitter processes with refactored skills and agents. Supports output as methodology or specialization.specializations/meta/assimilation/harness/*) - Integrates babysitter SDK with a specific AI coding harness (generic, codex, opencode, gemini-cli, openclaw, antigravity).During the interview phase, determine which assimilation workflow to use based on the user's target:
After successfully assimilating a methodology or harness integration, prompt the user to share it with the community. The assimilated process definitions, skills, and agents could benefit other babysitter users:
/babysitter:contrib library contribution: assimilated [methodology-name] into babysitter process definitions/babysitter:contrib library contribution: [harness-name] harness integration/babysitter:contrib bug report: assimilation of [target] failed because [description] or /babysitter:contrib feature request: [what the SDK needs to support]Even just reporting that an assimilation didn't work well helps improve babysitter for everyone.