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 vault packs every Ready skill you have access to into a single download, one folder per skill. See Connect agents for how installs work.

In Team and Enterprise Vaults, 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 check for changes. Check updates compares only skills already imported. Select the updates to save as new Drafts; checking does not add other skills from the repository or replace an open Draft. Nothing becomes Ready without the normal scan and approval lifecycle.

Automatic source checks run daily in batches. Sources and vault skill details show their last successful check and whether an update is available. Owners and admins receive one in-app alert for each changed package. Review updates shows added, changed and removed files at a fixed revision before you select what to import. Failed checks remain visible; they never delete saved packages or imply that a skill is up to date. See Marketplace and Notifications.

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 vault. Delete the skill itself only when the skill should be removed.