Agent library
The Agent library is the fastest way to stand up your first agents. It’s a browsable catalog of ready-made starters — each a one-task agent with a copy-paste-ready build prompt — surfaced so the ones you can actually run, given what you’ve connected, come first. Open it from Library in the sidebar.
What’s in the library
Section titled “What’s in the library”124 starters across 14 work areas, 15 of them flagged First Wave — the highest-impact, lowest-effort places to start. (Counts as of this writing; the library grows over time.)
By work area:
| Work area | Agents | First Wave |
|---|---|---|
| RevOps / Operations | 13 | 2 |
| Finance / Accounting | 12 | 1 |
| HR / People | 11 | 0 |
| Sales / SDR | 10 | 2 |
| Customer Success / Support | 10 | 2 |
| Marketing | 10 | 2 |
| Inventory / Supply | 10 | 1 |
| IT / Internal | 9 | 1 |
| Executive / Admin | 9 | 1 |
| Product / Engineering | 9 | 1 |
| Docs / Legal | 7 | 0 |
| Security / Trust & Compliance | 6 | 1 |
| Professional Services | 5 | 1 |
| Partnerships / Channel | 3 | 0 |
By archetype (the shape of work — see below):
| Archetype | Agents |
|---|---|
| Monitor & Alert | 36 |
| Workflow Trigger | 21 |
| Draft | 16 |
| Hygiene & Flag | 15 |
| Summarize & Digest | 13 |
| Capture & Structure | 10 |
| Knowledge Q&A | 6 |
| Reconcile | 4 |
| Extract | 3 |
By connection — how many starters a given connection unlocks (the top dozen; 26 connection categories appear in all):
| Connection | Starters that use it |
|---|---|
| Slack (notify) | 57 |
| CRM | 28 |
| Docs / knowledge | 25 |
| 22 | |
| Accounting | 13 |
| HRIS | 12 |
| Forms | 11 |
| Inventory | 10 |
| Issue tracker | 9 |
| Identity / SSO | 8 |
| Call recorder | 7 |
| Helpdesk | 6 |
Connecting Slack and your CRM alone makes the largest share of the library runnable.
Connection-aware ranking
Section titled “Connection-aware ranking”The library knows which connections you have, and ranks starters accordingly. Each card shows its required connections as chips:
- Ready — you have every connection it needs; it sorts to the top.
- Connect X — it needs a connection you can add (the chip links to Connections).
- Not yet — it needs a category Tembo doesn’t connect to yet.
A brand-new workspace still sees the whole library — connect your tools and watch starters light up as Ready. Built-in capabilities (web search and the Tasks Inbox) never count against readiness.
Browse by work area, label, or connection
Section titled “Browse by work area, label, or connection”Three facets narrow the list, plus a search box and a Ready for my connections toggle:
- Work area — the function it serves (Sales / SDR, Customer Success, RevOps, Finance, IT, HR, and more).
- Label — primarily the starter’s archetype (its shape of work), plus “New idea” for recent additions.
- Connection — show only starters that use a given connection — e.g. everything that touches a CRM, or a call recorder.
Archetypes
Section titled “Archetypes”Every starter follows one of a small set of archetypes — a proven shape of work with built-in guardrails. The guardrails are what make these safe first agents: most are read-only or draft-only, with a human in the loop.
| Archetype | What it does | Guardrail |
|---|---|---|
| Monitor & Alert | Watch a source, evaluate a condition, notify an owner | Read-only; never writes back |
| Hygiene & Flag | Scan records for a quality problem; flag offenders | Flags, never auto-fixes |
| Capture & Structure | Turn unstructured input into a structured record | Asks rather than guessing |
| Draft | Assemble context into a draft for review | Never sends or publishes |
| Knowledge Q&A | Answer questions from approved sources | Cites sources; no speculation |
| Workflow Trigger | On an event, kick off the next steps | Scoped, idempotent steps |
| Summarize & Digest | Roll many items into one summary | Read-only |
| Reconcile | Compare two systems; surface mismatches | Read-only; flags differences |
| Extract | Pull structured fields out of documents | Stages low-confidence values |
From a starter to a running agent
Section titled “From a starter to a running agent”- Click Use this on a starter. The New Agent form opens, pre-filled with the starter’s name and its full build prompt.
- Edit anything — tweak the prompt, rename it, adjust the scope.
- Click Create. Tembo’s coding agent writes the agent file and opens a pull request (or commits directly), exactly like authoring any agent.
- Review and merge. Connect anything still missing, then schedule it to run on its own.
Many starters surface their findings into the Tasks Inbox for you to review and act on.
Library vs. Example Agents
Section titled “Library vs. Example Agents”The library is the in-app, connection-aware take on Example Agents: the same idea — start from a proven prompt — but browsable, ranked to what you can run, and one click to pre-fill. The Example Agents page remains a handy copy-paste reference.
Under the hood
Section titled “Under the hood”Each starter is a small YAML file in the platform repo
(web/src/lib/agent-library/) — its title, build prompt, connection categories,
and labels. Self-hosting instances can add
or edit starters, and they show up in the library on the next deploy.