agent-orchestration-patterns

Standardize Pydantic tool schemas and agent state for multi-agent orchestration.

2|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/ricardoroche/ricardos-claude-code --skill agent-orchestration-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-orchestration-patterns
Source: https://github.com/ricardoroche/ricardos-claude-code/tree/main/.claude/skills/agent-orchestration-patterns
Command: npx skills add https://github.com/ricardoroche/ricardos-claude-code --skill agent-orchestration-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pydantic, httpx.

What problem does it solve?

This Skill provides essential patterns for designing and managing complex multi-agent AI systems. It tackles challenges like inconsistent tool interfaces, stateless conversations, and unreliable tool execution, enabling developers to build robust, scalable, and maintainable agentic applications.

Core Features & Use Cases

  • Pydantic Tool Schemas: Enforces strict input/output validation for AI tools using Pydantic, ensuring predictable interactions.
  • Agent State Management: Provides patterns for maintaining conversation history and agent state across turns, enabling coherent multi-step interactions.
  • Robust Tool Execution: Implements error handling, timeouts, and logging for tool calls, making agent interactions with external systems reliable.
  • Orchestration Patterns: Guides on sequential, parallel, router-based, and hierarchical agent orchestration for diverse workflow needs.
  • Use Case: A team is building an AI assistant that can research, synthesize, and write reports. This skill helps them implement a SequentialOrchestrator to chain a research agent, a synthesis agent, and a writer agent, ensuring each step is executed reliably and passes its output correctly.

Quick Start

Design a multi-agent system that sequentially researches a topic, synthesizes the information, and then writes a summary.

Frequently Asked Questions about agent-orchestration-patterns

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

FAQPage Schema
How do I build a multi-agent workflow that executes tasks sequentially?

Multi-agent workflows execute sequentially by chaining agents through an orchestrator that passes each agent's output as input to the next. This Skill provides orchestration patterns that standardize tool schemas with Pydantic and manage agent state across turns, ensuring reliable handoffs between research, synthesis, and writing agents or similar multi-step processes.

What's the best way to validate tool inputs and outputs in an LLM agent system?

Pydantic-based tool schemas enforce strict input and output validation, preventing malformed data from reaching external systems. This Skill standardizes tool interface design so agents reliably interact with APIs, databases, and services, reducing runtime errors in tool-calling pipelines built with LangChain, LlamaIndex, or Anthropic tools.

How do I maintain conversation history and state in a multi-agent system?

Agent state management patterns preserve conversation history and context across interaction turns, enabling coherent multi-step reasoning. This Skill provides structured state management using Pydantic to ensure agents recall prior decisions and information, supporting complex workflows where later agents depend on earlier results.

Can I integrate tool calling with error handling and timeouts across multiple agents?

Yes. This Skill implements comprehensive error handling, timeouts, and logging within tool execution, making agent interactions with external systems reliable and debuggable. It covers sequential, parallel, router-based, and hierarchical orchestration patterns so you can choose the right execution model for your workflow.

What's the difference between sequential and hierarchical agent orchestration?

Sequential orchestration chains agents linearly, passing outputs forward; hierarchical orchestration uses a parent agent to delegate subtasks to child agents and aggregate results. This Skill covers both patterns plus parallel and router-based approaches, helping you select the orchestration strategy that matches your workflow complexity and dependencies.

Do I need Pydantic to build multi-agent systems, or can I use unstructured data?

Pydantic is not strictly required, but this Skill enforces it to prevent tool interface inconsistencies and validation failures at scale. Unstructured data leads to unpredictable agent behavior; Pydantic schemas ensure every tool call is validated before execution, reducing debugging and making orchestration patterns reliable across agent frameworks.