How do I install the Blueprints skill?

Run npx skillmds@latest add a5c-ai/blueprints 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 Blueprints safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Blueprints?

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 Blueprints free to use?

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

Who published Blueprints?

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

Blueprints by a5c-ai — Agent Skill

Name: Blueprints
Rating: 4.2 (5 reviews)
Author: a5c-ai

File contents

blueprints

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 (--global): stored under ~/.a5c/, available for all projects
project (--project): stored under <projectDir>/.a5c/, project-specific

Marketplace Management

Marketplaces 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.

Add a marketplace

babysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] [--marketplace-branch <ref>] [--force] --global|--project [--json]

Update a marketplace

babysitter blueprints:update-marketplace --marketplace-name <name> [--marketplace-branch <ref>] --global|--project [--json]

List blueprints in a marketplace

babysitter blueprints:list-blueprints --marketplace-name <name> --global|--project [--json]

Blueprint Lifecycle

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.

Registry Management

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]

Deprecated Aliases

The old plugin:* commands remain available as deprecated aliases for one release. Prefer blueprint:* in new docs, skills, and process instructions.

Agent Plugins Are Separate

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.

---name: blueprintsdescription: manage Babysitter blueprints. Use this command to list installed blueprints, browse marketplaces, install, update, uninstall, configure, or create a new blueprint.---# blueprintsThis 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** (`--global`): stored under `~/.a5c/`, available for all projects- **project** (`--project`): stored under `<projectDir>/.a5c/`, project-specific## Marketplace ManagementMarketplaces 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.### Add a marketplace```bashbabysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] [--marketplace-branch <ref>] [--force] --global|--project [--json]```### Update a marketplace```bashbabysitter blueprints:update-marketplace --marketplace-name <name> [--marketplace-branch <ref>] --global|--project [--json]```### List blueprints in a marketplace```bashbabysitter blueprints:list-blueprints --marketplace-name <name> --global|--project [--json]```## Blueprint LifecycleFor `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.```bashbabysitter 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.## Registry Management```bashbabysitter 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]```## Deprecated AliasesThe old `plugin:*` commands remain available as deprecated aliases for one release. Prefer `blueprint:*` in new docs, skills, and process instructions.## Agent Plugins Are SeparateDo 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.

Frequently asked questions

Blueprints