> ## Documentation Index > Fetch the complete documentation index at: https://docs.appreply.co/llms.txt > Use this file to discover all available pages before exploring further. # Skills and workflows > Start RADAR on a guided routine, and save a routine of your own for the whole team A skill is a guided routine for RADAR, AppReply's AI assistant. Instead of describing a job from scratch, you pick a skill and RADAR follows its steps on your organization's data: it pulls the numbers, draws the charts and hands back a short answer. A skill your team writes for itself is called a workflow. Open the **Skills** page from the RADAR sidebar to see every skill you can start. ![The Skills page: a search field, two recommended skills, a banner for saving your own workflow, and skills grouped under Measure, Compete and Improve](https://mintcdn.com/appreply/bnS5T3Kw2jFffd-K/images/product/assistant/05-skills.png?fit=max\&auto=format\&n=bnS5T3Kw2jFffd-K\&q=85\&s=bd95d5219d247573bc51643412c5d745) ## What the Skills page shows Skills sit under one heading per kind of job, in this order: | Group | What it is for | | - | - | | **Your workflows** | The routines your own team saved. Shown first when there are any. | | **Measure** | Reading how things went, such as the weekly review, release health, the monthly executive summary and portfolio health. | | **Compete** | Your app against its rivals, such as competitor watch and the competitor deep dive. | | **Improve** | What needs you now, such as daily triage, spike response and the reply quality review. | | **Set up** | Getting a new workspace ready, such as the first week checklist, the knowledge base, reply voice, reply grading and going live gradually. | | **Research** | Questions that need outside data, such as keyword research, launch watch, the incident check and the AI visibility audit. | | **Help** | Where to do something RADAR cannot, and short guides for kinds of team: support teams, game studios, solo developers and others. | A group shows its first six skills. Click **Show all** to see the rest. Type in **Search skills** to find one by name or by what it does. Each skill has a one-line summary of what you get. Click it to start. > [!NOTE] > > The list depends on you. A skill that your role, your plan or your organization's settings hide is left out, the same way RADAR itself cannot use it. A Member and an Admin can see different lists. For example, **Voice of the customer** and **AI visibility audit** need a paid plan and at least one research connector switched on, **Review site reputation** needs a paid plan and **Review sites and search data** switched on, and **Learn and test the complete reply setup** is listed for Admins and Owners only. ### Recommended now When something is worth doing today, a **Recommended now** section appears above the groups with up to two skills. An open setup step comes first, because nothing else works well before it. After that, RADAR suggests the daily triage when replies are waiting for your approval or unhappy reviews from the last 30 days have no reply. If nothing is worth suggesting, the section is not shown. ## Start a skill There are three ways to start one: * **From the Skills page.** Click a skill. A new chat opens and RADAR starts it. The skill's name appears as a chip in place of the first message. * **From the slash menu.** In the message field, type `/` at the start or after a space. A list opens with commands first and your skills below it. Keep typing to narrow it, for example `/week`. Use the arrow keys and press Enter or Tab, or click a row. * **From the plus menu.** Click the plus button next to the message field and choose **Skills**. The last two put the skill in the field as a chip. You can type extra words to go with it, such as which app to look at, or send it as it is. Click the cross on the chip to take the skill off again. > [!TIP] > > A skill follows the same rules as any other chat. If it proposes a change, such as a reply or a new alert rule, the change waits on an approval card until you approve it. Skills that use outside research can cost a small amount per lookup, and only work when an Admin has switched on the research [connectors](/assistant/connectors.md). ## Save a workflow of your own Some routines are yours alone: the Monday review for your leadership channel, or the way you check a launch. Save one as a workflow and anyone in the organization can start it from the Skills page or the slash menu, the same as a built-in skill. Only an Admin or Owner can add, change or remove a workflow. For a Member the **Add skill** button is switched off, and a tooltip says why. There are three ways to add one. Open **Add skill** at the top of the Skills page, or use the **Teach RADAR your workflow** banner. The banner can be closed with its cross, and it then stays closed in this browser; **Add skill** keeps all three ways. **1. Create with RADAR** Describe the routine in your own words. RADAR asks up to three short questions if it needs them, drafts a name, a description and numbered steps, and shows you the whole draft. It then proposes saving it as a card. Nothing is saved until you approve the card, and the card shows the full text. **2. Write it yourself** Fill in a **Name**, a **Description** and the **Instructions**, then click **Create skill**. The button stays off until the text is acceptable. A counter appears under a field when you get near its limit. **3. Upload a file** Choose a `.md` or `.txt` file. RADAR opens it in the same form so you can check it before saving. If the file starts with a front matter block holding `name` and `description`, those fill the first two fields. Otherwise the name comes from the file name. ### What a workflow can hold | Part | Limit | | - | - | | Name | 80 characters | | Description | 200 characters | | Instructions | 30,000 characters | | Workflows per organization | 50 | Two workflows cannot share a name. Instructions are kept whole and are never shortened. Write the instructions as numbered steps with concrete actions: which data to pull, for what period, how to compare it and what to hand back. A workflow is instructions only. It runs under the same rules and the same approval cards as any chat, so it cannot skip an approval or change something without a card. Because every member can read a workflow, it is not saved if the text looks like it holds a password, key or token. ### Change or remove a workflow On a workflow row, Admins and Owners see a menu with **Edit** and **Remove**. Edit opens the same form. Remove asks for confirmation and removes the workflow for everyone in the organization. Chats that already ran it keep their answers. You can also ask RADAR in a chat to change a workflow. It proposes the update as a card that shows the text before and after. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.