adk-agent-builder
Scaffold 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".
What this skill does
# 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-adk` installed 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
1. Confirm scope: local-only agent scaffold vs Vertex AI Agent Engine deployment.
2. Choose an architecture:
- Single agent (ReAct) for adaptive tool-driven tasks
- Multi-agent system (specialists + orchestrator) for complex, multi-step workflows
3. Define the tool surface (built-in ADK tools + any custom tools you need) and required credentials.
4. Scaffold the project:
- `src/agents/`, `src/tools/`, `tests/`, and a dependency file (`pyproject.toml` or `requirements.txt`)
5. Implement the minimum viable agent and a smoke test prompt; add regression tests for tool failures.
6. 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): `${CLAUDE_SKILL_DIR}/references/implementation.md`
- Worked examples (single-agent + multi-agent): `${CLAUDE_SKILL_DIR}/references/examples.md`
- Error-handling and recovery patterns: `${CLAUDE_SKILL_DIR}/references/errors.md`
- Product / architecture context: `${CLAUDE_SKILL_DIR}/PRD.md`, `${CLAUDE_SKILL_DIR}/ARD.md`
- ADK / Agent Engine docs:
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.