Pack Registry¶
The KruxOS pack registry is the community hub for discovering and installing capability packs.
Registry ships in v0.0.2
v0.0.1 supports local-path installs only (kruxos pack install ./path/to/pack). The community registry, kruxos pack search / kruxos pack info discovery surfaces, GitHub-based publishing flow, seed packs, and the standalone pack-sdk CLI all ship in v0.0.2. The rest of this page describes the v0.0.2 surface.
Browsing packs (v0.0.2)¶
CLI¶
Example output:
my-weather-pack v1.1.0
by github-user · MIT license
Weather data capabilities for KruxOS agents
Capabilities:
weather.current (autonomous) — Current weather for a location
weather.forecast (autonomous) — Multi-day weather forecast
Install: kruxos pack install my-weather-pack
Web¶
Browse the registry at packs.kruxos.com.
Registry architecture (v0.0.2)¶
The registry that ships in v0.0.2 is a GitHub repository acting as a package index:
graph LR
A[kruxos pack publish] --> B[GitHub API]
B --> C[Registry Repository]
C --> D[metadata.yaml per pack]
C --> E[Versioned archives]
F[kruxos pack install] --> C
This approach was chosen for v0.0.2 because:
- No infrastructure to host or maintain
- Built-in authentication via GitHub
- Pull requests for community review
- Git history for auditability
- Free and open
A dedicated hosted registry is on the longer-term roadmap.
OpenClaw compatibility¶
The KruxOS registry can index OpenClaw-compatible skills via the compatibility bridge:
The bridge automatically:
- Downloads the OpenClaw skill
- Wraps it with type inference
- Generates capability definitions
- Installs it as a regular pack
See Migration from OpenClaw for details.
Pack security¶
Verification¶
Every published pack includes a SHA-256 checksum. The CLI verifies integrity on install:
Downloading my-weather-pack v1.1.0...
✓ Checksum verified (sha256:abc123...)
✓ Installed 2 capabilities
Review process¶
Packs published to the community registry go through:
- Automated checks — schema validation, no name conflicts
- Community review — pull request on the registry repo
- Signature — author identity verified via GitHub
Secret safety¶
Pack implementations access secrets via the vault's use-not-read model. The secret value is injected into the execution environment — the pack code never sees the raw secret in a variable it could log or exfiltrate.