api-gateway

Centralize authentication, rate limiting, caching, and request transformation for microservices API traffic.

1|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/CybLow/pypaginate --skill api-gateway-cyblow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-gateway
Source: https://github.com/CybLow/pypaginate/tree/main/.opencode/skills/api-gateway
Command: npx skills add https://github.com/CybLow/pypaginate --skill api-gateway-cyblow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API gateway patterns centralize cross-cutting concerns for microservices, including authentication, rate limiting, request transformation, caching, and BFF aggregation.

Core Features & Use Cases

  • Gateway Responsibilities: Authentication & Authorization, Rate Limiting, Request/Response Transformation, Load Balancing, Circuit Breaking, Caching, Logging & Monitoring, API Versioning.
  • Backend for Frontend (BFF): Aggregates data from multiple services for mobile/web clients.
  • Request Aggregation: Collects data from multiple services in a single request path.
  • HTTP Caching: Cache-Control headers, ETags, conditional requests, and cache strategies.
  • Quick Reference: Guidance on when to gateway vs direct access and common patterns.

Quick Start

Configure the gateway to route API requests to backend services, enable BFF aggregation, and apply caching headers.

Frequently Asked Questions about api-gateway

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

FAQPage Schema
How do I centralize API authentication and rate limiting for microservices?

Centralize API authentication and rate limiting by routing microservices traffic through an API gateway, applying consistent security policies across all incoming requests. This ensures uniform governance across all incoming requests.

What is a BFF pattern and when should I use it for API aggregation?

A Backend for Frontend (BFF) pattern aggregates data from multiple services into a single response for specific clients. Use BFF aggregation when mobile or web clients need consolidated data from diverse backend services.

How do I configure HTTP caching and ETags for API responses?

Configure HTTP caching and ETags by applying Cache-Control headers and conditional requests to API responses. This enables efficient client-side caching strategies and reduces unnecessary bandwidth consumption.

What is the best way to handle request transformation in a microservices gateway?

The best way to handle request transformation is implementing it within the API gateway layer. This allows consistent request and response modifications before routing traffic to backend services.

Do I need an API gateway for circuit breaking and load balancing?

You need an API gateway for circuit breaking and load balancing to centralize traffic management across microservices. This prevents cascading failures and distributes incoming requests effectively.

When should I use direct service access instead of routing through an API gateway?

Use direct service access instead of an API gateway for internal service-to-service communication where cross-cutting concerns like authentication or request transformation are already handled. Gateway routing suits external client traffic.