Skip to content
cccskills
FreePublished on GitHub

adk-agent-builder

Build a starter project for AI agents using Google Agent Development Kit (ADK). It can outline single-agent or multi-agent workflows, connect tools, add basic tests, and provide optional deployment and verification steps for Vertex AI Agent Engine.

OriginalShow the original description

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".

Works withGoogle Cloud

Run score Not tested

See how to install

Good for

  • Starting a ReAct-style ADK agent project
  • Planning a multi-agent workflow with an orchestrator
  • Preparing an ADK agent for Agent Engine deployment

Files included (6)

  • SKILL.md3.8 KB
  • ARD.md3.8 KB
  • PRD.md6.8 KB
  • references/errors.md3.2 KB
  • references/examples.md3.7 KB
  • references/implementation.md4.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

See all skills by jeremylongshore

Report a problem with this skill