Documentation
Install Skillcrew, publish your team's skills from one registry, and keep every developer's agents in sync.
Getting started
- InstallInstall the skillcrew binary on macOS or Linux with Homebrew, the install script or Go.
- Create a registryCreate the Git repository that holds your organization's skills and governance, then publish it.
- Join as a developerRun one command to get your organization's and your teams' skills in every agent, kept up to date.
Concepts
- The registryOne Git repository per organization holds every skill and the rules that decide who gets which.
- StatusesEvery skill is required, recommended, available, deprecated or blocked, and the status decides where it is installed.
- Teams and resolution rulesHow organization rules, team rules and a developer's own choices combine into one status per skill.
- Security modelThe registry is your root of trust; Skillcrew copies files, executes nothing from it and stores no secrets.
Guides
- Private registriesUse a private registry over SSH or HTTPS with the Git credentials developers already have.
- Pin a skillHold a skill at a tag or a commit while the rest of the registry moves on.
- Propose a changeTurn your local edits to a team skill, or one of your personal skills, into a pull request on the registry.
- Convert a Claude Code marketplaceTurn an existing Claude Code marketplace repository into a Skillcrew registry with one command.
- Validate in CIRun skillcrew validate on every pull request so a broken registry never reaches developer machines.
Reference
- CLIEvery skillcrew command, its arguments, flags and JSON output.
- skillcrew.yamlFull reference of the governance file at the root of the registry, and of the per-machine config.yaml.
- Files on diskEvery file and directory Skillcrew reads or writes on a developer machine.
Troubleshooting
- Diagnose with doctorRun skillcrew doctor first, then use the table of symptoms and fixes.
- FAQShort answers about local edits, name collisions, pinning, project skills and uninstalling.