AI Agents Production Patterns

VerifiedSafe

Production-grade patterns for building AI agents with MCP integration, agentic RAG, handoff orchestration, guardrails, and observability.

Sby Skills Guide Bot
Data & AIAdvanced
8/2/2026
Claude Code
#ai-agents#mcp#agent-orchestration#guardrails#observability

Recommended for

Automated summary

Provides production-oriented patterns for designing, evaluating, and deploying LLM agents, covering MCP tool integration, agentic RAG, handoff orchestration, guardrails, and observability.

Strengths

  • Includes a decision tree and quick-reference table that map agent types to control flow, interfaces, and suitable use cases.
  • Anchors guidance in production concerns: bounded tools, auditable state, OpenTelemetry tracing, human-in-the-loop, and OWASP LLM Top 10.
  • Defines clear scope boundaries and points to companion skills for prompting, retrieval, security, and inference depth.
  • Covers multiple architectures, from workflow and tool-using agents to planner/executor, multi-agent, OS, and SWE agents.

Limitations

  • Stays intentionally high-level and does not supply full implementation code, schemas, or end-to-end examples.
  • Assumes prior familiarity with LLM agents, MCP, and production deployment concepts.
  • Deep topics are delegated to linked skills, so it is not a standalone guide for prompt engineering, RAG tuning, or security hardening.
When to use it

Use when architecting or operationalizing an AI agent system that needs MCP tools, RAG, handoffs, guardrails, or rollout and evaluation planning.

When not to use it

Do not use for detailed prompt templates, retrieval/chunking tuning, security hardening, or inference optimization; use the dedicated companion skills instead.

Security analysis

Safe
Quality score84/100

The skill is a documentation and navigation hub for AI agent development patterns. It contains no destructive commands, no credential or secret handling, no obfuscated payloads, no tool declarations, and no instructions to bypass safety controls. References to MCP, A2A, OS agents, and external standards are conceptual and guarded by recommendations for sandboxing, allowlists, human-in-the-loop, and observability.

No concerns found

How this analysis is made

Examples

Tool-using agent design
Design a production tool-using agent that queries Postgres and Jira through MCP, with tool schemas, retries, timeouts, and OpenTelemetry tracing. Include the control flow and a guardrail checklist.
Multi-agent rollout plan
Create an evaluation and rollout plan for a multi-agent customer-support system with handoff contracts, human-in-the-loop approval, and OWASP LLM Top 10 controls.
Agent architecture choice
Help me choose between a workflow agent, a planner/executor, and a multi-agent orchestration for a knowledge-base assistant. Compare risks, control flow, and when each is appropriate.

name: ai-agents description: Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)

AI Agents Development — Production Skill Hub

Modern Best Practices (December 2025): deterministic control flow, bounded tools, auditable state, MCP-based tool integration, handoff-first orchestration, multi-layer guardrails, OpenTelemetry tracing, and human-in-the-loop controls (OWASP LLM Top 10: https://owasp.org/www-project-top-10-for-large-language-model-applications/).

This skill provides production-ready operational patterns for designing, building, evaluating, and deploying AI agents. It centralizes procedures, checklists, decision rules, and templates used across RAG agents, tool-using agents, OS agents, and multi-agent systems.

No theory. No narrative. Only what Claude can execute.


When to Use This Skill

Claude should activate this skill whenever the user asks for:

  • Designing an agent (LLM-based, tool-based, OS-based, or multi-agent).
  • Scoping capability maturity and rollout risk for new agent behaviors.
  • Creating action loops, plans, workflows, or delegation logic.
  • Writing tool definitions, MCP tools, schemas, or validation logic.
  • Generating RAG pipelines, retrieval modules, or context injection.
  • Building memory systems (session, long-term, episodic, task).
  • Creating evaluation harnesses, observability plans, or safety gates.
  • Preparing CI/CD, rollout, deployment, or production operational specs.
  • Producing any template in /resources/ or /templates/.
  • Implementing MCP servers or integrating Model Context Protocol.
  • Setting up agent handoffs and orchestration patterns.
  • Configuring multi-layer guardrails and safety controls.
  • For prompt scaffolds, retrieval tuning, or security depth, see Scope Boundaries below.

Scope Boundaries (Use These Skills for Depth)


Quick Reference

| Agent Type | Core Control Flow | Interfaces | MCP/A2A | When to Use | |------------|-----------|------------|---------|-------------| | Workflow Agent (FSM/DAG) | Explicit state transitions | State store, tool allowlist | MCP | Deterministic, auditable flows | | Tool-Using Agent | Route → call tool → observe | Tool schemas, retries/timeouts | MCP | External actions (APIs, DB, files) | | RAG Agent | Retrieve → answer → cite | Retriever, citations, ACLs | MCP | Knowledge-grounded responses | | Planner/Executor | Plan → execute steps with caps | Planner prompts, step budget | MCP (+A2A) | Multi-step problems with bounded autonomy | | Multi-Agent (Orchestrated) | Delegate → merge → validate | Handoff contracts, eval gates | A2A | Specialization with explicit handoffs | | OS Agent | Observe UI → act → verify | Sandbox, UI grounding | MCP | Desktop/browser control under strict guardrails | | Code/SWE Agent | Branch → edit → test → PR | Repo access, CI gates | MCP | Coding tasks with review/merge controls |


Decision Tree: Choosing Agent Architecture

What does the agent need to do?
    ├─ Answer questions from knowledge base?
    │   ├─ Simple lookup? → RAG Agent (LangChain/LlamaIndex + vector DB)
    │   └─ Complex multi-step? → Agentic RAG (iterative retrieval + reasoning)
    │
    ├─ Perform external actions (APIs, tools, functions)?
    │   ├─ 1-3 tools, linear flow? → Tool-Using Agent (LangGraph + MCP)
    │   └─ Complex workflows, branching? → Planning Agent (ReAct/Plan-Execute)
    │
    ├─ Write/modify code autonomously?
    │   ├─ Single file edits? → Tool-Using Agent with code tools
    │   └─ Multi-file, issue resolution? → Code/SWE Agent (HyperAgent pattern)
    │
    ├─ Delegate tasks to specialists?
    │   ├─ Fixed workflow? → Multi-Agent Sequential (A → B → C)
    │   ├─ Manager-Worker? → Multi-Agent Hierarchical (Manager + Workers)
    │   └─ Dynamic routing? → Multi-Agent Group Chat (collaborative)
    │
    ├─ Control desktop/browser?
    │   └─ OS Agent (Anthropic Computer Use + MCP for system access)
    │
    └─ Hybrid (combination of above)?
        └─ Planning Agent that coordinates:
            - Tool-using for actions (MCP)
            - RAG for knowledge (MCP)
            - Multi-agent for delegation (A2A)
            - Code agents for implementation

Protocol Selection:

  • Use MCP for: Tool access, data retrieval, single-agent integration
  • Use A2A for: Agent-to-agent handoffs, multi-agent coordination, task delegation

Core Concepts (Vendor-Agnostic)

Control Flow Options

  • Reactive: direct tool routing per user request (fast, brittle if unbounded).
  • Workflow (FSM/DAG): explicit states and transitions (default for deterministic production).
  • Planner/Executor: plan with strict budgets, then execute step-by-step (use when branching is unavoidable).
  • Orchestrated multi-agent: separate roles with validated handoffs (use when specialization is required).

Memory Types (Tradeoffs)

  • Short-term (session): cheap, ephemeral; best for conversational continuity.
  • Episodic (task): scoped to a case/ticket; supports audit and replay.
  • Long-term (profile/knowledge): high risk; requires consent, retention limits, and provenance.

Failure Handling (Production Defaults)

  • Classify errors: retriable vs fatal vs needs-human.
  • Bound retries: max attempts, backoff, jitter; avoid retry storms.
  • Fallbacks: degraded mode, smaller model, cached answers, or safe refusal.

Do / Avoid

Do

  • Do keep state explicit and serializable (replayable runs).
  • Do enforce tool allowlists, scopes, and idempotency for side effects.
  • Do log traces/metrics for model calls and tool calls (OpenTelemetry GenAI semantic conventions: https://opentelemetry.io/docs/specs/semconv/gen-ai/).

Avoid

  • Avoid runaway autonomy (unbounded loops or step counts).
  • Avoid hidden state (implicit memory that cannot be audited).
  • Avoid untrusted tool outputs without validation/sanitization.

Navigation: Core Concepts & Patterns

Governance & Maturity

  • Agent Maturity & Governance - resources/agent-maturity-governance.md
    • Capability maturity levels (L0-L4)
    • Identity & policy enforcement
    • Fleet control and registry management
    • Deprecation rules and kill switches

Modern Best Practices

  • Modern Best Practices - resources/modern-best-practices.md
    • Model Context Protocol (MCP)
    • Agent-to-Agent Protocol (A2A)
    • Agentic RAG (Dynamic Retrieval)
    • Multi-layer guardrails
    • LangGraph over LangChain
    • OpenTelemetry for agents

Context Management

Core Operational Patterns

  • Operational Patterns - resources/operational-patterns.md
    • Agent loop pattern (PLAN → ACT → OBSERVE → UPDATE)
    • OS agent action loop
    • RAG pipeline pattern
    • Tool specification
    • Memory system pattern
    • Multi-agent workflow
    • Safety & guardrails
    • Observability
    • Evaluation patterns
    • Deployment & CI/CD

Navigation: Protocol Implementation


Navigation: Agent Capabilities

Skill Packaging & Sharing


Navigation: Production Operations


Navigation: Templates (Copy-Paste Ready)

Checklists

Core Agent Templates

RAG Templates

Tool Templates

Multi-Agent Templates

Service Layer Templates


External Sources Metadata

  • Curated References - data/sources.json Authoritative sources spanning standards, protocols, and production agent frameworks

Shared Utilities (Centralized patterns — extract, don't duplicate)


Related Skills

This skill integrates with complementary Claude Code skills:

Core Dependencies

  • ../ai-llm/ - LLM patterns, prompt engineering, and model selection for agents
  • ../ai-rag/ - Deep RAG implementation: chunking, embedding, reranking
  • ../ai-prompt-engineering/ - System prompt design, few-shot patterns, reasoning strategies

Production & Operations

Supporting Patterns

Usage pattern: Start here for agent architecture, then reference specialized skills for deep implementation details.


Usage Notes for Claude

  • Modern Standards: Default to MCP for tools, agentic RAG for retrieval, handoff-first for multi-agent
  • Lightweight SKILL.md: Use this file for quick reference and navigation
  • Drill-down resources: Reference detailed resources for implementation guidance
  • Copy-paste templates: Use templates when the user asks for structured artifacts
  • External sources: Reference data/sources.json for authoritative documentation links
  • No theory: Never include theoretical explanations; only operational steps

Key Modern Migrations

Traditional → Modern:

  • Custom APIs → Model Context Protocol (MCP)
  • Static RAG → Agentic RAG with contextual retrieval
  • Ad-hoc handoffs → Versioned handoff APIs with JSON Schema
  • Single guardrail → Multi-layer defense (5+ layers)
  • LangChain agents → LangGraph stateful workflows
  • Custom observability → OpenTelemetry GenAI standards
  • Model-centric → Context engineering-centric

AI-Native SDLC Pattern (Delegate → Review → Own)

  • Plan: Have the agent draft PLAN.md or use a planning tool; require code-path trace, dependency map, and risk/edge-case list before build starts.
  • Design: Convert mocks to components; enforce design tokens/style guides; surface accessibility gaps; keep MCP-linked component libraries in context.
  • Build: Let the agent scaffold end-to-end (models/APIs/UI/tests/docs); enforce long-run guardrails (time cap, allowed commands/tools, commit/PR gating, kill switch).
  • Test: Demand failing test first; agent generates and runs suites; require coverage deltas and flaky-test notes; human reviews assertions and fixtures.
  • Review: Agent runs first-pass review tuned for P0/P1; human focuses on architecture, performance, safety, and migration risk; always own final merge.
  • Document: Agent drafts PR summaries, module/file notes, and mermaid diagrams; require doc updates in the same run; human adds “why” and approvals.
  • Deploy & Maintain: Agent links logs/metrics via MCP for triage; propose hotfixes with rollback plans; human approves rollouts; track drift/regressions with evals.

Executive Briefing (Optional)

  • Value: Coding agents compress SDLC time; delegate mechanical work, keep humans on intent/architecture; measurable gains come from tight guardrails plus eval loops.
  • Cost & Risk: Training vs inference economics; long runs need caps/kill switches; data/secret handling and supply-chain policies stay human-owned.
  • Governance: Multi-layer guardrails (policy prompt, tool allowlist, auth scopes, eval gates, audit logs); require human sign-off for deploys and safety-sensitive changes.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/ai-agents-production-patterns-msba3nft' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ai-agents-production-patterns-msba3nft/download' --output '.skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md.part' && mv '.skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md.part' '.skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Quick Reference
Agent TypeCore Control FlowInterfacesMCP/A2AWhen to Use
Workflow Agent (FSM/DAG)Explicit state transitionsState store, tool allowlistMCPDeterministic, auditable flows
Tool-Using AgentRoute → call tool → observeTool schemas, retries/timeoutsMCPExternal actions (APIs, DB, files)
RAG AgentRetrieve → answer → citeRetriever, citations, ACLsMCPKnowledge-grounded responses
Planner/ExecutorPlan → execute steps with capsPlanner prompts, step budgetMCP (+A2A)Multi-step problems with bounded autonomy
Multi-Agent (Orchestrated)Delegate → merge → validateHandoff contracts, eval gatesA2ASpecialization with explicit handoffs
OS AgentObserve UI → act → verifySandbox, UI groundingMCPDesktop/browser control under strict guardrails
Code/SWE AgentBranch → edit → test → PRRepo access, CI gatesMCPCoding tasks with review/merge controls

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md' && test -s '.skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ai-agents' && cp -R '.skill-downloads/ai-agents-production-patterns-msba3nft' '.claude/skills/ai-agents'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/ai-agents-production-patterns-msba3nft'

openskills read 'ai-agents-production-patterns-msba3nft'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills