Collections
Syllago organizes content into three collection types, each serving a different role in your workflow. Your library holds content you own and manage directly. Registries connect you to shared content from teams or the community. Loadouts bundle content together so you can apply entire configurations at once.
Quick comparison
Section titled “Quick comparison”| Aspect | Library | Registries | Loadouts |
|---|---|---|---|
| Location | ~/.syllago/content/ | Git repos (cloned locally) | Defined in config |
| Access | Read-write | Read locally, contribute via PR | Apply/revert |
| Purpose | Your personal content | Shared team/community content | Bundled configurations |
| Key commands | add, install, list | registry add/sync/items | loadout create/apply/remove |
Library
Section titled “Library”Your personal content store at ~/.syllago/content/. This is where syllago manages the content you acquire from providers. You have full read-write access — add, edit, or remove content as needed.
syllago add --from <provider>syllago listsyllago install <name> --to <provider>Registries
Section titled “Registries”Git-based repositories of shared content maintained by teams or the community. You consume registry content locally and can contribute back via pull request using syllago publish.
syllago registry add <url>syllago registry syncsyllago registry itemsLoadouts
Section titled “Loadouts”Bundled sets of content — rules, skills, agents, hooks, MCP configs — that apply as a unit. Loadouts let you switch between configurations quickly, either temporarily for testing or permanently.
syllago loadout createsyllago loadout apply <name> --try # temporarysyllago loadout apply <name> --keep # permanentsyllago loadout remove <name>