> 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/migrating-to-skills.md). # Migrating to Skills Since September 17, 2026 the Agent guides and acts through Skills only. What was removed, what still connects the Agent to your experiences, and how to convert what you have. {% hint style="info" %} **What changed on September 17, 2026.** The Agent no longer finds or launches Tours and No-Code Actions. The Tours and Actions tabs of Knowledge, the tour trigger "On Agent response" and the action setting "Allow Agent to run this action" are gone. Your Tours and Actions still exist as experiences and run from their own triggers, CTAs and checklists. **Custom Answers stay.** {% endhint %} #### What maps to what
| You had | You create | The difference | | ------------------------------------- | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A Tour exposed to the Agent | A **Guide user in a flow** Skill | The Agent guides live on the real page, checks results and corrects errors, instead of replaying a fixed sequence. Users need the eye on. | | A No-Code Action exposed to the Agent | An **Execute a flow** Skill | Same idea, taught by doing and aware of the page's elements. Steps that send, pay, delete or change permissions are handed back to the user. | | A Custom Answer | Nothing to migrate | Custom Answers stay the tool for wording you control word for word, and for launching an existing experience from the chat. Add an **Explain** Skill where the answer depends on what is on screen. | A tour's steps cannot be reused as a Skill: rebuild the flow with [Show me](/docs/experiences/agent/skills/create-a-skill.md#step-3-describe-it-or-show-it) on the scanned page. #### What still connects the Agent and your experiences | Direction | How | Limits | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | Agent to another page | A running Guide or Execute Skill follows your app's own links | The link must be visible to the Agent: kept in the scan, or on a Read all page. A guide resumes after a reload in the same tab. | | Agent to any URL | A Custom Answer with a **Navigate To** button, or a link written in an answer | Only when that Custom Answer matches. | | Agent to an existing Tour, Survey or Checklist | A Custom Answer with a **Launch Experience** button | Only for that question, and the user clicks. If a Skill also matches, its Start button replaces it. Banners and Hints cannot be chosen. | | Experience to Agent | The **Launch Agent** action on a button, checklist task, Resource Center block or trigger, with an optional pre-filled message | The message is text the Agent interprets. It cannot target a specific Skill. | #### "I want the Agent to run my onboarding tour" 1. **For that exact tour:** create a [Custom Answer](/docs/experiences/agent/knowledge/custom-answers.md) for questions like "how do I get started?" with a **Launch Experience** button pointing at it. 2. **For an Agent-native version:** rebuild the flow as a **Guide user in a flow** Skill on the scanned page. Users need the eye on. 3. **For the other direction:** end the tour with a **Launch Agent** action and a pre-filled message such as "What should I do next?". Tours stay the always-on layer that uses no Agent requests; the Agent handles open questions and procedures on demand. #### Recommended path 1. [Scan the pages](/docs/experiences/agent/knowledge/interface/scan-a-page.md) your Tours and Actions ran on. Skills need the elements. 2. Recreate each one as a Skill, starting from the flows users ask about most ([Analyze > Conversations](/docs/experiences/agent/analyze.md) tells you). 3. Test each Skill with **Try this skill**, then live in your product, eye on, in a new chat. 4. Turn the Skill **Active** once it runs end to end. #### Related pages * [Skills](/docs/experiences/agent/skills.md): the three types, and how a Skill is offered * [Create a skill](/docs/experiences/agent/skills/create-a-skill.md): Describe it, or Show me * [Custom answers](/docs/experiences/agent/knowledge/custom-answers.md): the Launch Experience button * [Agent](/docs/experiences/agent.md): what the Agent can do today