Oct 12, 2026 · 7 min read
Share Agents as templates
Turn an Agent that works into a recipe others can install. What travels, what stays private, and a workshop Project to build it in.
Lea Brandt built an Agent that turns client call notes into a one-page brief. It works, and Sam Okafor wants one too. Copying the instructions by hand would lose its skills and setup. Handing over Lea's Agent would hand over her accounts and everything it has learned about her clients.
A template sits in between. It is a recipe, not a copy. Sam installs his own Agent from Lea's recipe, with his own model and accounts. It starts fresh and learns from Sam's work. Conversations, accounts and learned memory never travel.
The team
This guide also sets up a workshop Project, a place to design, test and review Agents before you share them.
| Agent | One job | Never does | Works in |
|---|---|---|---|
| Agent Builder (@agent-builder), lead | Builds an Agent with you, then improves it from real feedback | Promises tools, connectors or knowledge the Agent doesn't have | #general, #template-reviews |
| Tinker (@tinker) | Turns repeated know-how into a skill or tool, so the recipe carries it | Publishes anything before you approve it | #general |
| Team Reviewer (@team-reviewer) | Reviews your Agents for overlap and suggests the smallest useful change | Deletes an Agent (only people do) | #template-reviews |
| Pushback (@pushback) | Critiques the draft Agent before it ships | Rewrites it for you | #template-reviews |
People: Lea designs, Sam tests, and Ana, an admin, can share any Agent. People and Agents review in the same threads, so everyone sees why a recipe changed before anyone installs it.
Set it up
The workshop (works today on the web)
- Add the built-ins. Agents → the + card → "Add agent". Pick "Agent Builder" and click "Create agent". Repeat for "Pushback", and for "Tinker" unless you already have it.
- Install the reviewer. In "Library", choose the "Agents" chip and the "Operations" category. Open the template that designs and reviews Agent teams, click "Install agent", name it "Team Reviewer", and click "Install agent".
- Create the Project and Channels. Projects "+" → "Create a new project", name it
agent-workshop, and click "Create project". Brief#generalthrough right-click → "Channel settings…" → "Description". Add#template-reviewswith the Project's ⋯ → "New channel".#general: Design and test Agents here. Describe the job; Agent Builder drafts it and you try it.#template-reviews: Before sharing: what the recipe carries, and what must stay private.
- Team it. Agents → "Agent teams" → "New team" → "Create team". Name it "Agent Workshop", select the four Agents, paste the team instructions, and click "Create team". Then, in the Project, "People & Agents" → "+" next to "Agents" → "Deploy team" → both Channels → "Deploy to 2 channels".
- Set up the weekly review. On Team Reviewer's profile, under "Automations", click "Set up". The editor opens switched off. Set "Posts to" to
#template-reviewsand "When to run" to "Every week", Monday 10:00. Turn on "Run quietly in the background", then click "Create". If the instruction ends with lines about when it fires, delete them; "When to run" holds the schedule.
Agent Builder leads and owns each new Agent. Before anything is shared, it mentions @pushback and @team-reviewer in #template-reviews; each posts its own verdict in that thread. Tinker turns repeated know-how into a skill. An Agent's yes is never a person's yes: sharing and publishing wait for a person. Stay quiet when nothing changed.
Share an Agent
- Open the Agent's ⋯ → "Share…". In "Share agent", write a "Description" and choose "Who can install it?": "Your organization" or "Anyone with the link".
- Leave "Show in the Agent Library" off to share by link only. Turned on, the listing is reviewed first, but the link works right away.
- Open "What's included" and read each row of "Template details". Then click "Share agent", then "Copy link", and paste the link in a Channel.
| Travels in the template | Stays with you |
|---|---|
| Name, avatar, instructions and persona | Conversations |
| Tools switches, and the skills and tools added from the Library | Connected accounts (the template lists which services are needed, never your sign-ins) |
| Which connectors it needs | Memory the Agent learned |
| Proactivity, if you changed it | Your automations and their schedules |
| For an Agent installed from a template: that template's automation instructions and included knowledge | Files on its Computer |
So put know-how you want to share into instructions or a skill. Memory and your automations won't travel.
Install one
- Open the link and read the template page: "Instructions", "Capabilities", "Tools", "Connectors" and "Setup notes". Click "Install agent", choose a name and model, pick an account for each connector or "Set up later", and click "Install agent".
- On the new Agent's profile, finish "Template connectors" with "Connect" or "Use account". Any template automations wait under "Automations" with "Set up", switched off.
Teams install the same way. The ready-made teams under Agents → "Agent teams" → "Ready to install" give you fresh Agents with your own accounts, like any template. Your own teams aren't shared as templates; you share one Agent at a time.
What happens each day
Every Agent has its own Computer
Its own files and tools, plus a profile with Memory, skills, and connectors. A live demo with sample data; try it.
- Mon 09:40. In
#general, Lea asks @agent-builder for an Agent that turns call notes into a one-page brief. Agent Builder shows the name, job, instructions and what it won't do, then posts a New Agent card. Lea clicks "Review", then "Accept and create". - Mon 10:15. Lea tries it on real notes. The brief buries the decisions, so she says so, and Agent Builder updates the instructions.
- Mon 11:00. Lea asks @tinker to make the brief format a skill. Tinker shows the whole skill, publishes it after her yes, and adds it to the Agent. It will now travel in the recipe.
- Tue 14:00. In
#template-reviews, @pushback questions whether the brief needs a risks section, and @team-reviewer notes it overlaps an older notes Agent. Lea narrows the old one. - Tue 15:30. Lea shares to "Your organization" and pastes the link. Sam installs it and connects his own Notion.
- Next Mon 10:00. The weekly review runs quietly and raises one change worth making.
Copy these prompts
@agent-builder I want an Agent that turns client call notes into a one-page brief: decisions, open questions, next steps with owners. Draft it here and show me what it won't do.
@tinker Make the brief format we settled on into a skill, so anyone who installs this Agent gets it. Show me the full skill before you publish.
@pushback @team-reviewer Review the brief Agent before I share it. What is weak, what overlaps our other Agents, and what in its instructions only makes sense for me?
@agent-builder Rewrite this Agent's instructions for someone outside our studio: no client names, no links only we can open. Show me the change before you save it.
Rules that keep it healthy
- Test before you share. Run the Agent on real work in
#generalfirst. - Write for a stranger. Remove your names, clients and private links from the instructions.
- Put know-how in skills. Memory doesn't travel; skills do.
- Share the smallest audience first. "Your organization" before "Anyone with the link".
- Read before you install. Check the instructions, tools and connectors on every template page.
What it can't do yet
- Installed copies don't update when you click "Publish update". "Stop sharing" disables the link; installed Agents stay.
- Instructions are locked at install. Edit them on the Agent afterwards.
- Only the owner or an admin can share an Agent, and Agents can't share themselves.
- Agents that run on your computer can't be shared.
- No share button inside conversations. Paste the link instead.
- Public templates can include custom code. Install only skills and tools you trust.
- Automations never arrive scheduled. You choose where and when each one runs.