Enterprise Integration Patterns
Use when the user asks about enterprise integration patterns, ESB vs iPaaS, integrating legacy or ERP systems, message routing and transformation, anti-corruption layer or dead letter queues. Produces an integration design with contracts, SLAs and error handling. Not for app-level messaging (use backend-message-queue) or webhooks (use backend-webhooks).
Install
npx skills add j4flmao/agent-skills --skill enterprise-integration-patternsgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/enterprise/integration-patterns ~/.claude/skills/enterprise-integration-patternsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Integration Patterns Agent ## Purpose Designs enterprise integration systems with message routing, protocol transformation, and error handling. ## Framework/Methodology ### INTEGRATE Framework A six-phase methodology for enterprise integration: Phase 1 - Identify: Map all systems requiring integration. Define system-of-record per data domain. Document protocols, data formats, and latency requirements. Identify integration touchpoints and data flows. Phase 2 - Negotiate: Define contracts between systems (API specs, message schemas, SLA terms). Establish consumer-driven contracts. Agree on error handling and retry policies. Phase 3 - Transform: Build anti-corruption layers between bounded contexts. Implement protocol and data format transformations. Enforce schema validation at boundaries. Phase 4 - Route: Design message routing topology. Select integration style (API/messaging/streaming/file). Configure content-based, header-based, or topic-based routing. Phase 5 - Govern: Monitor SLAs per integration flow. Track DLQ depth and error rates. Implement end-to-end tracing. Manage schema evolution with compatibility checks. Phase 6 - Retire: Decommission deprecated integration points. Migrate consumers to new endpoints. Archive integration documentation. ### Enterprise Integration Patterns (EIP) Catalog Messaging Patterns: - Point-to-Point Channel: One-to-one message delivery - Publish-Subscribe Channel: One-to-many message delivery
Details
- Skill name
enterprise-integration-patterns- Repository
- j4flmao/agent-skills
- Path
skills/enterprise/integration-patterns/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Enterprise Integration Patterns skill do?
Use when the user asks about enterprise integration patterns, ESB vs iPaaS, integrating legacy or ERP systems, message routing and transformation, anti-corruption layer or dead letter queues. Produces an integration design with contracts, SLAs and error handling. Not for app-level messaging (use backend-message-queue) or webhooks (use backend-webhooks).
How do I install the Enterprise Integration Patterns skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill enterprise-integration-patterns. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Enterprise Integration Patterns popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Enterprise Legacy Migration
45j4flmao/agent-skills
Use when the user asks to migrate a legacy monolith, apply the strangler fig pattern, plan a parallel run or big bang cutover, replace a mainframe, or keep dual writes in sync. Produces a migration strategy with anti-corruption layer, verification and rollback. Not for moving servers to the cloud (use cloud-migration) or refactoring code (use dev-loop-refactor-guide).
Enterprise Identity Provider
45j4flmao/agent-skills
Use when the user asks about SSO, SAML, OIDC federation, choosing an IdP (Okta, Entra ID, Keycloak), SCIM directory sync, MFA enforcement or access reviews. Produces IdP selection, federation and provisioning design. Not for in-app login code (use backend-auth-patterns) or permission models (use backend-authorization).
Enterprise Togaf Zachman
45j4flmao/agent-skills
Use when the user asks about TOGAF, the ADM phases, Zachman Framework, enterprise architecture frameworks, architecture building blocks or stakeholder viewpoints. Produces ADM phase plans, Zachman cell mapping and EA deliverables. Not for review boards and decision rights (use enterprise-architecture-governance) or solution design (use create-tech-spec).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.