> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/experiences/agent/skills.md). # Skills *** {% hint style="warning" %} **Beta** ยท This feature is currently in beta. Behavior and interface may still evolve. {% endhint %} **Dashboard path:** [Agent > Skills](https://i.usejimo.com/agent/skills) A Skill teaches the Agent **how to get something done** in your product. Where [Knowledge](/docs/experiences/agent/knowledge.md) makes the Agent able to explain, Skills make it able to act: walk a user through a flow, execute the flow itself, or build a precise answer from the page and your sources.
### The three types of Skills
| Type | Short label | Who is in control | What happens | | ---------------------------- | ----------- | ----------------- | ------------------------------------------------------------------------------------------------------------ | | **Execute a flow** | Execute | The Agent | It completes the task by clicking, filling in forms, and navigating on behalf of the user. | | **Guide user in a flow** | Guidance | The user | The Agent shows steps, checks results, and corrects errors. The user does the clicking. | | **Answer complex questions** | Explain | Conversation only | The Agent answers in text, using relevant page elements and knowledge sources. No interaction with the page. | In page panels, the type shows under each Skill's name as **Execute Skill**, **Guide Skill** or **Explain Skill**; Guide and Guidance name the same type. Execute and Guidance share the same structure: a flow of steps on the page's elements. The only difference is whether the flow progresses automatically or waits for the user, which is why a Skill can [switch between these two modes](/docs/experiences/agent/skills/create-a-skill.md) after creation. Explain is a different construction: no flow, an answer framed around the elements you select. The right type is a trust decision as much as a capability one. **Execute** fits repetitive, low-risk tasks (create a report, apply a filter set). **Guide** fits anything the user should learn or where a wrong click matters. **Answer** fits questions whose answer depends on what is on screen, without needing to touch it. {% hint style="warning" %} #### **Skills replace Tours, Actions and Custom Answers for the Agent** (all three stop on September 12, 2026) * A **Guidance** Skill succeeds Tours: a tour built on the fly, AI-assisted, on the scanned page. * An **Execute** Skill succeeds No-Code Actions in conversations: same construction as Guidance, but the flow runs on its own. The Automated Actions section is already limited to projects that still have active Actions; everywhere else, Execute Skills are the way. * An **Explain** Skill rethinks Custom Answers: instead of a fixed Q\&A pair with a CTA, it frames a topic around a specific interface to contextualize the answer. The action-triggering side of old Custom Answers moves to Guidance and Execute, which suggest and run flows natively. {% endhint %}
### The Skills list Two cards sit at the top of the page: **Skill usage**, the number of runs over the last 30 days with its variation, and **Completion rate**, week by week.
Below, every Skill in the project appears in one table: | Column | What it tells you | | ------------------- | ------------------------------------------------------------------------------------------------- | | **Name** | The Skill's name, with the first line of its description underneath. | | **Last updated** | When the Skill was last edited. | | **Usage** | How many times it ran. | | **Completion rate** | Share of runs that reached the end of the flow. A Skill that has never run shows **No runs yet**. | **Search skills**, a sort selector and an **All Skills** filter narrow the list. **Add Skill**, top-right, opens the creation flow. ### Where Skills live Skills exist in two views of the same thing: * **This page** lists every Skill in the project. * **Each scanned page** shows its own Skills in the [Page details](/docs/experiences/agent/knowledge/interface/page-details.md) panel, because a Skill runs on the elements of a page. The Interface list even shows a Skills counter per page. That link is why scanning comes first: a Skill can only click, fill or reference what the Agent can [read](/docs/experiences/agent/knowledge/interface.md#two-ways-the-agent-can-learn-a-page). ### What a Skill is made of Click a Skill, from this list or from a page's panel, to open it. Its panel has two tabs, **Usage** and **Settings**, an **Active** toggle in the header, and a menu with **Delete**. The **Settings** tab holds the three things that define the Skill: * **Description for the agent**: what the Skill covers, and above all *when* the Agent should use it. This is what decides whether the Skill fires on a given question, so it is written around the questions users actually ask. * **Instructions for the agent**: the goal, the **inputs needed from the user**, and the numbered steps the Agent follows. * **Mode**: the type, switchable after creation.
The **Active** toggle controls whether *end users can trigger it*. A Skill stays invisible to your users until you turn it on, so you can draft and test it in peace. **Try this skill** runs it in a test chat on the real page.
{% hint style="warning" %} **The description does the routing.** Two Skills with vague, overlapping descriptions will compete for the same questions. Write each one around a distinct user intent, in the words users use. {% endhint %} ### How a Skill performs
The **Usage** tab of a Skill is where its own numbers live: **Usage** over a period you choose, a chart of runs over time, and the **conversations** where the Skill fired, filterable by response. Flow Skills (Execute and Guidance) add a **Completed** counter with its rate; an Explain Skill has nothing to complete, so it only counts usage.
{% hint style="info" %} #### **Skill statistics and Analyze are two different reads.** [Analyze](/docs/experiences/agent/analyze.md) covers **every** conversation the Agent had, at project level. It does not break them down by Skill or by scanned page: each Skill, and each Skill attached to a page in [Interface](/docs/experiences/agent/knowledge/interface.md), keeps its own Usage tab, and that is where the link to the conversations it drove is made. {% endhint %} ### Creating one **Add Skill** opens the creation flow, with two methods: describe it in words, or do the task once and let the Agent capture it. See [Create a skill](/docs/experiences/agent/skills/create-a-skill.md). ### Related pages * [Create a skill](/docs/experiences/agent/skills/create-a-skill.md): Describe it, or Show me * [Interface](/docs/experiences/agent/knowledge/interface.md): the pages Skills run on * [Knowledge](/docs/experiences/agent/knowledge.md): the five kinds of Agent knowledge, and what Skills replace * [Analyze](/docs/experiences/agent/analyze.md): every conversation the Agent had, at project level