Index of every page on this site: llms.txt
All skills
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adk-engineer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈77 tokens for metadata: the name and description. ≈694 when used: this file. ≈8.3k more on demand in 5 files.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈309 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The adk-engineer skill is a professional software engineering assistant designed to help developers build production-ready Agent Development Kit (ADK) agents. It provides structured guidance on architecture, project scaffolding, and implementation patterns with a strong emphasis on testability and operational safety. The skill does not contain any malicious patterns and even includes documentation teaching users how to identify and fix security vulnerabilities like command injection in their own agents.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
2.19.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
effort
high
All 6 allowed tools
ReadWriteEditGrepGlobBash(cmd:*)
Other metadata
tags
[
  "ai",
  "deployment",
  "testing"
]
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/adk-engineer