Skip to content
cccskills
FreePublished on GitHub

adk-engineer

Build and prepare ADK agents for deployment with clear code structure, tool interfaces, tests, and operational safeguards. The skill covers both individual agents and coordinated teams, with architecture plans, implementation changes, and validation checklists.

OriginalShow the original description

Execute software engineer specializing in creating production-ready ADK agents with best practices, code structure, testing, and deployment automation. Use when asked to "build ADK agent", "create agent code", or "engineer ADK application". Trigger with relevant phrases based on skill purpose.

Run score Not tested

See how to install

Good for

  • Build an ADK agent with tests
  • Refactor an existing agent before deployment
  • Design a workflow with multiple agents
  • Prepare deployment and health checks

Files included (7)

  • SKILL.md3.3 KB
  • PRD.md2.8 KB
  • references/ARD.md5.5 KB
  • references/errors.md5.9 KB
  • references/examples.md13.2 KB
  • references/implementation.md4.8 KB
  • scripts/setup-project.sh2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

ADK Engineer

Engineer production-ready Agent Development Kit (ADK) agents and multi-agent systems: clean structure, testability, safe tool usage, and deployment automation.

Overview

Use this skill to design and implement ADK agent code that is maintainable and shippable: clear module boundaries, structured tool interfaces, regression tests, and a deployment checklist (local or Agent Engine).

Prerequisites

  • A target runtime (Python/Java/Go) consistent with the project’s pinned versions
  • ADK installed (and any required model/provider SDKs configured)
  • A test runner available in the repo (unit tests at minimum)
  • If deploying: access to a Google Cloud project and permissions for the chosen deployment target

Instructions

  1. Clarify requirements: agent goals, tool surface, latency/cost constraints, and deployment target.
  2. Propose architecture: single agent vs multi-agent, orchestration pattern, state strategy (Memory Bank / external store).
  3. Scaffold structure: agent entrypoint(s), tool modules, config, and tests.
  4. Implement incrementally:
    • add one tool at a time with input validation and structured outputs
    • add regression tests for each tool and critical prompt flows
  5. Add operational guardrails: retries/backoff, timeouts, logging, and safe error messages.
  6. Validate locally (tests + smoke prompts) and provide a deployment plan (when requested).

Output

  • A concrete architecture plan and file layout
  • Agent and tool implementations (or patches) with tests
  • A validation checklist (commands to run, expected outputs, and failure triage)
  • Optional: deployment instructions and post-deploy health checks

Error Handling

  • Build/test failures: isolate the failing module, minimize the repro, fix, and add a regression test.
  • Tool/runtime errors: enforce structured error responses and safe retries where appropriate.
  • Deployment failures: provide the exact failing command, logs to inspect, and least-privilege IAM fixes.

Examples

Example: Productionizing an existing ADK agent

  • Request: “Refactor this agent into a clean module structure and add tests before we deploy.”
  • Result: reorganized src/ layout, tool boundaries, a test suite, and a deployment checklist.

Example: Multi-agent workflow

  • Request: “Build a validator + deployer + monitor agent team with a sequential orchestrator.”
  • Result: orchestrator skeleton, per-agent responsibilities, and smoke tests for each step.

Resources

  • Full detailed playbook (kept for reference): ${CLAUDE_SKILL_DIR}/references/SKILL.full.md
  • Repo standards (source of truth):
    • 000-docs/6767-a-SPEC-DR-STND-claude-code-plugins-standard.md
    • 000-docs/6767-b-SPEC-DR-STND-claude-skills-standard.md
  • ADK / Agent Engine docs:

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