API Integration Specialist

Integrate REST and GraphQL APIs with OAuth, retries, and error handling.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/boomNDS/soop-discoard-bot --skill api-integration-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: API Integration Specialist
Source: https://github.com/boomNDS/soop-discoard-bot/tree/main/.agents/skills/api-integration-specialist
Command: npx skills add https://github.com/boomNDS/soop-discoard-bot --skill api-integration-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers implement API integrations with secure auth, reliable error handling, rate limiting, and resilient retries, reducing boilerplate and errors.

Core Features & Use Cases

  • Authentication & Security: Manage OAuth flows, API keys, and credential storage securely.
  • Resilience & Reliability: Implement retry/backoff, idempotent requests, and circuit breaker patterns for flaky APIs.
  • Integration Patterns: Provide reusable REST/GraphQL client templates, error normalization, and request/response transformations.
  • Use Case: When integrating a payment gateway or CRM, use this Skill to standardize authentication, error handling, and retry strategies across services.

Quick Start

To begin, create a client skeleton using standard templates and wire in OAuth or API key authentication for the target service, then implement retry logic and response transformation.

Frequently Asked Questions about API Integration Specialist

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

FAQPage Schema
How do I implement OAuth flows and API key management for third-party API integrations?

API integration authentication manages OAuth flows and API keys securely by standardizing credential storage and request signing. This reduces boilerplate and prevents security errors when connecting to third-party services.

What is the best way to handle API rate limiting and retry logic in production applications?

Handling API rate limiting and retry logic requires implementing resilient retry and backoff strategies alongside circuit breaker patterns. This ensures production-grade reliability for flaky APIs by normalizing errors and enforcing idempotent requests.

How do I normalize REST and GraphQL API errors and transform request responses?

Standardize REST and GraphQL API errors using reusable client templates that perform request and response transformations. This normalizes disparate error formats into a consistent structure, simplifying downstream application logic.

When do I need circuit breaker patterns and idempotent requests for API integrations?

Circuit breaker patterns and idempotent requests are needed when integrating flaky APIs that require production-grade resilience. They prevent cascading failures and ensure duplicate requests from retries do not create unintended side effects.

Does this API integration approach work for both payment gateway and CRM webhooks?

This API integration approach works for payment gateways, CRMs, and webhooks by standardizing authentication, error handling, and retry strategies across services. It provides reusable templates adaptable to both REST and GraphQL environments.