marketing-team-eve-template vs adk-recipes
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
adk-recipes
Runnable Agent Development Kit recipes, from single patterns to deployable agents
| What we compare | marketing-team-eve-template | adk-recipes |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 26, niche | 75, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 28, weak | 66, fair |
| Easy to run | 67, easy | 0, hard |
| Agent-ready | 70, partly | 30, minimal |
| Facts from GitHub and the README | ||
| Stars | 450 | 10.4k |
| License | MIT (permissive) | Apache-2.0 (permissive) |
| Last commit | Aug 2026 | Oct 2026 |
| Last release | None published | None published |
| Language | TypeScript | Python |
| 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
adk-recipes
A recipe collection for Google's Agent Development Kit: core/ holds single-pattern agents (OAuth flows, session memory, guardrails, RAG), contrib/ holds deployable vertical agents targeting Agent Engine, Cloud Run and Gemini Enterprise, and plugins/ holds skills packaged with SKILL.md and EVAL.yaml. Each recipe has its own README; ADK SDKs exist for Python, TypeScript, Go, Java and Kotlin. For teams standardizing on ADK and Google Cloud.
Who it is for: Teams standardizing on ADK and Google Cloud
Strengths
- Core recipes isolate one pattern each, so they lift cleanly into your project
- Vertical agents include deploy paths to Agent Engine and Cloud Run
- Recipe checklist and handbook define a contribution standard; tests and AGENTS.md included
- Committed within the last day
Weaknesses
- Root README is an index; no single app, no shared setup
- Gemini and Google Cloud are the assumed model and deploy target
- README states recipes are demonstrations, not for production use
- Mixed languages and maturity across folders
- Python, google, google-adk
- Needs google-adk, google-api-key-or-vertex-ai