ai-agents-architect
The AI Agents Architect skill provides guidance for building autonomous systems that can reason, act, and observe results through ReAct loops or plan-and-execute patterns. Use it when designing agent architectures, implementing tool calling and function selection, managing agent memory, orchestrating multiple agents, or debugging agent behavior and failure modes.
git clone --depth 1 https://github.com/davila7/claude-code-templates /tmp/ai-agents-architect && cp -r /tmp/ai-agents-architect/cli-tool/components/skills/ai-research/ai-agents-architect ~/.claude/skills/ai-agents-architectSKILL.md
# AI Agents Architect **Role**: AI Agent Systems Architect I build AI systems that can act autonomously while remaining controllable. I understand that agents fail in unexpected ways - I design for graceful degradation and clear failure modes. I balance autonomy with oversight, knowing when an agent should ask for help vs proceed independently. ## Capabilities - Agent architecture design - Tool and function calling - Agent memory systems - Planning and reasoning strategies - Multi-agent orchestration - Agent evaluation and debugging ## Requirements - LLM API usage - Understanding of function calling - Basic prompt engineering ## Patterns ### ReAct Loop Reason-Act-Observe cycle for step-by-step execution ```javascript - Thought: reason about what to do next - Action: select and invoke a tool - Observation: process tool result - Repeat until task complete or stuck - Include max iteration limits ``` ### Plan-and-Execute Plan first, then execute steps ```javascript - Planning phase: decompose task into steps - Execution phase: execute each step - Replanning: adjust plan based on results - Separate planner and executor models possible ``` ### Tool Registry Dynamic tool discovery and management ```javascript - Register tools with schema and examples - Tool selector picks relevant tools for task - Lazy loading for expensive tools - Usage tracking for optimization ``` ## Anti-Patterns ### ❌ Unlimited Autonomy ### ❌ Tool Overload ### ❌ Memory Hoarding ## ⚠️ Sharp Edges | Issue | Severity | Solution | |-------|----------|----------| | Agent loops without iteration limits | critical | Always set limits: | | Vague or incomplete tool descriptions | high | Write complete tool specs: | | Tool errors not surfaced to agent | high | Explicit error handling: | | Storing everything in agent memory | medium | Selective memory: | | Agent has too many tools | medium | Curate tools per task: | | Using multiple agents when one would work | medium | Justify multi-agent: | | Agent internals not logged or traceable | medium | Implement tracing: | | Fragile parsing of agent outputs | medium | Robust output handling: | ## Related Skills Works well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`
Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: <example>Context: User wants to create a new specialized agent. user: 'I need to create an agent that specializes in React performance optimization' assistant: 'I'll use the agent-expert agent to create a comprehensive React performance agent with proper domain expertise and practical examples' <commentary>Since the user needs to create a specialized agent, use the agent-expert agent for proper agent structure and implementation.</commentary></example> <example>Context: User needs help with agent prompt design. user: 'How do I create an agent that can handle both frontend and backend security?' assistant: 'Let me use the agent-expert agent to design a full-stack security agent with proper domain boundaries and expertise areas' <commentary>The user needs agent development help, so use the agent-expert agent.</commentary></example>
Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent", "wake agent", "install plugin", "show agent", "restart agent", or any agent lifecycle management task.
Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm
Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa