Skills and workers
Package tools as declared skills and route them to bounded language-specific runtimes.
Skill manifests
Each skill is described by `skill.json`, including its inputs, runtime, resource needs, and requested capabilities. Discovery validates manifests and tracks content with BLAKE3 checksums.
Execution runtimes
- Node.js for the broad TypeScript skill catalog
- Python for research, data, and quantum integrations
- WASM through Wasmtime and WASI Preview 1
- Native Rust named operations for trusted system work
Discovery and validation
Startup scanning and file watching discover skill manifests. Validation rejects malformed declarations before registration, and BLAKE3 content checksums make changed packages visible to the Skill Book.
Worker boundaries
Workers receive only the task payload and capabilities resolved for that execution. Health checks report the ledger head, build checksum, and configuration version; mismatches quarantine a worker and prevent new task assignment.
Authoring paths
- Use Node.js or Python for broad ecosystem access and rapid iteration
- Use WASM for portable sandboxed skills with explicit WASI access
- Use native Rust named operations only for trusted work that needs tight core integration
- Migrate a skill without changing its manifest-level contract where possible
Refresh the Skill Book
The active Skill Book can be rebuilt after manifests change. File watching keeps the registry synchronized during development.
carnelian skills refresh