Template cabinets
You don't have to build your AI team from scratch. cabinets.sh is a public registry of plug-and-play cabinets — each one is a complete folder with agents, jobs, knowledge, and connectors ready to run.
Browse them at cabinets.sh.
What's inside a template
Every template is a real, working cabinet folder:
job-hunt-hq/
├── .cabinet ← identity, version, parent
├── .agents/
│ ├── resume-tailor/persona.md
│ ├── interview-coach/persona.md
│ └── offer-analyst/persona.md
├── .jobs/
│ ├── daily-job-scan.yaml
│ └── weekly-pipeline-review.yaml
├── pipeline/
│ ├── target-companies.csv
│ └── applications.csv
├── interviews/
└── index.md
You install it. Cabinet picks up the agents, the jobs, and the knowledge skeleton all at once. You're running in 30 seconds.
Install in one command
npx cabinets add cabinet-app/job-hunt-hq
That clones the template into your data folder, runs Cabinet's first-time setup for the cabinet, and asks you to confirm any heartbeats before they fire.
If you only want one template from a monorepo:
git clone --filter=blob:none --sparse \
https://github.com/cabinet-app/cabinets.git \
&& cd cabinets && git sparse-checkout set job-hunt-hq
Featured templates
| Template | What it does | Team | Get it |
|---|---|---|---|
| ship-it-solo | Full startup ops for a one-person team — strategy, product, growth, support | CEO, CTO, Growth Lead, Support Rep | npx cabinets add cabinet-app/ship-it-solo |
| job-hunt-hq | Run your job search like a sales pipeline | Resume Tailor, Interview Coach, Networking Strategist, Offer Analyst | npx cabinets add cabinet-app/job-hunt-hq |
| reply-to-everyone | Email triage, drafting, follow-up automation | Inbox-Zero Strategist, Reply Drafter, Follow-up Nagger | npx cabinets add cabinet-app/reply-to-everyone |
| saas-startup | Marketing, product, ops cabinets for a small SaaS | PM, Marketer, Customer Success, QA | npx cabinets add cabinet-app/saas-startup |
| wedding-ops | Wedding planning as a project, with a team | Planner, Budget Hawk, Day-of Coordinator | npx cabinets add cabinet-app/wedding-ops |
| podcast-machine | Podcast pipeline — research, scripts, show notes, social | Producer, Researcher, Show-Notes Writer, Clip Strategist | npx cabinets add cabinet-app/podcast-machine |
| open-source-maintainer | Issue triage, PR review prep, releases, community | Triage Lead, Docs Writer, Release Manager | npx cabinets add cabinet-app/open-source-maintainer |
| agency | Multi-client agency ops with a child cabinet per client | Account Lead, Producer, Project Manager | npx cabinets add cabinet-app/agency |
Browse all 20+ templates on cabinets.sh ↗
Make it yours
A template is a starting point, not a contract. Once installed, edit anything:
- Open
.agents/<agent>/persona.md. Change the model, the role, the heartbeats. - Open
.jobs/<job>.yaml. Retime, retarget, disable, delete. - Move folders. Rename pages. Add child cabinets.
Cabinet doesn't track "diff from upstream." Once it's in your data folder, it's yours. You can still pull updates from the template repo when they ship — it's just git pull from inside the cabinet folder.
Publishing your own template
Made something useful? Share it.
# In the cabinet folder you want to publish
npx cabinets publish
That:
- Strips out anything in
.gitignore(your real client data, API keys, chat logs). - Generates a
README.mdat the cabinet root from the index. - Validates the persona.md and job.yaml schemas.
- Opens a PR to the cabinets.sh registry repo with your folder.
Tips for a template people will actually install:
Tip — Name it like a noun, not a verb.
wedding-opsbeatsplan-your-wedding. People scan for what it is, not what it does.
Tip — Ship example data, not real data. Replace your real CSV rows with synthetic ones. Make it obvious. Real users will fill in their own.
Tip — Write a one-line
descriptionin the .cabinet manifest. That's what shows in the registry list. Keep it ≤80 chars.
What templates can't do
- They can't bring your API keys. You add those in Settings after installing.
- They can't bring your private connectors (Gmail, Calendar, etc). The template defines the shape; you authorize per-install.
- They can't auto-fire heartbeats on first install. Cabinet asks you to confirm each one.
Read on
- Philosophy: a team of teams — why templates compose well.
- Org chart & departments — the structure templates ship with.
- cabinets.sh ↗ — the registry itself.