api-gateway-configurator

Configure API gateways for SDK traffic management

509 stars

Best use case

api-gateway-configurator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Configure API gateways for SDK traffic management

Teams using api-gateway-configurator should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/api-gateway-configurator/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/sdk-platform-development/skills/api-gateway-configurator/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/api-gateway-configurator/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How api-gateway-configurator Compares

Feature / Agentapi-gateway-configuratorStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Configure API gateways for SDK traffic management

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# API Gateway Configurator Skill

## Overview

This skill configures API gateways to manage SDK traffic including routing, authentication, rate limiting, and circuit breakers for reliable API delivery.

## Capabilities

- Configure request routing and load balancing
- Implement rate limiting and throttling
- Set up authentication and authorization
- Configure circuit breakers for resilience
- Implement request/response transformation
- Set up API versioning routes
- Configure caching policies
- Implement CORS and security headers

## Target Processes

- Platform API Gateway Design
- API Versioning Strategy
- Authentication and Authorization Patterns

## Integration Points

- Kong Gateway
- AWS API Gateway
- Apigee
- Azure API Management
- Envoy/Istio

## Input Requirements

- Routing requirements
- Rate limiting policies
- Authentication methods
- Transformation needs
- Resilience requirements

## Output Artifacts

- Gateway configuration files
- Route definitions
- Rate limit policies
- Authentication plugins
- Circuit breaker configs
- Transformation rules

## Usage Example

```yaml
skill:
  name: api-gateway-configurator
  context:
    gateway: kong
    routes:
      - path: /v1/*
        upstream: api-v1
        plugins:
          - rate-limiting
          - jwt-auth
      - path: /v2/*
        upstream: api-v2
        plugins:
          - rate-limiting
          - oauth2
    rateLimiting:
      default: 1000/hour
      authenticated: 10000/hour
    circuitBreaker:
      threshold: 5
      timeout: 30s
```

## Best Practices

1. Use declarative configurations
2. Implement proper rate limiting tiers
3. Configure circuit breakers for all upstreams
4. Version APIs through routing
5. Centralize authentication
6. Monitor gateway metrics