Managing skills

Once skills exist in your catalog, managing them is about deciding which ones are reachable, at which scope, and by which agents. This page covers enabling, importing, versioning, and attaching.

Browse and scope the catalog

Open /a/<account>/settings/skills. The catalog lists every skill you can see across scopes — system, account, project, user, and agent — with filters for scope, body kind, and source. A skill authored at a narrower scope shadows a same-named one above it; toggle Show shadowed to see what a given skill is overriding.

Choose the scope when you create or import a skill:

• Account — shared across the whole organization.
• Project — visible only inside one project.
• User — a personal draft nobody else sees.

Promote a skill to a broader scope when it is ready; promotion copies it into the target scope and leaves the original in place.

Import from GitHub or npm

Use Import skills to pull a bundle from a public GitHub repository or an npm package:

1. Pick the source and pin a ref (a commit SHA or tag for GitHub, an exact version for npm).
2. Preview the parsed skills and select the subset to bring in.
3. Choose the destination scope and apply.

Imported skills are pinned to that ref. When the upstream publishes a new version, the dashboard surfaces an update banner with a side-by-side diff so you can pull, skip, or unpin per skill. To customise an imported skill, fork it into your account scope — the fork is independent of future upstream changes.

Control which skills agents can reach

Two account-level controls gate the catalog:

• A denylist blocks a specific skill even when it would otherwise be in scope.
• An allowlist, once it has any entries, switches the account to allow-only mode — agents can reach only the listed skills.

Resolution order is denylist first, then allowlist, then scope shadowing. Use these to keep, say, a shell-running skill out of reach for a team that shouldn't have it.

Attach a skill to an agent

Open the agent's Skills tab and enable the skills it may call. Agents default closed, so a skill in the catalog is not callable until it is both in scope and attached here. Every invocation is audited and metered against the account.

Where to go next

• Authoring a skill to create or edit the skills you manage here.
• Create an agent to attach skills and run it.