Skip to main content
Kits turn “install these seven skills” into masterskills add @acme/ai-team. Any active member can build one. Concept details: Kits.

​
Through your agent

You: make a Next.js kit for the team from our frontend skills Agent: Proposal — create @acme/nextjs (private) with: @acme/nextjs-conventions · @acme/component-standards · @acme/review-checklist Create it? You: yes Agent: Done. Anyone on the team installs it with masterskills add @acme/nextjs.
The agent works out candidate skills from the catalog, shows the exact kit — namespace, slug, visibility, full skill list — and creates it only after you approve.

​
From the CLI

A kit holds 1–50 skills. If creation fails with slug_taken, the name already belongs to a skill or kit in that namespace — pick another slug.

​
Publish straight into a kit

Filing a skill into a kit at publish time is one flag:
--group (alias --kit) adds the published skill to the kit and creates the kit if it doesn’t exist. When an agent does this for you, the kit step always comes after the approved publish — never before.

​
Installing a kit

Installing a kit installs the skills you’re entitled to see; a kit never widens access. Deleting a kit (admin+) never touches the skills inside it.