Documentation
the Aviary
Install and publish community Feathers through the toowl registry.
the Aviary is toowl's Feather registry. First-party Feathers ship
built in; additional Feathers install into ~/.config/toowl/plugins/.
List available Feathers
bash scripts/feather-list.sh Install a Feather
# From the monorepo checkout (dev)
bash scripts/feather-install.sh nest
# From the remote catalog (sha256-pinned; prefers per-feather release tarball)
bash scripts/feather-install.sh --remote mcp
When a catalog entry includes archive.url, --remote downloads only that
release tarball (not the full monorepo). Checksums are verified against archive.sha256
and the directory hash in the catalog.
Verify the catalog
bash scripts/feather-verify.sh
bash scripts/feather-sign.sh # maintainers: sign registry with minisign
Remote installs optionally verify feather-registry.minisig when
scripts/feather-registry.pub is present and minisign is installed.
Scaffold a new Feather
bash scripts/feather-new.sh my-feather python
bash scripts/feather-new.sh my-feather node
bash scripts/feather-new.sh my-feather rust Publish to the Aviary
- Implement your Feather (subprocess or in-process PR to toowl).
- Add an entry to
scripts/feather-registry.jsonand refresh checksums:bash scripts/feather-checksums.sh. - Run
bash scripts/feather-submit.sh <id>locally. - Open a PR; maintainers attach release tarballs and sign the registry.
Trust model
- The registry JSON is pinned by
scripts/feather-registry.sha256. - Each installable Feather directory has a matching
sha256in the catalog. - Maintainers may additionally sign the registry with minisign (
feather-registry.minisig).
Questions? Open an issue on GitHub.