Collections & sources

Collections

Collections group skills for curation and access. Use them to bundle what belongs together — a team's toolkit, a project's approved set, a topic.

• Manual collections are yours to arrange: add and remove skills freely.
• Source collections are created automatically by GitHub imports and track the repository they came from.

Collections also participate in access control: reviewers can be assigned per collection, and bundles can be downloaded per collection.

Connected agents can install a whole collection in one go: the workspace packs every Ready skill you have access to into a single download, one folder per skill. See Connect agents for how installs work.

In company Workspaces, only owners and admins create, rename, delete, or change membership for collections. Members can browse collections and use the skills they have access to.

Sources

Sources keep the provenance of imported skills — repository, branch, last commit and sync history — so you always know where a skill came from and can re-sync it. When the upstream repository changes, a re-sync imports the changes as new draft versions; nothing becomes Ready without going through the normal lifecycle.

Owners and admins can delete a source when they want to remove provenance and sync history. Deleting a source also removes its automatic source collection, but the imported skills stay in the workspace. Delete the skill itself only when the skill should be removed.