Collections
Organize your skills into subsets so each API key only sees what it needs.
What Are Collections?
A collection is a named API key with a filtered skill list. By default, an API key has access to all skills in your drive. A collection restricts that to only specific skills.
This is useful when you want different AI clients, projects, or environments to see different subsets of your library.
| Use Case | Example |
|---|---|
| Per-project filtering | A “data-science” collection with only analysis and visualization skills |
| Per-client environments | Give Claude Desktop a different set of skills than Cursor |
| Security scoping | Limit a shared key to only approved, safe skills |
Managing Collections in the Dashboard
The easiest way to work with collections is through the Collections button in your drive.
Open Collections
Click the “Collections” button in your drive to see all your collections and create new ones.
Pick your skills
Create a collection with a descriptive name (e.g. “Data Science”) and select which skills it should include from your drive.
Use the collection's API key
Each collection gets its own API key. Connect with that key and your client will only see the skills you selected.
Add or remove skills anytime
How Collections Affect What Your Agent Sees
Each API key maps to one collection. When a client connects with that key, it only sees skills in that collection's list.
Keys with no collection see all drive + team + shared skills. Keys with an empty collection see nothing.
Skills must be in your drive
Team & Shared Skill Toggles
By default, every collection includes skills from your personal drive, your teams, and skills shared with you. You can toggle each source independently per collection.
| Toggle | Default | Effect |
|---|---|---|
| Team skills | On | When on, the collection includes skills from all teams you belong to. Turn off to restrict to only your personal drive. |
| Shared skills | On | When on, the collection includes skills shared with you by other users. Turn off to exclude shared skills. |
Per-collection control
Managing Collections via Your Agent
Your AI agent can also create and manage collections through natural conversation. This is handy for quick adjustments without opening the dashboard.
| What you say | What happens |
|---|---|
| “Create a collection called Data Science with my CSV and visualization skills” | Agent creates a new API key scoped to those skills |
| “Add the regression skill to my Data Science collection” | Agent adds the skill to the existing collection |
| “Remove CSV parser from Data Science” | Agent removes the skill from the collection |
| “Rename my Data Science collection to ML & Analytics” | Agent renames the collection |
| “Disable team skills on my Data Science collection” | Agent sets includeTeamSkills to false |