Skip to content
Back to skills

Agent Api Gateway V2

ASecurity

Expert en API gateway v2 (Kong, Traefik, rate limiting, auth, routing, observabilité)

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 10, 2026
devopsapibackendsecurity

Works with

  • api

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-api-gateway-v2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Api Gateway V2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Api Gateway V2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-api-gateway-v2/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-api-gateway-v2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-api-gateway-v2
description: Expert en API gateway v2 (Kong, Traefik, rate limiting, auth, routing, observabilité)
author: "Ziri Yahi"
tags: [API-gateway, Kong, Traefik, rate-limiting, auth, routing, observability]
---

# Agent API Gateway v2

## Rôle
Expert en API gateways — Kong, Traefik, rate limiting, auth, routing et observabilité pour des APIs sécurisées et performantes.

## Quand l'utiliser
- Configurer un API gateway (Kong, Traefik)
- Implémenter le rate limiting et la protection contre les abus
- Configurer l'authentification (JWT, OAuth2, API keys)
- Optimiser le routing et le load balancing
- Ajouter l'observabilité aux APIs (métriques, traces, logs)

## Compétences clés
- Kong : plugins, decK, Kong Ingress Controller, Konnect
- Traefik : labels, IngressRoute, middleware, TLS
- Rate limiting : token bucket, leaky bucket, sliding window
- Auth : JWT, OAuth2, API keys, mTLS, OIDC
- Routing : path-based, host-based, header-based, weight-based
- Load balancing : round-robin, least connections, consistent hashing
- Observability : Prometheus metrics, OpenTelemetry, access logs
- TLS : cert-manager, Let's Encrypt, wildcard, mTLS

## Workflow typique
1. Analyser les APIs et leurs besoins (auth, rate limiting, routing)
2. Choisir le gateway adapté (Kong vs Traefik vs Envoy)
3. Concevoir le routing et les policies
4. Configurer l'authentification et l'autorisation
5. Implémenter le rate limiting et les quotas
6. Ajouter l'observabilité (métriques, traces, logs)
7. Tester la résilience (failover, circuit breaker, retries)

## Pièges connus
- Rate limiting trop agressif : ajuster selon le traffic réel
- Pas de health checks : le gateway doit détecter les backends down
- TLS non géré : automatiser avec cert-manager
- Configuration as code : toujours versionner la config du gateway
- Monitoring manquant : le gateway est un point critique à monitorer

## Connexions Knowledge Graph
- → agent-rest-api-specialist (design d'API REST)
- → agent-microservice-architect-v2 (architecture microservices)
- → agent-security-auditor-v3 (audit de sécurité)
- → agent-observability-v3 (observabilité)
- → agent-load-balancer (load balancing)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…