> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/agents/skills.md).

# Skills

{% hint style="info" %}
This feature is currently in beta, with access limited to those participating in the beta.
{% endhint %}

Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.

### Creating Skills

The easiest way to create a Skill is with Assist Agent:

1. Work through a real issue or workflow.
2. Refine the investigation steps and desired output.
3. Ask Assist Agent to **turn this into a Skill**.
4. Review the generated instructions.
5. Attach the Skill to the agents that should use it.

You can also create a Skill from the [Skills page](https://app.usepylon.com/settings/ai-controls/skills) or import an existing skill markdown file from another AI tool.

<figure><img src="/files/YtFkhjaUsYwZBnW4HoaN" alt=""><figcaption></figcaption></figure>

### Using Skills

Once created, skills can be used across all of Pylon's agents:

* [Assist Agent](https://support.usepylon.com/articles/8245939244-how-does-the-assist-agent-work?lang=en) — invoke a skill on-demand by typing `/` followed by the skill name, or just ask the Assist Agent to run it.
* [Background Agents](https://support.usepylon.com/articles/9186512601-how-do-background-agents-work) — skills run automatically when a Background Agent is triggered. For example, the out-of-the-box `investigate` skill runs on every new issue to pre-investigate before your team arrives.

Agents can also invoke skills automatically when they detect a matching scenario — no manual trigger needed. Within each [agent](https://app.usepylon.com/settings/ai-controls/agents?tab=assist) you can control what skills are available.

<figure><img src="/files/uJV5hzRH3X2n2ayRYAMn" alt=""><figcaption></figcaption></figure>

#### Visibility & Permissions

Skills can be scoped to the entire org or specific teams or team members.

<figure><img src="/files/i9eyBQsWPOpgg5sCNo9W" alt=""><figcaption></figcaption></figure>

#### Examples

{% hint style="info" %}
Keep Skills small and scenario-specific. Several focused Skills are easier to select, test, and maintain than one large Skill covering unrelated workflows.
{% endhint %}

* A skill to escalate an issue to engineering by summarizing reproduction instructions and post into a Slack channel or creating a Linear issue
* A skill to call certain [Connectors](/pylon-docs/agents/connectors.md) to do a deeper investigate for a specific kind of issue
* A skill to summarize whether a certain feature request got shipped and what the changes included in it were


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.usepylon.com/pylon-docs/agents/skills.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.