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

# Skills

AI agent skills are multi-step jobs your agent runs end to end, like testing its answers on past tickets or finding ticket trends. Learn how to run one.

A skill is a job your teammate knows how to do end to end: a multi-step job with a set process and a saved result. Your teammate testing its answers against hundreds of your past tickets is a skill. Reading a month of conversations and writing up what customers keep asking about is a skill.

A skill can also act on what it finds, so the work gets finished rather than handed back to you.

## Quick start

{% stepper %}
{% step %}

### Ask your agent to run a skill

Open the chat in your dashboard and ask for the skill by name, or describe the job you want done. Your agent picks the skill, gathers what it needs and reports each step in the chat as it goes.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-6cad8c003908b0f9c07104b38a811d245781fd45%2Fskills-run-chat.png?alt=media" alt="A dashboard chat where the user asks the agent to run the Helpdesk simulation skill, and the agent reports each step as it samples 20 resolved tickets and starts the runs"><figcaption><p>The Helpdesk simulation skill starting from one line of chat.</p></figcaption></figure>

If the skill needs an app you have not connected, it tells you and walks you through connecting it.
{% endstep %}

{% step %}

### Read the result

When it is done, the result comes back in the same chat: the headline finding first, then the detail.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-bc79839d5b1f7aee7ddaa83bb450f92ffaea441c%2Fskills-run-results.png?alt=media" alt="The chat showing the simulation result: 17 of 20 tickets matched the team&#x27;s reply quality, with a score for each ticket theme"><figcaption><p>The headline score, then the same score split by theme.</p></figcaption></figure>

It ends with what it suggests you do next, a link to the full output, and a note of anything it sent on your behalf.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-c4129260e26c9f6b5bff1f3be9649dbccdfffd83%2Fskills-run-fixes.png?alt=media" alt="The same chat scrolled down, listing five ranked fixes, a link to the full simulation report and a note that the summary was emailed"><figcaption><p>Five ranked fixes, the report link, and the email it sent.</p></figcaption></figure>
{% endstep %}

{% step %}

### Open the full report

Click the link, or the file under **Files** in the left sidebar. The report opens as a document beside the chat, so you can read it and act on it in the same place.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-89d8bd80a6d67fe3bc81c66743e09d7c94e2ef71%2Fskills-run-report.png?alt=media" alt="The Simulation report file open in the dashboard next to the chat, showing the headline finding, four result tiles and the results by theme"><figcaption><p>The saved report, with the chat still beside it.</p></figcaption></figure>

A skill can also run on its own. Attach it to an [automation](/automations-and-schedules/automations-and-schedules.md) and it runs on a schedule, for example a report every Monday morning.
{% endstep %}

{% step %}

### Or start one from the Skills page

Open **Skills** in the left sidebar to see every skill your agent has, grouped by what it is for. Click **Ask eesel** on a tile and the chat opens with that skill ready to run. **See an example** shows a sample of what it produces.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-3bbcebbb1c39f9277e5561cce36ee35b2eb12a50%2Fskills-list.png?alt=media" alt="The Skills page listing Helpdesk simulation, Analyze ticket trends, Write a blog post and Commit and push to GitHub as tiles, each with an Ask eesel or Contact us button"><figcaption><p>The Skills page, with Ask eesel on each tile.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## What ships out of the box

| Skill                                                                    | What it does                                                                                                            |
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| **Simulation**                                                           | Runs your agent against real past tickets or generated test cases, scores each answer, and suggests instruction changes |
| **Analyze and improve replies**                                          | Looks at what your team rejected or edited, finds the pattern, and suggests fixes                                       |
| **Review agent setup**                                                   | Audits your agent's configuration and performance, and tells you what to change                                         |
| **Analyze ticket trends**                                                | Recurring topics, sentiment, volume and resolution patterns across your conversations                                   |
| **Update knowledge base**                                                | Finds the questions your help center does not answer, and drafts the missing articles                                   |
| **Write a blog post**                                                    | Researches and writes a full post with images. See [Content Writing](/use-cases/content-writing.md)                     |
| **Translate content**                                                    | Translates content while keeping formatting and meaning intact                                                          |
| **Draft an internal note**                                               | Writes a reply as an internal note for your team to review                                                              |
| **Send a public reply**                                                  | Sends a reply to the customer                                                                                           |
| [**Look up Calendly meetings**](/integrations/communication/calendly.md) | Reads your Calendly bookings: who a meeting is with, who is hosting, when, and whether it was canceled. Read-only       |
| **Voice call transcriber**                                               | Transcribes call recordings                                                                                             |
| **Commit and push to GitHub**                                            | Commits and pushes changes to a repository                                                                              |

## Work that is not on the list

If the job you want is not a skill here, describe it in chat. Your teammate does the work. When it is something you will want again, it writes the steps down as a file under **Files**, not as a skill, so next time you only have to ask.

## FAQ

<details>

<summary>What is a skill in eesel?</summary>

A skill is a multi-step job your agent knows how to do end to end, with a set process and a saved result. Testing its answers against your past tickets is a skill, and so is writing up what customers keep asking about.

</details>

<details>

<summary>How do I run a skill?</summary>

Ask for it in the dashboard chat, by name or by describing the job. Or open **Skills** in the left sidebar and click **Ask eesel** on a tile. Your agent reports each step in the chat and saves the full result under **Files**.

</details>

<details>

<summary>Can a skill run on a schedule?</summary>

Yes. Attach it to an [automation](/automations-and-schedules/automations-and-schedules.md) and it runs on a schedule or a trigger, for example a report every Monday morning.

</details>

<details>

<summary>A skill shows "Contact us" instead of an add button. Why?</summary>

Some skills need to be switched on for your workspace before your teammate can add them. If one is not available, [contact us](https://eesel.ai/contact) or ask in the in-app support chat under **Help and support**.

</details>

<details>

<summary>Is there a community marketplace?</summary>

Not yet. The skills on your Skills page are built by eesel and added from there, or by asking your agent in chat. From a terminal, `eesel chat "turn on the ticket trends skill"` does the same through the [CLI](/apis-and-developer-resources/cli.md). A community marketplace where teams publish skills for each other is something we are working towards.

</details>

<details>

<summary>Can a skill work across more than one app?</summary>

Yes. A skill can use anything your agent is connected to, in one run: read your helpdesk, check Shopify, and post the result to Slack. A skill can also reach your own systems through [Network Access](/apis-and-developer-resources/network-access.md).

</details>

<details>

<summary>Where do I see what a skill produced?</summary>

Every run shows up in **Activity** with its output attached. Outputs sent to a file live under **Files**.

</details>

<details>

<summary>Can a skill have its own instructions?</summary>

Yes. A skill can carry saved instructions that apply only when it runs, so a blog style guide does not sit in the instructions your support replies read. Your agent's core [instructions](/instructions-and-memory/instructions-and-memory.md) still apply underneath.

</details>

## Related

* [Automations and Schedules](/automations-and-schedules/automations-and-schedules.md) to run a skill on a schedule or a trigger
* [Instructions and Memory](/instructions-and-memory/instructions-and-memory.md) for how skills feed back into how your agent behaves
* [Reports](/reports/reports.md) for the report skills and the Reports page
* [Use eesel from Claude and other AI assistants](/apis-and-developer-resources/use-eesel-from-claude-and-other-assistants.md) and [Use eesel from ChatGPT](/apis-and-developer-resources/use-eesel-from-chatgpt.md) to ask your agent for a skill from a chat assistant


---

# 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.eesel.ai/skills/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.