> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Workspace skills

> Choose which Guild skills agents in a workspace can load. Attach private skills to the workspaces that need them, and see which skills are account-wide.

The **Skills** page lists the [skills](https://docs.guild.ai/platform/skills.md) that agents in a workspace can find and load. Open the workspace and click **Skills** under **Setup**.

A skill is available in a workspace when the workspace's account owns it and either:

* it's attached to this workspace, or
* it's public, which makes it **account-wide**: available in every workspace the account owns.

Agents can't see a private skill that isn't attached here. It's missing from `skills_search`, `skills_activate` refuses it, the `/` picker in [workspace chat](https://docs.guild.ai/platform/sessions.md#skill-mentions) leaves it out, and a [Goose recipe](https://docs.guild.ai/guide/goose-agents.md#skills) that declares it doesn't get it.

To attach a skill:

1. Open the workspace and click **Skills** under **Setup**.
2. Click **Add skill**.
3. Search your account's skills and select the one to add.

The **Workspace skills** table lists each attached skill, its **Availability** (**Workspace** or **Account-wide**), and who added it. To detach a skill, click **Remove skill** on its row. Removing a skill from one workspace doesn't affect its other attachments, and an account-wide skill stays available after removal.

You can attach one skill to several workspaces. Anyone who can edit the workspace can attach and remove skills; you don't need to be an organization admin.

> [!NOTE]
>
> Removing a skill blocks later lookups. It doesn't erase a skill body that a running session has already loaded. End or restart those sessions if the content must be gone.

## Manage attachments with the API

You can also list, attach, and remove skills through the API:

* [List the skills attached to a workspace](https://docs.guild.ai/api-reference/workspaces/list-the-skills-attached-to-a-workspace.md)
* [Attach a skill to a workspace](https://docs.guild.ai/api-reference/workspaces/attach-a-skill-to-a-workspace.md)
* [Detach a skill from a workspace](https://docs.guild.ai/api-reference/workspaces/detach-a-skill-from-a-workspace.md)

## Make a skill account-wide

To make a skill available in every workspace without attaching it, make it public with `guild skill update <identifier> --public`. For an organization-owned skill, only an organization admin can do this. Making a skill public is permanent, and public skills are visible to all Guild users. See [Skill settings](https://docs.guild.ai/platform/skills.md#settings).

## Related pages

* [Skills](https://docs.guild.ai/platform/skills.md) for creating, versioning, and archiving skills
* [Manage skills with the CLI](https://docs.guild.ai/cli/skills.md)