Synthèse automatique
Ce skill propose des patrons opérationnels pour concevoir, évaluer et déployer des agents IA en production, avec intégration d'outils MCP, RAG agentique, orchestration par handoffs, garde-fous et observabilité.
Points forts
- Fournit un arbre de décision et un tableau de référence rapide qui relient chaque type d'agent à son flux de contrôle, ses interfaces et ses cas d'usage.
- Intègre dès le départ des exigences de production : outils bornés, état auditable, traçage OpenTelemetry, human-in-the-loop et OWASP LLM Top 10.
- Délimite clairement son périmètre et renvoie aux skills complémentaires pour le prompting, la récupération, la sécurité et l'inférence.
- Couvre plusieurs architectures : workflow, agent outillé, RAG, planificateur/exécuteur, multi-agent, agent OS et agent de code.
Limites
- Reste volontairement au niveau des principes : peu de code complet, de schémas détaillés ou d'exemples de bout en bout.
- Suppose une familiarité préalable avec les agents LLM, MCP et les contraintes de mise en production.
- Les sujets approfondis sont délégués à des skills liés ; ce n'est donc pas un guide autonome pour le prompting, le réglage du RAG ou le durcissement sécurité.
À utiliser pour concevoir ou industrialiser un système d'agents IA nécessitant des outils MCP, du RAG, des handoffs, des garde-fous ou un plan d'évaluation et de déploiement.
À éviter pour des modèles de prompts détaillés, le réglage du chunking/retrieval, le durcissement sécurité ou l'optimisation d'inférence ; préférer les skills spécialisés.
Analyse de sécurité
SûrThe 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.
Aucun point d'attention détecté
Comment cette analyse est faiteExemples
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.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.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)
- Prompt scaffolds & structured outputs → ai-prompt-engineering
- RAG retrieval & chunking → ai-rag
- Search tuning (BM25/HNSW/hybrid) → ai-rag
- Security/guardrails → ai-mlops
- Inference optimization → ai-llm-inference
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
- Context Engineering -
resources/context-engineering.md- Progressive disclosure
- Session management
- Memory provenance
- Retrieval timing
- Multimodal context
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
-
MCP Practical Guide -
resources/mcp-practical-guide.mdBuilding MCP servers, tool integration, and standardized data access -
MCP Server Builder -
resources/mcp-server-builder.mdEnd-to-end checklist for workflow-focused MCP servers (design → build → test) -
A2A Handoff Patterns -
resources/a2a-handoff-patterns.mdAgent-to-agent communication, task delegation, and coordination protocols -
Protocol Decision Tree -
resources/protocol-decision-tree.mdWhen to use MCP vs A2A, decision framework, and selection criteria
Navigation: Agent Capabilities
-
Agent Operations -
resources/agent-operations-best-practices.mdAction loops, planning, observation, and execution patterns -
RAG Patterns -
resources/rag-patterns.mdContextual retrieval, agentic RAG, and hybrid search strategies -
Memory Systems -
resources/memory-systems.mdSession, long-term, episodic, and task memory architectures -
Tool Design & Validation -
resources/tool-design-specs.mdTool schemas, validation, error handling, and MCP integration
Skill Packaging & Sharing
-
Skill Lifecycle -
resources/skill-lifecycle.mdScaffold, validate, package, and share Claude skills with teams (Slack-ready) -
API Contracts for Agents -
resources/api-contracts-for-agents.mdRequest/response envelopes, safety gates, streaming/async patterns, error taxonomy -
Multi-Agent Patterns -
resources/multi-agent-patterns.mdManager-worker, sequential, handoff, and group chat orchestration -
OS Agent Capabilities -
resources/os-agent-capabilities.mdDesktop automation, UI grounding, and computer use patterns -
Code/SWE Agents -
resources/code-swe-agents.mdSE 3.0 paradigm, autonomous coding patterns, SWE-Bench, HyperAgent architecture
Navigation: Production Operations
-
Evaluation & Observability -
resources/evaluation-and-observability.mdOpenTelemetry GenAI, metrics, LLM-as-judge, and monitoring -
Deployment, CI/CD & Safety -
resources/deployment-ci-cd-and-safety.mdMulti-layer guardrails, HITL controls, NIST AI RMF, production checklists
Navigation: Templates (Copy-Paste Ready)
Checklists
- Agent Design & Safety Checklist -
templates/checklists/agent-safety-checklist.mdGo/No-Go safety gate: permissions, HITL triggers, eval gates, observability, rollback
Core Agent Templates
-
Standard Agent Template -
templates/core/agent-template-standard.mdFull production spec: memory, tools, RAG, evaluation, observability, safety -
Specialized Agent Template -
templates/core/agent-template-specialized.mdDomain-specific agents with custom capabilities and constraints -
Quick Agent Template -
templates/core/agent-template-quick.mdMinimal viable agent for rapid prototyping
RAG Templates
-
Basic RAG -
templates/rag/rag-basic.mdSimple retrieval-augmented generation pipeline -
Advanced RAG -
templates/rag/rag-advanced.mdContextual retrieval, reranking, and agentic RAG patterns -
Hybrid Retrieval -
templates/rag/hybrid-retrieval.mdSemantic + keyword search with BM25 fusion
Tool Templates
-
Tool Definition -
templates/tools/tool-definition.mdMCP-compatible tool schemas with validation and error handling -
Tool Validation Checklist -
templates/tools/tool-validation-checklist.mdTesting, security, and production readiness checks
Multi-Agent Templates
-
Manager-Worker Template -
templates/multi-agent/manager-worker-template.mdOrchestration pattern with task delegation and result aggregation -
Evaluator-Router Template -
templates/multi-agent/evaluator-router-template.mdDynamic routing with quality assessment and domain classification
Service Layer Templates
- FastAPI Agent Service -
../dev-api-design/templates/fastapi/fastapi-complete-api.mdAuth, pagination, validation, error handling; extend with model lifespan loads, SSE, background tasks
External Sources Metadata
- Curated References -
data/sources.jsonAuthoritative sources spanning standards, protocols, and production agent frameworks
Shared Utilities (Centralized patterns — extract, don't duplicate)
- ../software-clean-code-standard/utilities/llm-utilities.md — Token counting, streaming, cost estimation
- ../software-clean-code-standard/utilities/error-handling.md — Effect Result types, correlation IDs
- ../software-clean-code-standard/utilities/resilience-utilities.md — p-retry v6, circuit breaker for API calls
- ../software-clean-code-standard/utilities/logging-utilities.md — pino v9 + OpenTelemetry integration
- ../software-clean-code-standard/utilities/observability-utilities.md — OpenTelemetry SDK, tracing, metrics
- ../software-clean-code-standard/utilities/testing-utilities.md — Test factories, fixtures, mocks
- ../software-clean-code-standard/resources/clean-code-standard.md — Canonical clean code rules (
CC-*) for citation
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
../qa-observability/- OpenTelemetry, metrics, distributed tracing../software-security-appsec/- OWASP Top 10, input validation, secure tool design../ops-devops-platform/- CI/CD pipelines, deployment strategies, infrastructure
Supporting Patterns
../dev-api-design/- REST/GraphQL design for agent APIs and tool interfaces../ai-mlops/- Model deployment, monitoring, drift detection../qa-debugging/- Agent debugging, error analysis, root cause investigation
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.jsonfor 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.mdor 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.
Du fichier au premier essai
Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.
Consulter la source et ses fichiers annexesCe téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.
1. Télécharger le fichier
Télécharger SKILL.mdDepuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.
Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.
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. Vérifier les prérequis
Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.
Extrait original : 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 |
Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.
3. Charger la skill
Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.
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 doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.
Installation officielle d’OpenSkillsopenskills install './.skill-downloads/ai-agents-production-patterns-msba3nft'openskills read 'ai-agents-production-patterns-msba3nft'La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.
Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.
openskills syncMode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.
4. Faire un premier essai
Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :
Lis .skill-downloads/ai-agents-production-patterns-msba3nft/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.
Créer des cartes interactives avec kepler.gl
Data & IA
Création de cartes interactives et export HTML autonome avec le package Python keplergl, à partir de données géospatiales (DataFrame, GeoJSON, CSV).
Optimisation de paramètres par agent
Data & IA
Guide d'optimisation de systèmes configurables avec objectif mesurable, via des essais bornés et une recommandation fondée sur des preuves.
Relance des visiteurs ICP
Data & IA
Identifiez les utilisateurs inscrits correspondant au profil client idéal mais qui n'ont pas activé, et rédigez des messages de relance personnalisés pour les réengager.