菜单
manage Babysitter blueprints. Use this command to list installed blueprints, browse marketplaces, install, update, uninstall, configure, or create a new blueprint.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/a5c-ai/babysitter-pi --skill blueprints命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| 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.