Skip to content
cccskills
FreePublished on GitHub

adk-deployment-specialist

Build and deploy Google ADK agents to Vertex AI Agent Engine. Define sequential, parallel, or looping workflows and A2A interfaces for agent communication, then verify endpoints and add logging and retry behavior.

OriginalShow the original description

Deploy and orchestrate Vertex AI ADK agents using A2A protocol. Manages AgentCard discovery, task submission, Code Execution Sandbox, and Memory Bank. Use when asked to "deploy ADK agent" or "orchestrate agents". Trigger with phrases like 'deploy', 'infrastructure', or 'CI/CD'.

jeremylongshore/tons-of-skills-marketplace
Works withGoogle Cloud

Run score Not tested

See how to install

Good for

  • Deploying ADK agents to Vertex AI Agent Engine
  • Designing sequential, parallel, or looping agent workflows
  • Verifying AgentCard discovery and task submission APIs

Files included (9)

  • SKILL.md2.7 KB
  • references/ARD.md4.9 KB
  • references/errors.md6.0 KB
  • references/examples.md3.0 KB
  • references/how-it-works.md5.1 KB
  • references/PRD.md4.0 KB
  • references/workflow-examples.md4.6 KB
  • scripts/deploy-agent.sh4.4 KB
  • scripts/test-a2a-protocol.py8.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Adk Deployment Specialist

Overview

Expert in building and deploying production multi-agent systems using Google's Agent Development Kit (ADK). Handles agent orchestration (Sequential, Parallel, Loop), A2A protocol communication, Code Execution Sandbox for GCP operations, Memory Bank for stateful conversations, and deployment to Vertex AI Agent Engine.

Prerequisites

  • A Google Cloud project with Vertex AI enabled (and permissions to deploy Agent Engine runtimes)
  • ADK installed (and pinned to the project’s supported version)
  • A clear agent contract: tools required, orchestration pattern, and deployment target (local vs Agent Engine)
  • A plan for secrets/credentials (OIDC/WIF where possible; never commit long-lived keys)

Instructions

  1. Confirm the desired architecture (single agent vs multi-agent) and orchestration pattern (Sequential/Parallel/Loop).
  2. Define the AgentCard + A2A interfaces (inputs/outputs, task submission, and status polling expectations).
  3. Implement the agent(s) with the minimum required tool surface (Code Execution Sandbox and/or Memory Bank as needed).
  4. Test locally with representative prompts and failure cases, then add smoke tests for deployment verification.
  5. Deploy to Vertex AI Agent Engine and validate the generated endpoints (/.well-known/agent-card, task send/status APIs).
  6. Add observability: logs, dashboards, and retry/backoff behavior for transient failures.

Output

  • Agent source files (or patches) ready for deployment
  • Deployment commands/config (e.g., vertexai.Client.agent_engines.create() invocation + required parameters)
  • A verification checklist for Agent Engine endpoints (AgentCard + task APIs) and security posture

Error Handling

See references/errors.md for comprehensive error handling.

Examples

See references/examples.md for detailed examples.

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

abridge-ci-integration

FreeSummary

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

abridge-common-errors

FreeSummary

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

abridge-core-workflow-a

FreeSummary

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

abridge-core-workflow-b

FreeSummary

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

abridge-cost-tuning

FreeSummary

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

abridge-debug-bundle

FreeSummary

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