Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsAPI Integration Design & Error Handling Architect
Designs reliable API integrations with request validation, contract mapping, retries, timeout policies, idempotency, rate-limit protection, token refresh, dead-letter handling, monitoring, and recovery plans.
$55
API Integration Design & Error Handling Architect
Example session with this skill installed
Design an API integration between Shopify paid orders and our ERP.
Context
- Shopify is the source of truth for order creation and payment status.
- The ERP is used for fulfillment and accounting.
- We need to sync paid orders, customers, line items, shipping address, tax, currency, and payment status.
- We are worried about duplicate orders, webhook retries, missing SKU mappings, ERP timeouts, rate limits, and partial failures.
Please include
- integration architecture
- data contract
- field mapping approach
- request validation
- response validation
- retry and backoff policy
- idempotency strategy
- rate-limit protection
- dead-letter handling
- monitoring and alerting
- testing matrix
- runbook notes
- Read your context and instructions
- Compiled the api integration design
=== API INTEGRATION DESIGN & ERROR HANDLING BLUEPRINT ===
Business process
Sync paid Shopify orders into the ERP for fulfillment and accounting.
Systems integrated
- Source: Shopify
- Target: ERP
Source of truth
Shopify is the source of truth for order creation and payment status. The ERP is the source of truth for fulfillment and accounting processing after successful sync.
Integration architecture
- Shopify order-paid webhook.
- Webhook signature validation.
- Event ID capture.
- Payload validation.
- Order transformation.
- ERP customer lookup or create.
- ERP order create.
- Idempotency and state store.
- Dead-letter handling.
- Monitoring and reconciliation report.
Data contract
Required source fields
- Shopify order ID
- customer ID or customer email
- line items
- variant IDs or SKUs
- quantity
- price
- currency
- payment status
- shipping address
Required target fields
- ERP customer reference
- ERP order lines
- ERP item ID or SKU
- quantity
- price
- tax
- shipping method
- payment status
Request validation
Reject or route to review if
- Shopify order ID is missing
- payment status is not paid
- line items are empty
- SKU mapping is missing
- currency is unsupported
- shipping address is incomplete
- tax mapping cannot be determined
Response validation
Confirm that
- ERP customer reference is returned
- ERP order ID is returned
- order status is accepted or created
- line item count matches expected count
- no partial success warning is present
Idempotency strategy
Use Shopify order ID plus operation type as the idempotency key.
Duplicate behavior
If the ERP order already exists, do not create another order. Update sync status and append an audit note.
Retry policy
Retry timeouts, 429 responses, and selected 5xx responses with exponential backoff and jitter. Do not retry validation failures, missing SKU mappings, permission errors, or malformed requests.
Rate-limit protection
Queue order sync jobs and throttle ERP requests according to provider limits. Alert if queue depth grows or repeated rate-limit responses occur.
Dead-letter handling
Route failed orders to a review queue with:
- Shopify order ID
- correlation ID
- failed step
- error category
- safe error message
- retry count
- recommended action
- replay allowed flag
Monitoring
Track
- orders received
- orders synced
- orders failed
- duplicate orders prevented
- retry count
- ERP latency
- dead-letter count
- SKU mapping failures
- reconciliation mismatches
Testing matrix
- valid paid order
- missing SKU mapping
- unsupported currency
- duplicate webhook event
- ERP timeout before response
- ERP timeout after accepting request
- ERP validation error
- rate-limit response
- partial customer created but order failed
- replay from dead-letter
- reconciliation report detects unsynced paid order
Runbook notes
- integration owner must review dead-letter items daily during pilot
- failed SKU mappings should be assigned to operations or catalog owner
- replay is allowed only after idempotency key and ERP order status are checked
- production rollout should begin with a limited-volume pilot
Connects securely to your tools. The creator never sees your data.
About this skill
API Integration Design & Error Handling Architect helps developers, automation engineers, SaaS teams, integration agencies, technical consultants, and companies connecting many business systems design robust API integrations between CRMs, ERPs, Shopify, HubSpot, Stripe, Airtable, Slack, Notion, Google Sheets, internal tools, and other SaaS platforms.
Many enterprise automations depend on external APIs, but fragile integrations often fail because they do not properly handle malformed requests, missing fields, schema changes, authentication errors, expired tokens, permission failures, timeouts, incomplete responses, rate limits, webhook retries, duplicate requests, partial completion, and downstream system failures.
This skill creates defensive API integration architectures with request validation, response validation, field mapping, schema and contract mapping, authentication planning, token refresh logic, timeout policies, retry and exponential backoff strategies, rate-limit protection, idempotency keys, error classification, ambiguous response handling, dead-letter queues, webhook reliability patterns, monitoring, alerting, testing matrices, runbooks, and remediation tickets.
It is ideal for building integrations between CRMs, ERPs, ecommerce platforms, payment systems, support platforms, internal databases, workflow automation tools, communication platforms, productivity systems, and reporting tools.
The skill is designed to transform fragile API flows into reliable, observable, recoverable, enterprise-grade integrations that reduce operational risk, prevent data loss, avoid duplicate records, support safe retries, and make integration failures easier to diagnose and recover from.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Shopify.
This skill designs and audits API integrations, but it does not execute live API calls, modify production systems, verify vendor-specific behavior without documentation, guarantee uptime, replace security review, or replace compliance approval.
Real reliability depends on provider behavior, implementation quality, test coverage, infrastructure, rate limits, schema stability, authentication configuration, data quality, monitoring, ownership, and ongoing maintenance.
The skill may use placeholders when the user does not provide API documentation, payload samples, schema definitions, rate-limit details, authentication flow details, logs, or business-impact context. All recommendations should be validated against official provider documentation and tested in a sandbox or staging environment before production rollout.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 months ago
Permissions
File Scopes
This skill uses file access to read user-provided API documentation, OpenAPI/Swagger files, schema files, request and response samples, webhook payload examples, integration requirements, field mapping documents, workflow exports, sanitized logs, monitoring summaries, incident reports, and business process notes. It uses write access to create structured Markdown/text outputs such as API integration blueprints, error-handling plans, contract mapping documents, retry and rate-limit policies, webhook consumer designs, fragile-flow hardening reviews, integration testing matrices, remediation tickets, monitoring plans, runbooks, and SKILL.md files. Optional API documentation, OpenAPI/Swagger, workflow export, log, webhook sample, schema, mapping, monitoring, and incident report access should remain read-only unless a separately approved implementation workflow requires otherwise. The default safe setup does not require terminal access, unrestricted network access, environment-variable access, secret-value access, production write access, database write access, deployment access, credential management access, or payment operation access.