# Bootstrap

Capify an existing project.

- Repository: https://github.com/infragate/capa (719 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add infragate/capa --skill bootstrap -g -a claude-code -y`
Codex: `npx skills add infragate/capa --skill bootstrap -g -a codex -y`
Cursor: `npx skills add infragate/capa --skill bootstrap -g -a cursor -y`
Gemini CLI: `npx skills add infragate/capa --skill bootstrap -g -a gemini-cli -y`

## Description

Capify an existing project. Scans the repo for already-installed MCP servers, skills, rules, hooks, sub-agents, and plugins (across .claude, .cursor, .codex, .gemini, etc.), consolidates them into shared top-level directories (skills/, rules/, hooks/), and synthesizes a sound capabilities.yaml from the inventory. Use whenever the user says "bootstrap capa", "capify this project", "onboard capa onto an existing repo", "inventory my agent setup", or asks how to turn an ad-hoc Claude/Cursor/Codex configuration into a capabilities file. Use even when the user only mentions one provider, discovery should still sweep all of them.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Bootstrap

Turn an existing project that has accumulated MCP servers, skills, rules, hooks, and sub-agents across several provider-specific directories into a clean, reproducible `capabilities.yaml` managed by capa.

## When to use

The user has a repo that already works with at least one AI coding agent (Claude Code, Cursor, Codex, Gemini, Copilot, etc.) but has never run `capa init`. They want capa to take over so the configuration is shared across providers and version-controlled in one place.

Trigger words and shapes: "bootstrap capa", "capify", "set capa up on this repo", "convert my .claude/.cursor config to capa", "I have a bunch of skills and rules already, onboard them".

If `capabilities.yaml` already exists at the repo root, this skill is the wrong tool, point the user at the `capabilities-manager` skill instead, which knows how to extend an existing file.

## How this relates to `capabilities-manager`

Bootstrap is the one-time on-boarding helper. It produces a `capabilities.yaml` from scratch. `capabilities-manager` is the long-term editor, adding skills, registering MCP servers, configuring hooks on an already-bootstrapped project. **Read `capabilities-manager` for schema details and YAML examples** rather than re-deriving them here; this skill focuses on discovery and migration, and defers all schema questions to it.

When you (the agent) need to know the exact shape of a `skills:` entry, a `hooks:` entry, the canonical event names, the difference between `@` and `::` in `def.repo`, or any other schema-level detail, load the `capabilities-manager` skill rather than guessing. Bootstrap calls schema decisions out by name, but never inlines the schema reference.

## The flow at a glance

The rest: https://github.com/infragate/capa/blob/HEAD/skills/bootstrap/SKILL.md