GooglePier Paolo Ippolito, Shahin SaadatiExplainer
Three layers, one repo: a tour of google/adk-recipes
Summary
The google/adk-recipes repository serves as the single source of truth for ADK content across Google Cloud’s Agent Platform, including the Agents CLI, Agent Garden, and Gemini Enterprise app. It is organized into three top-level folders: core/ with reference patterns curated by the Agents CLI and DevRel teams, plugins/ with installable vertical skills packaged as Plugin Recipes conforming to the Agent Plugins v1.0.0 spec, and contrib/ with end-to-end deployable services in five languages. Every recipe ships a validated manifest.yaml and an AGENTS.md written primarily for AI coding assistants, and CI enforces the standards on every pull request. The core/ layer features Horizon, a reference harness for long-horizon memory agents that handles cross-session memory, per-user sandboxing, guardrails, and multi-step task orchestration. The retail Plugin Recipe includes product-search and virtual-tryon skills using Vector Search 2.0 and Gemini models, with deployable counterparts in contrib/ that can be surfaced on five deployment personas.
Takeaways
The repository is split into three top-level folders: core/ for reference patterns, plugins/ for installable vertical skills packaged as Plugin Recipes, and contrib/ for end-to-end deployable services in five languages.
Every recipe includes an AGENTS.md file written primarily for AI coding assistants, enabling automatic discovery and installation without requiring human reading.
Horizon, in core/, provides a reference harness for building long-horizon memory agents with cross-session memory, per-user sandboxing, guardrails, and resumable multi-step tasks.
FAQ
What is the purpose of AGENTS.md in each recipe?
AGENTS.md is written primarily for AI coding assistants to describe the recipe and how to use it. It enables automatic discovery and installation by the assistant without requiring human reading.
How does Horizon handle long-horizon agent interactions?
Horizon uses cross-session memory, per-user sandboxing, secrets management, guardrails against runaway behavior, and orchestration primitives to make multi-step tasks resumable across days of interaction.
What is the structure of a Plugin Recipe like the retail plugin?
The retail Plugin Recipe consists of a top-level plugin.json manifest and skills folders, each containing a SKILL.md conversational installer, README.md, EVAL.yaml quality gates, and necessary scripts and assets.
Source and freshness
- Source
- developers.googleblog.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.