Bot templates and share links
Start a bot from the built-in template gallery, export your own bot as a template, or share an encrypted copy with a link, with exactly what travels and what never does.
A bot you have tuned (instructions, skills, routines) is worth reusing. Neoo gives you three ways to do it: a gallery of ready-made templates, Export as template for your own bots, and share links that let someone else install a copy.
The template gallery
When you create a bot, open the Templates tab next to Describe it. Six templates are built in:
| Template | What it does |
|---|---|
| Executive Assistant | Triages your inbox, drafts replies for your approval and sends a short briefing every morning. |
| Research Analyst | Investigates a question, cross-checks sources and writes a structured brief with confidence levels. |
| Social Media Manager | Plans a content calendar and drafts posts in your voice. It publishes only what you validate. |
| Sales Prospector | Finds companies that match your ideal customer, researches them and drafts personal outreach. It never sends on its own. |
| Collections Follow-up | Watches overdue invoices and prepares polite, escalating payment reminders for your approval. |
| Data Analyst | Pulls your numbers, keeps weekly KPIs in its own data tables and writes a short report. |
Each template carries careful instructions, one to three short skills, suggested routines, the integrations it expects, and a first conversation guide. Click Use template to see a preview before anything is created.
Review, choose where it runs, create
The preview lists what the template contains (skills, routines, triggers, integrations), how many credentials you will have to provide yourself, and anything Neoo cleaned. Then choose This computer or Neoo Cloud and click Create bot.
- Routines and triggers are installed disabled. Nothing runs until you turn it on.
- The bot uses your default model and provider, not the author's.
- Right after creation the bot starts a conversation with you and walks you through its setup, one question at a time: accounts to connect, your preferences, the tone, the schedule. It saves what it learns in its memory and asks before enabling any routine.
Export as template
In the bot's Actions → Advanced settings, open Share and templates and click Export as template. Neoo saves a .template.json file with the bot's profile, instructions, Job, skills, routines, triggers and the list of integrations. It never contains your memories, files or databases. To use it later, open the Templates tab and choose Open a file….
Share links
Actions → Advanced settings → Share and templates → Share link… creates a link to a copy of the bot as it is now.
You choose what to add. These options are off by default:
| Option | What it adds |
|---|---|
| Memories | The bot's durable memory and approved knowledge. |
| Private database | The bot's private data tables (up to 8 MB). |
The dialog previews the contents and sizes before you create the link. Once created, you get a link such as https://vatoide.com/bots/share/…#k=…. Click Copy and send it to someone you trust.
A share link is a capability: anyone who has the link can install a copy of the bot. Share it only with people you trust, and revoke it when you are done.
The link is a frozen copy: changing the bot afterwards does not change what the link installs.
Opening a link
Clicking a link opens a small page that offers Open in Neoo and explains that the Neoo desktop app is required. In Neoo:
- The bundle is downloaded, its checksum is verified and it is decrypted on your computer. You must be signed in to Neoo.
- You see a preview: contents, integrations to connect, and warnings.
- You choose This computer or Neoo Cloud.
- The bot is created. Its routines and triggers stay disabled until you enable them.
You can also paste a link in Templates → From a share link or a file.
Managing your links
The same dialog lists Shared links with their title, creation date and number of uses. Revoke stops the link at once and deletes the encrypted copy from our servers. A revoked link tells the person who opens it that it was revoked. You can have up to 50 active links.
What travels, and what never does
Always included: the bot's name, role, instructions, color, its Job, its skills, its routines and triggers (disabled), and the list of integrations (toolkits) it needs.
Optional, off by default: memories, and the private database.
Never included:
- conversation history,
- secrets: Vault entries, tokens, cookies,
.envfiles, connected accounts, - the shared database,
- budgets and limits from the author (bots run in Full Access without budgets),
- folder paths of the author's computer (a file trigger arrives without its folder).
Credentials are cleaned
Before a bundle is built, and again when one is opened, Neoo scans every text for literal secrets: API keys (sk-, sk-ant-), Slack tokens, GitHub tokens, AWS keys, private key blocks, JWTs and passwords inside URLs. Each one is replaced by [SECRET_REMOVED] and the warning names the field, never the value. Files that look like credential dumps (.env*, id_rsa*, *.pem, *.p12, credentials*.json, *.kdbx) are refused without exception. A private database that contains a literal secret is left out entirely.
Cleaning is a safety net, not a guarantee: read what you share, and keep real secrets in the Vault.
Triggers tied to an account or webhook arrive disabled and have to be reconnected. Integrations are declared by name only: you connect your own accounts after installing.
Encryption
The bundle is encrypted on your computer with AES-256-GCM using a random key. The key is placed in the part of the link after the #, which browsers never send to a server. Neoo's servers store only the encrypted bytes, a checksum and the optional title you typed (the title is not encrypted). Without the full link, the stored data cannot be read, not even by us. Downloading requires a Neoo session and is rate-limited.
Because the key lives only in the link, if you lose the link there is no way to recover it: create a new one.
Compatibility
Older exports of a bot (the .json from Export and the bundles used to move a bot between your computers) still open in the Templates tab: they are converted, and their history and checkpoints are left out.