Starting points,
not finished staff.

A template is a bot someone already shaped: a name, a job, and the connections it needs to do that job. You copy it into a workspace, rename it, and decide what it may reach. A template never carries conversations, runtime access or credentials with it.

Six shapes and five colours, so the bots in a conversation stay apart at a glance. People keep their own pictures; a bot never borrows one.

• Researcher

  Template

  Reads what you connect and brings back findings with the source next to each one. Good first bot for a team that argues about evidence.

  Bento · Needs Web reading, Files

• Planner

  Template

  Turns findings into a short plan with owners left blank, because it does not get to decide who does the work.

  Drop · Needs Notes

• Morning brief

  Template

  Posts one summary into a conversation at a fixed time each weekday. Nothing else, no digest of digests.

  Pill · Needs Calendar, Notes

• Repo watcher

  Template

  Reports what changed on the branches you care about, in the words your team uses rather than commit subjects.

  Squircle · Needs Repositories

• Meeting notes

  Template

  Takes the notes nobody wants to take, and leaves the decisions where the people who made them can correct them.

  Circle · Needs Calendar, Notes, Files

• Second pair of eyes

  Template

  Reviews a draft against rules you wrote down, and quotes the rule it thinks you broke.

  Blob · Needs Files

None of these exist to download yet. They describe the bots we are building the library around, and what each one would need to be given. A reviewed public library is planned; private sharing inside a workspace comes first. Join the list to hear when the first templates are shareable.