Skip to main content
A kit bundles skills under one name. Publish your team’s baseline into @acme/ai-team, and everyone installs the whole set with a single command:
Kits share the @org/slug namespace with skills, so add resolves the name to a skill or a kit automatically — nobody needs to know which it is.

​
What kits are for

  • Onboarding sets — everything a new teammate’s agent should know, in one install.
  • Stack bundles — a nextjs kit, a data-pipeline kit, a qa kit.
  • Team baselines — conventions and checklists every member should run with.

​
The rules

  • Every active member sees every kit in the organization, just as they see every skill.
  • Kits never grant access. A private skill inside a kit stays governed by org membership; installing a kit installs only the skills you’re entitled to see.
  • Any active member can create and curate kits — add or remove skills, from the CLI or the panel. Deleting (archiving) a kit requires an admin or the owner, and never touches the skills inside it.
  • A kit and a skill cannot share a slug — creation fails with slug_taken if the name is taken.

​
Working with kits

Through your agent — “bundle these three into an ai-team kit”, “install the frontend kit” — or directly:
Publishing straight into a kit is one flag: masterskills publish <path> --group ai-team creates the kit if it doesn’t exist yet. Full command reference: masterskills kit.