القائمة
manage Babysitter blueprints. Use this command to list installed blueprints, browse marketplaces, install, update, uninstall, configure, or create a new blueprint.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Execute via @babysitter. Use this skill when asked to babysit a task, do anything that is structured process-driven (even a loop) or whenever it is called explicitly. (babysit, babysitter, with a process, orchestrate, orchestrate a run, workflow, loop until, etc.)
Orchestrate a babysitter run. use this command to start babysitting a complex workflow.
Pre-deploy gate that scans built JS chunks for forbidden substring markers (saga-era / obsolete code paths) listed in a project-local forbidden-markers.txt
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
Diagnose babysitter run health - journal integrity, state cache, effects, locks, sessions, logs, and disk usage
| name | blueprints |
| description | manage Babysitter blueprints. Use this command to list installed blueprints, browse marketplaces, install, update, uninstall, configure, or create a new blueprint. |
This command installs and manages Babysitter blueprints. A blueprint is a version-managed package of contextual instructions or deterministic Babysitter processes, not a conventional software plugin.
If the command is run without arguments, list installed blueprints with their name, version, marketplace, installation date, and last update date. Also list configured marketplaces and show how to add the default marketplace when none exist.
Blueprints can be installed at two scopes:
--global): stored under ~/.a5c/, available for all projects--project): stored under <projectDir>/.a5c/, project-specificMarketplaces are git repositories containing a marketplace.json manifest and blueprint package directories. The SDK clones new marketplaces to .a5c/blueprints/marketplaces/ for the selected scope and reads legacy .a5c/marketplaces/ clones for compatibility.
babysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] [--marketplace-branch <ref>] [--force] --global|--project [--json]
babysitter blueprints:update-marketplace --marketplace-name <name> [--marketplace-branch <ref>] --global|--project [--json]
babysitter blueprints:list-blueprints --marketplace-name <name> --global|--project [--json]
For blueprint:install, blueprint:update, blueprint:configure, and blueprint:list-blueprints, the --marketplace-name flag is auto-detected when only one marketplace is cloned for the selected scope.
babysitter blueprints:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
babysitter blueprints:update --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
babysitter blueprints:configure --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
babysitter blueprints:uninstall --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
The --plugin-name flag is preserved for CLI compatibility with existing marketplace manifests. User-facing docs should call the installable a blueprint.
babysitter blueprints:list-installed --global|--project [--json]
babysitter blueprints:update-registry --plugin-name <name> --plugin-version <ver> --marketplace-name <mp> --global|--project [--json]
babysitter blueprints:remove-from-registry --plugin-name <name> --global|--project [--json]
The old plugin:* commands remain available as deprecated aliases for one release. Prefer blueprint:* in new docs, skills, and process instructions.
Do not rename or reinterpret agent harness plugins while handling blueprints. CLAUDE_PLUGIN_ROOT, PI_PLUGIN_ROOT, .claude/plugins/, hooks-adapter, extensions-adapter, and agent plugin manifests stay plugin-specific.