Skip to content

skill-registry.md

Latest commit

 

History

History
71 lines (56 loc) · 2.66 KB

skill-registry.md

File metadata and controls

71 lines (56 loc) · 2.66 KB
Raw

Install skills with the shadcn CLI

Brigade's skills are published as a shadcn registry. The registry distributes skill files, the same way a component registry distributes components. remocn by kapishdima ships Remotion video components through this mechanism. Brigade ships agent skills through it.

Setup

Add the registry to components.json in your project (create the file if you do not have one):

{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "new-york",
  "tailwind": { "config": "", "css": "app.css", "baseColor": "neutral", "cssVariables": true },
  "aliases": { "components": "components", "utils": "lib/utils" },
  "registries": {
    "@brigade": "https://brigade.tools/r/{name}.json"
  }
}

Non-React and non-Node projects work. The CLI needs one more file, tsconfig.json, even when the payload is markdown:

{ "compilerOptions": { "baseUrl": "." } }

Install a skill

npx shadcn@latest add @brigade/check

This writes .claude/skills/check/SKILL.md. Claude Code discovers it on the next session. Available skills: check, refire, bug-hunt, latent-premises, retry-safety, reduce, taste.

If you run Brigade, project the skill into other harnesses afterward:

brigade skills import .claude/skills/check
brigade skills install check --target all

Brigade's own bundled skills use a separate canonical source identity. A named install such as brigade skills install brigade-work --target cursor resolves the current template shipped by the installed Brigade package. Use registry:brigade-work or an explicit path only when you intend to select a same-named local registry copy. brigade skills fleet status reports stale harness copies and the exact update command for each supported copy. If current metadata no longer supports an installed harness, it reports an uninstall command instead of recommending another install.

Use brigade skills sync --workspace . --target all --trust workspace to plan the complete registry-to-harness matrix without changing files. Add --write to install only missing or changed pairs at or above the trust floor. Sync uses explicit registry identities, so a same-named bundled skill cannot replace the reviewed registry source. Completed targets keep their receipts and rollback snapshots if another target fails.

What gets installed

One markdown file per skill, byte-identical to its source in escoffier-labs/skillet. No dependencies, no code execution, no config changes. Read the file before you adopt it, like anything else that instructs an agent.