Agent Architect

Design ADK agent architectures from user requirements without writing code.

Updated May 13, 2026
One-click install
npx skills add https://github.com/hpuri/salus-a2ui --skill agent-architect-hpuri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Agent Architect
Source: https://github.com/hpuri/salus-a2ui/tree/main/skills/agent_architect
Command: npx skills add https://github.com/hpuri/salus-a2ui --skill agent-architect-hpuri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps design robust, scalable, and simple ADK agent architectures by translating user requirements into architectural designs without writing code.

Core Features & Use Cases

  • Deep Requirements Analysis: Analyze user requirements for gaps, ambiguity, and non-functional requirements.
  • Pattern Selection & Validation: Choose the appropriate agent pattern and validate it with the user.
  • ADK Compliance: Ensure compliance with ADK standards, such as handling user interaction outside non-interactive loops.
  • Collaborative Design: Collaborate with users to design major workflows before finalizing the document.
  • Architecture Definition: Define agent identity, scope boundaries, logic, flow, and dependencies.
  • Evaluation Strategy: Define measurable success criteria for the architecture.

Quick Start

Use the Agent Architect skill to design the architecture for a new ADK agent based on the provided requirements.

Frequently Asked Questions about Agent Architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an ADK agent architecture without writing code?

To design an ADK agent architecture without writing code, analyze user requirements, select appropriate agent patterns, validate ADK compliance, and define components and evaluation strategies collaboratively.

What is the process for analyzing requirements to select an agent pattern?

Analyzing requirements involves identifying gaps, ambiguity, and non-functional requirements to select and validate the appropriate agent pattern, ensuring the major workflow design aligns with ADK standards.

How do I ensure ADK compliance when defining agent architecture?

To ensure ADK compliance, verify that the defined agent architecture handles user interaction outside non-interactive loops and adheres to ADK standards throughout the pattern selection and workflow design.

What's the best way to define evaluation strategies for complex agent architectures?

The best way to define evaluation strategies is to establish measurable success criteria during the architecture definition phase, covering agent identity, scope boundaries, logic, flow, and dependencies.

Can I use this approach to design architectures for non-interactive ADK agents?

Yes, you can design architectures for non-interactive ADK agents by ensuring ADK compliance, specifically by handling user interaction outside non-interactive loops during the architecture definition process.