api-integration

Build REST and GraphQL API clients with centralized error handling, authentication, and retries.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/dseirz-rgb/worker --skill api-integration-dseirz-rgb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-integration
Source: https://github.com/dseirz-rgb/worker/tree/main/.kiro/skills/api-integration
Command: npx skills add https://github.com/dseirz-rgb/worker --skill api-integration-dseirz-rgb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of reliably integrating third-party REST and GraphQL APIs with robust error handling and deterministic retry behavior across services.

Core Features & Use Cases

  • Defensive API client design: centralized error normalization, authentication handling, and retry policies.
  • Supports REST and GraphQL integration workflows with guidance on library choices (e.g., ky, axios, graphql-request) and type generation.
  • Use Case: Build a reusable API client layer that communicates with a public API, gracefully handles 429 rate limits, and degrades gracefully during network issues.

Quick Start

Start by creating a basic REST client with a base URL and authorization header, then wrap calls with a unified error handler and a retry mechanism. Extend to GraphQL by adding a GraphQL client and optional type generation as needed.

Frequently Asked Questions about api-integration

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

FAQPage Schema
How do I handle 429 rate limits and network errors during REST API integration?

To handle 429 rate limits during REST API integration, you can build a defensive API client with centralized error normalization and configurable retry strategies that gracefully degrade during network issues.

What is the best way to normalize errors across REST and GraphQL services?

The best way to normalize errors across REST and GraphQL services is to implement a centralized error handling layer within your API client architecture, ensuring unified error management and resilience.

How do I build a type-safe API client in TypeScript with deterministic retries?

You build a type-safe API client in TypeScript by creating a base client with authorization, wrapping calls with unified error handling, and applying deterministic retry policies using established libraries.

Does this API integration approach work with both axios and graphql-request?

Yes, this API integration approach works with both axios and graphql-request, providing guidance on library choices and optional type generation for building robust REST and GraphQL clients.

Can I use a single API client design for frontend and backend applications?

Yes, you can use a single API client design for frontend and backend applications, as this approach applies to architecture tasks involving type-safe client design and resilience across both environments.