Changelog

Published specialists share what they do, not your data

Publishing a specialist now shares a template of what it does, never the workflows, apps, files, or memory you built. When you choose Publish, the specialist reads its own workflows, apps, and skills and writes its template the way our own templates are written: its role, what it starts out knowing, what it can set up, and a made-up example. Whoever installs it gets a specialist that sets itself up.

How it works

  • Nothing of yours goes with it. Before you see the draft, it is checked for the names of your workspace and its members, the channels its settings post to, and any email address, phone number, link, or account id. Anything found goes back to the specialist to rewrite, and the check runs again on publish.
  • A brief for each piece. Every workflow, app, and skill in a template carries a short brief on how it works, the settings it asks for, and where results go, so an installed specialist can build it for any business.
  • See it before it is public. Once drafted, Publish opens on the template's page and card as Templates will show them, with the memory and setup notes each copy gets. A banner above holds who can install it and Publish.
  • Earlier publications keep working. A specialist published before today installs as it did until you publish it again.

Also shipped

  • Publish beside Share. It reads Published once the template is out, marked with who can install it. On the live page you can change who can install it without republishing, copy its link, publish a new version, or take it down.

Your first specialist starts here.

Give it one job. Build the workflows, apps, and skills to get it done.