# Collections

> Markdown variant of <https://www.skillzdrive.com/docs/guides/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.

1. **Open Collections** — click the **Collections** button in your drive to see all your collections and create new ones.
2. **Pick your skills** — create a collection with a descriptive name (e.g. "Data Science") and select which skills it should include from your drive.
3. **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.

You can update a collection's skill list at any time. Changes take
effect on the next connection — no need to regenerate the API key.

## 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.

```
API Key  →  Collection Filter  →  Filtered Skill List
```

Keys with no collection see all drive + team + shared skills. Keys
with an empty collection see nothing.

You can only add skills that are already in your drive. Import
marketplace skills first before adding them to a collection.

## 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. |

These toggles are set independently on each collection. Your drive
key always includes all sources. Use these toggles when you want a
collection that only exposes your personal skills — for example, to
keep a client-specific key isolated from team or shared content.

## 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 |

The agent uses these MCP tools:

- `skills_listCollections` — list owned collections (all-skills keys only).
- `skills_createCollection(name, skillSlugs?, includeTeamSkills?, includeSharedSkills?)`.
- `skills_updateCollection(collectionName, newName?, includeTeamSkills?, includeSharedSkills?)`.
- `skills_addToCollection(collectionName, skillSlug)` — single slug, not array.
- `skills_removeFromCollection(collectionName, skillSlug)` — single slug, not array.

Collections with `allowed_skill_ids=null` (all skills) reject
add/remove operations.

## Next steps

- [Teams](https://www.skillzdrive.com/docs/guides/teams.md): shared skill libraries for groups.
- [Sharing](https://www.skillzdrive.com/docs/guides/sharing.md): share individual skills with specific users.
- [Discovering skills](https://www.skillzdrive.com/docs/guides/discovering-skills.md).