Update to Roar AI

Snapshot Nov 12, 2026 · 12:08 UTC · version 1.0.4

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for get-started

Skill instructions — Now says: Offer a first job Offer to start on one thing, and ask only what it needs. Say the question from the tool's `next.ask` reply, using the business name they...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Roar AI and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 9, 2026 · 01:03 UTC

Show what they can do Show the groups and example requests from the tool's `next` reply, as they are. If the tool gave none, show this: **Build an app on Roar AI** - "Build a customer support chat for my website on Roar AI" - "Build an a...

After

Nov 12, 2026 · 12:08 UTC

Offer a first job Offer to start on one thing, and ask only what it needs. Say the question from the tool's `next.ask` reply, using the business name they just gave you. For example: "Shall I start with a one-page website for Lanka Bakes...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -18,30 +18,31 @@
 - If it succeeds, confirm in one line: "You're set up, <first name>."
 - If it says the account is already set up, say so in one line and carry on. Do not try again or try another way to rename it.
 
-## 3. Show what they can do
+## 3. Offer a first job
 
-Show the groups and example requests from the tool's `next` reply, as they are. If the tool gave none, show this:
+Offer to start on one thing, and ask only what it needs. Say the question from the tool's `next.ask` reply, using the business name they just gave you. For example:
 
-**Build an app on Roar AI**
-- "Build a customer support chat for my website on Roar AI"
-- "Build an app that summarises my customer emails on Roar AI"
-- "Build a tool that writes product descriptions on Roar AI"
+"Shall I start with a one-page website for Lanka Bakes? Tell me what it does, and I'll build it and put it online."
 
-**Already have an app?**
-- "Deploy my app and give me the live link"
+If it is just them, offer a website for them or their project instead.
 
-Then ask: "What would you like to do first?"
+Under it, in a line or two, list the other example requests from the tool's `next` reply, so they can pick something else. If the tool gave none, list these:
+
+- "Build an AI chatbot for my business"
+- "Build a simple tool for my team"
+- "Put my app online"
+
+Ask nothing else until they answer. Do not ask "What would you like to do first?": one clear offer is easier to say yes to than a list.
 
 ## 4. Do the first task
 
-When they pick one, do it with the Roar AI tools.
+If they say yes, or simply tell you what their business does, build the website. If they pick something else, do that. Use the Roar AI tools.
 
-- **Building an app:** agree in a few lines what the app does, then write it with them. The app reads its Roar AI key from `ROAR_API_KEY` and the AI endpoint from `ROAR_BASE_URL`, which is OpenAI-compatible. Roar AI gives every deployed app its own key, so never put a key in the code or the chat. Put the app online with `deploy_app` and share the live link.
-- **The code goes on GitHub first.** `deploy_app` deploys from a GitHub repository. If you cannot create one yourself, help the person create one on github.com and upload the app's files to it. Check `get_github_status`: if GitHub is not connected to Roar AI yet, an owner connects it once in the Roar AI console.
-- **Deploying an app they already have:** ask which GitHub repository it is in, then deploy it and share the live link.
+- **Building an app:** ask only what the job needs (for a website, the business's name and what it does; for a chatbot, what the business does and what people usually ask), agree in a few lines what the app does, then write it with them. Keep a first app small, so it goes live in this chat. The app reads its Roar AI key from `ROAR_API_KEY` and the AI endpoint from `ROAR_BASE_URL`, which is OpenAI-compatible. Roar AI gives every deployed app its own key, so never put a key in the code or the chat. Put the app online with `deploy_app_from_files`, which takes the files you wrote straight from this chat, so no GitHub repository is needed. Share the live link from `get_deploy_status`, and pass on what its `nextStep` says the app can have next, in a line. When they ask for a change later, send only the files that changed with `update_app_files`.
+- **Deploying an app they already have:** ask where it is. If it is a folder on their computer, the simplest way is to drop it in the Roar AI console (New application › From your computer); a small app they attach here you can send with `deploy_app_from_files`. If it is in a GitHub repository connected to Roar AI, deploy it with `deploy_app`. Then share the live link.
 
 ## Keep it simple
 
 - Short messages, plain words. The person may not be a developer.
 - No prices, credit or offers.
-- Do not ask what they plan to use Roar AI for, or anything about their business, beyond the two names.
+- While setting up, do not ask what they plan to use Roar AI for, or anything about their business, beyond the two names.

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\nname: get-started\ndescription: Set up a new Roar AI account and show what Roar AI can do. Use when the person sets up the Roar AI plugin, asks to set up their Roar AI account, or asks how to get started with Roar AI.\n---\n\n# Get started with Roar AI\n\nHelp the person set up their Roar AI account in two short answers, then get them to a first result.\n\n## 1. Ask for two names\n\nIn one short message, ask for their own name and their company's name, and say that if it is just them, their name is enough. Ask nothing else. Use only what they tell you: never guess a name or take one from anywhere else.\n\n## 2. Save them\n\nCall `set_up_account` with `fullName`, and with `company` unless it is just them.\n\n- If it succeeds, confirm in one line: \"You're set up, <first name>.\"\n- If it says the account is already set up, say so in one line and carry on. Do not try again or try another way to rename it.\n\n## 3. Show what they can do\n\nShow the groups and example requests from the tool's `next` reply, as they are. If the tool gave none, show this:\n\n**Build an app on Roar AI**\n- \"Build a customer support chat for my website on Roar AI\"\n- \"Build an app that summarises my customer emails on Roar AI\"\n- \"Build a tool that writes product descriptions on Roar AI\"\n\n**Already have an app?**\n- \"Deploy my app and give me the live link\"\n\nThen ask: \"What would you like to do first?\"\n\n## 4. Do the first task\n\nWhen they pick one, do it with the Roar AI tools.\n\n- **Building an app:** agree in a few lines what the app does, then write it with them. The app reads its Roar AI key from `ROAR_API_KEY` and the AI endpoint from `ROAR_BASE_URL`, which is OpenAI-compatible. Roar AI gives every deployed app its own key, so never put a key in the code or the chat. Put the app online with `deploy_app` and share the live link.\n- **The code goes on GitHub first.** `deploy_app` deploys from a GitHub repository. If you cannot create one yourself, help the person create one on github.com and upload the app's files to it. Check `get_github_status`: if GitHub is not connected to Roar AI yet, an owner connects it once in the Roar AI console.\n- **Deploying an app they already have:** ask which GitHub repository it is in, then deploy it and share the live link.\n\n## Keep it simple\n\n- Short messages, plain words. The person may not be a developer.\n- No prices, credit or offers.\n- Do not ask what they plan to use Roar AI for, or anything about their business, beyond the two names.\n"

AFTER

"---\nname: get-started\ndescription: Set up a new Roar AI account and show what Roar AI can do. Use when the person sets up the Roar AI plugin, asks to set up their Roar AI account, or asks how to get started with Roar AI.\n---\n\n# Get started with Roar AI\n\nHelp the person set up their Roar AI account in two short answers, then get them to a first result.\n\n## 1. Ask for two names\n\nIn one short message, ask for their own name and their company's name, and say that if it is just them, their name is enough. Ask nothing else. Use only what they tell you: never guess a name or take one from anywhere else.\n\n## 2. Save them\n\nCall `set_up_account` with `fullName`, and with `company` unless it is just them.\n\n- If it succeeds, confirm in one line: \"You're set up, <first name>.\"\n- If it says the account is already set up, say so in one line and carry on. Do not try again or try another way to rename it.\n\n## 3. Offer a first job\n\nOffer to start on one thing, and ask only what it needs. Say the question from the tool's `next.ask` reply, using the business name they just gave you. For example:\n\n\"Shall I start with a one-page website for Lanka Bakes? Tell me what it does, and I'll build it and put it online.\"\n\nIf it is just them, offer a website for them or their project instead.\n\nUnder it, in a line or two, list the other example requests from the tool's `next` reply, so they can pick something else. If the tool gave none, list these:\n\n- \"Build an AI chatbot for my business\"\n- \"Build a simple tool for my team\"\n- \"Put my app online\"\n\nAsk nothing else until they answer. Do not ask \"What would you like to do first?\": one clear offer is easier to say yes to than a list.\n\n## 4. Do the first task\n\nIf they say yes, or simply tell you what their business does, build the website. If they pick something else, do that. Use the Roar AI tools.\n\n- **Building an app:** ask only what the job needs (for a website, the business's name and what it does; for a chatbot, what the business does and what people usually ask), agree in a few lines what the app does, then write it with them. Keep a first app small, so it goes live in this chat. The app reads its Roar AI key from `ROAR_API_KEY` and the AI endpoint from `ROAR_BASE_URL`, which is OpenAI-compatible. Roar AI gives every deployed app its own key, so never put a key in the code or the chat. Put the app online with `deploy_app_from_files`, which takes the files you wrote straight from this chat, so no GitHub repository is needed. Share the live link from `get_deploy_status`, and pass on what its `nextStep` says the app can have next, in a line. When they ask for a change later, send only the files that changed with `update_app_files`.\n- **Deploying an app they already have:** ask where it is. If it is a folder on their computer, the simplest way is to drop it in the Roar AI console (New application › From your computer); a small app they attach here you can send with `deploy_app_from_files`. If it is in a GitHub repository connected to Roar AI, deploy it with `deploy_app`. Then share the live link.\n\n## Keep it simple\n\n- Short messages, plain words. The person may not be a developer.\n- No prices, credit or offers.\n- While setting up, do not ask what they plan to use Roar AI for, or anything about their business, beyond the two names.\n"

Full snapshot data

{
"description": "Set up a new Roar AI account and show what Roar AI can do. Use when the person sets up the Roar AI plugin, asks to set up their Roar AI account, or asks how to get started with Roar AI.",
"included_files": [],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: Set up a new Roar AI account and show what Roar AI can do. Use when the person sets up the Roar AI plugin, asks to set up their Roar AI account, or asks how to get started with Roar AI.\n---\n\n# Get started with Roar AI\n\nHelp the person set up their Roar AI account in two short answers, then get them to a first result.\n\n## 1. Ask for two names\n\nIn one short message, ask for their own name and their company's name, and say that if it is just them, their name is enough. Ask nothing else. Use only what they tell you: never guess a name or take one from anywhere else.\n\n## 2. Save them\n\nCall `set_up_account` with `fullName`, and with `company` unless it is just them.\n\n- If it succeeds, confirm in one line: \"You're set up, <first name>.\"\n- If it says the account is already set up, say so in one line and carry on. Do not try again or try another way to rename it.\n\n## 3. Offer a first job\n\nOffer to start on one thing, and ask only what it needs. Say the question from the tool's `next.ask` reply, using the business name they just gave you. For example:\n\n\"Shall I start with a one-page website for Lanka Bakes? Tell me what it does, and I'll build it and put it online.\"\n\nIf it is just them, offer a website for them or their project instead.\n\nUnder it, in a line or two, list the other example requests from the tool's `next` reply, so they can pick something else. If the tool gave none, list these:\n\n- \"Build an AI chatbot for my business\"\n- \"Build a simple tool for my team\"\n- \"Put my app online\"\n\nAsk nothing else until they answer. Do not ask \"What would you like to do first?\": one clear offer is easier to say yes to than a list.\n\n## 4. Do the first task\n\nIf they say yes, or simply tell you what their business does, build the website. If they pick something else, do that. Use the Roar AI tools.\n\n- **Building an app:** ask only what the job needs (for a website, the business's name and what it does; for a chatbot, what the business does and what people usually ask), agree in a few lines what the app does, then write it with them. Keep a first app small, so it goes live in this chat. The app reads its Roar AI key from `ROAR_API_KEY` and the AI endpoint from `ROAR_BASE_URL`, which is OpenAI-compatible. Roar AI gives every deployed app its own key, so never put a key in the code or the chat. Put the app online with `deploy_app_from_files`, which takes the files you wrote straight from this chat, so no GitHub repository is needed. Share the live link from `get_deploy_status`, and pass on what its `nextStep` says the app can have next, in a line. When they ask for a change later, send only the files that changed with `update_app_files`.\n- **Deploying an app they already have:** ask where it is. If it is a folder on their computer, the simplest way is to drop it in the Roar AI console (New application › From your computer); a small app they attach here you can send with `deploy_app_from_files`. If it is in a GitHub repository connected to Roar AI, deploy it with `deploy_app`. Then share the live link.\n\n## Keep it simple\n\n- Short messages, plain words. The person may not be a developer.\n- No prices, credit or offers.\n- While setting up, do not ask what they plan to use Roar AI for, or anything about their business, beyond the two names.\n"
}

SHA-256 of public snapshot: 2a8edcad5ba82e0d91b9092d862e5ade4b2374edda4edc0342b506aa96858cbd