jeremylongshore/tons-of-skills-marketplace / plugins/ai-ml/jeremy-google-adk/skills/adk-agent-builder
adk-agent-builder
VerifiedScaffold production-ready AI agents on Google's Agent Development Kit (ADK): ReAct-style single agents, multi-agent orchestration (Sequential/Parallel/Loop), tool wiring, evaluation, and optional Vertex AI Agent Engine deployment. Use when building, scaffolding, or deploying ADK agents on Google Cloud, or when wiring ADK tools and orchestration patterns. Trigger with "build an ADK agent", "scaffold an agent on ADK", or "deploy to Agent Engine".
ADK Agent Builder
Build production-ready agents with Google’s Agent Development Kit (ADK): scaffolding, tool wiring, orchestration patterns, testing, and optional deployment to Vertex AI Agent Engine.
Overview
- Creates a minimal, production-oriented ADK scaffold (agent entrypoint, tool registry, config, and tests).
- Supports single-agent ReAct-style workflows and multi-agent orchestration (Sequential/Parallel/Loop).
- Produces a validation checklist suitable for CI (lint/tests/smoke prompts) and optional Agent Engine deployment verification.
Prerequisites
- Python runtime compatible with your project (often Python 3.10+)
google-adkinstalled and importable- If deploying: access to a Google Cloud project with Vertex AI enabled and permissions to deploy Agent Engine runtimes
- Secrets available via environment variables or a secret manager (never hardcoded)
Instructions
- Confirm scope: local-only agent scaffold vs Vertex AI Agent Engine deployment.
- Choose an architecture:
- Single agent (ReAct) for adaptive tool-driven tasks
- Multi-agent system (specialists + orchestrator) for complex, multi-step workflows
- Define the tool surface (built-in ADK tools + any custom tools you need) and required credentials.
- Scaffold the project:
src/agents/,src/tools/,tests/, and a dependency file (pyproject.tomlorrequirements.txt)
- Implement the minimum viable agent and a smoke test prompt; add regression tests for tool failures.
- If deploying, produce an
adk deploy ...command and a post-deploy validation checklist (AgentCard/task endpoints, permissions, logs).
Output
- A repo-ready ADK scaffold (files and directories) plus starter agent code
- Tool stubs and wiring points (where to add new tools safely)
- A test + validation plan (unit tests and a minimal smoke prompt)
- Optional: deployment commands and verification steps for Agent Engine
Error Handling
- Dependency/runtime issues: provide pinned install commands and validate imports.
- Auth/permission failures: identify the missing role/API and propose least-privilege fixes.
- Tool failures/rate limits: add retries/backoff guidance and a regression test to prevent recurrence.
Examples
Example: Scaffold a single ReAct agent
- Request: “Create an ADK agent that summarizes PRs and proposes test updates.”
- Result: agent entrypoint + tool registry + a smoke test command for local verification.
Example: Multi-agent orchestrator
- Request: “Build a supervisor + deployer + verifier team and deploy to Agent Engine.”
- Result: orchestrator skeleton, per-agent responsibilities, and
adk deploy ...+ post-deploy health checks.
Resources
- Implementation patterns (scaffolds, tool wiring, orchestration):
references/implementation.md - Worked examples (single-agent + multi-agent):
references/examples.md - Error-handling and recovery patterns:
references/errors.md - Product / architecture context:
PRD.md,ARD.md - ADK / Agent Engine docs:
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |