marketing-team-eve-template vs personal-agent-template
Two of the top agent backends, side by side: score, setup, license, activity and what each review found.
marketing-team-eve-template
eve lead agent delegating to five marketing specialists with approval gates
personal-agent-template
eve and Nuxt personal agent with Slack, GitHub, Linear and per-user memory
| What we compare | marketing-team-eve-template | personal-agent-template |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 26, niche | 30, niche |
| Freshness | 100, active | 100, active |
| Maintenance | 28, weak | 11, weak |
| Easy to run | 67, easy | 67, easy |
| Agent-ready | 70, partly | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 450 | 476 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Aug 2026 | Sep 2026 |
| Last release | None published | None published |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
marketing-team-eve-template
An eve project where a lead agent briefs one of five specialists (product marketing, content, social, SEO, email) and returns their output as Notion pages, Typefully drafts or Resend campaigns through MCP connections. A shared brand context document in Vercel Blob is the only state, sends and scheduled publishes pause for approval in Slack or the terminal, and models come through Vercel AI Gateway. For teams studying multi-agent delegation.
Who it is for: Teams studying multi-agent delegation with real tool writes
Strengths
- Approval matrix is enforced in connection tool lists, not only in prompts
- Each specialist is a directory; the lead routes on its description alone
- Remote agents let a specialist live in its own deployment
- CLAUDE.md, AGENTS.md and architecture docs included
Weaknesses
- Needs Notion, Resend and Slack connectors via Vercel Connect plus a Typefully key
- Tied to eve, Vercel AI Gateway, Blob and Sandbox
- No tests; pnpm validate covers lint and typecheck
- No .env.example
- TypeScript, eve, ai-gateway, ai-sdk
- Needs vercel-connect, notion, resend, slack, typefully-api-key, vercel-blob, ai-gateway
- GitHub template
personal-agent-template
A Nuxt app plus an eve agent runtime: Better Auth email login, web chat with threads that eve persists, Slack DMs and mentions linked to the same user, GitHub tools with durable approval on writes, Linear via Vercel Connect MCP, and a bounded per-user memory document in Vercel Blob. Postgres via Drizzle holds users and links; on Vercel it deploys as two services. For developers building a single-user or small-team assistant on eve.
Who it is for: Developers building a personal or small-team assistant on eve
Strengths
- Memory is per authenticated principal, recalled before every turn and after compaction
- Slack identity links to the web profile so context follows the user
- Write actions on GitHub gate on durable approvals
- CI workflow, CLAUDE.md and AGENTS.md present
Weaknesses
- Needs Vercel Connect for Slack and Linear; self-hosting those integrations is on you
- No model provider named in the README; configured through eve
- No tests listed; CI covers typecheck and build
- Requires Node 24+
- TypeScript, eve, ai-sdk
- Needs postgres, vercel-blob, vercel-connect
- GitHub template
- env example file
- sign-in: Better Auth