> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/agent-builder-and-skills/create-reusable-skills.md).

# Create reusable skills

A skill stores instructions for a recurring task. Create it once, then attach it to the agents that need the same guidance. A skill can also include reference files and required tools.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FGaA0HGPYksl6x3hJ93iD%2FG017.mp4?alt=media&token=ead5b3c6-555d-4786-96e2-915080ba2598>" %}

## Create a skill

Open **Skills → Custom → New skill**. Enter a name and a description that explain when the skill should be used.

![New custom skill name and description](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/rcdiXwhnpv8peNrZyeJk/assets/g017-g017-01-new-skill.png)

## Add supporting files

Use **Supporting Files** to add reference material. Read any tool dependency notice shown in the editor.

![Supporting Files and dependency notice](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/w7UjE1HUGpxCYCMGistF/assets/g017-g017-02-terminal-dependency.png)

Give each file a clear filename and write its content in the file editor.

![Supporting file name and editable content](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/fAgFxYjrv9O9iDUTtihO/assets/g017-g017-03-style-guide.png)

## Write the instructions

In **SKILL.md**, describe the required inputs, the steps to follow, and the expected result. Refer to supporting files by filename.

![SKILL.md instructions and file references](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/l7HkTiUeJAAQjTGn7OXD/assets/g017-g017-04-saved-skill.png)

## Start with instructions only

Supporting files are optional. For a first skill, write a self-contained procedure in **SKILL.md**:

```
When to use: The user asks to summarize supplied text.
Required input: The text to summarize.
Steps: Identify the main facts, preserve dates and amounts, and write three short bullets.
Missing input: Ask the user to provide the text.
Expected result: Three factual bullets without invented details.
```

Use the editor’s name and description fields to identify the skill and when it applies. Add supporting files when the procedure actually needs additional reference material.

## Save the skill

Select **Save**. The skill appears in the Custom catalog.

![Saved skill in the Custom catalog](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/ItkKtNmtj8hfjRlLLOTx/assets/g017-g017-05-catalog.png)

Open the saved skill to review or edit its instructions and files.

![Saved skill instructions and supporting files](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/JLdyv0vJzRG1lX5pNTDj/assets/g017-g017-06-style-guide.png)

## Important behavior

Saving a skill does not attach it to an agent. Follow [Attach skills and their tools to an agent](https://docs.stackai.com/guides-and-quickstarts/agent-builder-and-skills/attach-skills-and-their-tools-to-an-agent.md) to select it in a Workflow Builder AI Agent node. That guide explains the builder required for attachment.

A skill with supporting files can require the **Terminal** tool so the agent can read those files or run the commands its procedure requires while it works. This is a tool the agent uses, not a request for you to open a terminal on your computer. Configure the tools named in the dependency notice when attaching the skill.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/agent-builder-and-skills/create-reusable-skills.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
