Stats
Actions
Tags
From babysitter
Assimilates external target (repo URL, harness name, or spec path) into babysitter process definitions with skills and agents using specialized workflows.
How this command is triggered — by the user, by Claude, or both
Slash command
/babysitter:assimilate Target to assimilate (e.g. repo URL, harness name, or spec path)This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
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: Run the process after formalizing it. Available assimilation workflows: - **methodology-assimilation** (`specializations/meta/assimilation/workflows/methodology-...
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.
npx claudepluginhub a5c-ai/babysitter --plugin babysitter/toolsImports skills and agents from GitHub repos into the resource registry, with support for selective add/remove/modify via prompt, and also lists registry tools and stats.
/exploreLoads and executes Hypo-Workflow skill instructions from a SKILL.md file, applying user-provided arguments. Includes discipline for asking questions and DeepSeek tool calling rules.
/methodologyManages development methodologies — list available, show current/info, activate/use one, compose multiple, or deactivate. Dispatches to methodology.sh shell script.
/claude-code-plugin-helpDisplays the unabridged reference for Claude Code 2026 runtime, covering Unified Skills Protocol, skill directory structure, front matter schema, and execution modes.