Installation and updates
Install a versioned release without repository access, verify its checksum, and pin it in automation.
Homebrew on macOS
Homebrew is the recommended path on macOS. It installs the current version and upgrades it with everything else on your machine.
brew install vulk-corp/tap/bworlds
bworlds --versionHomebrew verifies the release checksum before it installs. The tap is a public repository that carries the formula only.
Upgrade with the rest of your tools:
brew upgradeA package install cannot write into your home directory, so it installs no skills. Add them once, as the formula tells you after installing:
npx skills add https://docs.bworlds.co/bworlds-cli-SKILL.md -g
npx skills add https://docs.bworlds.co/bworlds-audit-SKILL.md -g
npx skills add https://docs.bworlds.co/bworlds-check-SKILL.md -gThat command keeps one copy under $HOME/.agents/skills, which most coding agents read directly, and links it into the directory each remaining agent uses.
Installer script
Use the script on Linux, in automation, and on macOS without Homebrew. Download it from this site, inspect it if your organization requires it, then run it:
curl -fsSLO https://docs.bworlds.co/install.sh
less install.sh
sh install.shThe installer downloads one archive and the release's checksums.txt, verifies SHA-256 before extraction, and installs the bworlds executable and the three skills. It supports:
| Operating system | Architecture | Archive suffix |
|---|---|---|
| macOS | Apple silicon | darwin-arm64 |
| macOS | Intel | darwin-amd64 |
| Linux | x86-64 | linux-amd64 |
It installs into $HOME/.local/bin by default and tells you when that directory is not on your PATH. Set BWORLDS_INSTALL_DIR to choose another directory.
The skills
The installer writes each skill to $HOME/.claude/skills/<name>/SKILL.md, where a local coding agent reads it without any copy step: bworlds-cli for the command contract, bworlds-audit to audit a Build end to end, and bworlds-check for a recurring health check. Set BWORLDS_SKILL_DIR when your agent reads skills from another directory.
Pin a version
Homebrew always installs the newest published version. Automation should pin one instead, which the script does:
BWORLDS_VERSION=0.1.0-preview.1 sh install.shRun bworlds --version after installation. The same version appears at the top of the CLI command reference and in the cliVersion field of /command-reference.json.
Update
brew upgrade bworlds moves a Homebrew install to the newest published version. With the script, run it again with a newer explicit BWORLDS_VERSION; it replaces both the executable and the skills. Your sign-in survives either path. Review the generated reference for the new version before changing the pinned version in automation.