Manage capa CLI configuration — capabilities.yaml / capabilities.json, skills, MCP servers, tools, hooks, sub-agents, rules, plugins, AGENTS.md / CLAUDE.md, security options, and tool exposure modes. Use whenever the user edits the capabilities file, runs any capa command (init, install, add, clean, sh, start/stop/restart/status, auth, upgrade, cache, registry), wires up an MCP server, adds a skill from GitHub / GitLab / a registry / a remote URL / a local path, configures secrets via ${VarName} placeholders, installs lifecycle hooks, defines sub-agents, or troubleshoots a failed install. Use even when the user only names a fragment ("add a skill", "wire up brave search", "block this phrase in skills") without saying "capa" — if a capabilities.yaml or capabilities.json lives at the project root, this is almost certainly the right skill. If the project does NOT yet have a capabilities file, point at the bootstrap skill instead.
$npx -y skills add infragate/capa --skill capabilities-managerInstalls into the current project.
Run `npx skills use "https://github.com/infragate/capa" --skill "infragate/capa/capabilities-manager"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/infragate/capa" that are relevant to the current task. Run `npx skills add "https://github.com/infragate/capa"` and select the relevant skills, then follow their instructions.