Agent skill · software engineering · jeremylongshore
building-api-gateway
Create API gateways with routing, load balancing, rate limiting, and
Why this skill is useful
Adds executable scripts for API gateway configuration, including routing, authentication, and rate limiting that aren't in public docs.
What it needs
Requires express-gateway, kong, krakend installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Building API Gateway Overview Create an API gateway that provides unified entry point routing, load balancing, authentication enforcement, rate limiting, request transformation, and response aggregation across multiple backend microservices. Support path-based and header-based routing, circuit breaker protection for downstream services, and centralized cross-cutting concern management. Prerequisites Multiple backend API services with known endpoints, health check URLs, and authentication requirements Gateway framework: Express Gateway, Kong (declarative config), KrakenD, or custom Node.js/Go implementation Service registry or static upstream configuration for backend service discovery TLS certificates for gateway termination and optional mTLS for backend communication Centralized logging and metrics collection for gateway-level observability Instructions 1. Inventory all backend services using Read and Grep, documenting their base URLs, endpoint paths, authentication requirements, and health check endpoints. 2. Define routing rules that map public-facing URL patterns to backend service endpoints: path-based (/users/ -> user-service), header-based (X-API-Version: 2 -> v2-service), or method-based routing. 3. Implement authentication at the gateway layer: validate JWT tokens, API keys, or OAuth2 tokens once at the gateway and forward authenticated user context to backend services via headers (X-User-ID, X-User-Roles). 4. Add rate limiting at the gateway level with per-consumer quotas, applying limits before requests reach backend services to protect all downstream services uniformly. 5. Configure request transformation: strip internal headers from incoming requests, add correlation IDs, rewrite URL paths for backend routing, and inject service-specific headers. 6. Implement response aggregation for composite endpoints that fan out to multiple backend services, merge responses, and return a unified payload to the client. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/building-api-gateway