---
name: adk-engineer
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.'
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*)
version: 2.19.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
effort: high
tags:
  - ai
  - deployment
  - testing
compatibility: Designed for Claude Code
title: adk-engineer
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adk-engineer
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [PRD.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adk-engineer/PRD.md), [references/ARD.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adk-engineer/references/ARD.md), [references/errors.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adk-engineer/references/errors.md), [references/examples.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adk-engineer/references/examples.md), [references/implementation.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adk-engineer/references/implementation.md), [scripts/setup-project.sh](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adk-engineer/scripts/setup-project.sh).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/adk-engineer`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/adk-engineer`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/adk-engineer) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/adk-engineer`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/adk-engineer --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/adk-engineer --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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:
