Skip to content
TrustedSkillsbeta
Back to all skills

Api Gateway Patterns

Listed
manutej·vlatest·backend

Helps with API, patterns as part of agent workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add manutej/luxor-claude-marketplace --skill api-gateway-patterns -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

manutej

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: httpbin.org.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    users-service.default.svc.cluster.locallocalapi.internallocallegacy.internallocalfragile-api.internallocalapi-dev.internallocalapi-staging.internallocalgraphql-api.internallocalusers-api.default.svc.cluster.locallocalorders-api.default.svc.cluster.locallocalproducts-api.default.svc.cluster.locallocalpayments-api.default.svc.cluster.locallocalnotifications-api.default.svc.cluster.locallocalzipkin.observability.svc.cluster.locallocallogstash.observability.svc.cluster.locallocalistio-ingressgateway.istio-system.svc.cluster.locallocalhttpbin.orgundeclaredusers.internallocalorders.internallocalinventory.internallocal

    What it found

    • plugins/luxor-devops-suite/skills/api-gateway-patterns/README.md:155contacts httpbin.org
      url: http://httpbin.org
    • plugins/luxor-devops-suite/skills/api-gateway-patterns/README.md:169contacts httpbin.org
      --data url=http://httpbin.org

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned manutej/luxor-claude-marketplace at 1861cc9720.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1861cc9720
Manifest
plugins/luxor-devops-suite/skills/api-gateway-patterns/SKILL.md
Scanned
3 files, 5,376 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to interact with backend services through standardized API gateway configurations. It streamlines communication between the agent and various microservices, ensuring consistent routing, authentication, and rate limiting across different endpoints.

When to use it

  • Integrating an AI agent into a complex microservices architecture requiring centralized traffic management.
  • Implementing uniform security policies and access controls for multiple backend APIs accessed by the agent.
  • Managing high-volume requests from an autonomous agent to prevent overwhelming individual service instances.

Key capabilities

  • Centralized routing of API requests to specific backend services.
  • Enforced authentication and authorization mechanisms at the gateway level.
  • Rate limiting and throttling controls to protect downstream services.
  • Standardized response formatting and error handling for consistent agent interactions.

Example prompts

  • "Configure the API gateway to route all user profile requests to the identity service while applying strict rate limits."
  • "Set up authentication rules so the AI agent can only access public endpoints without a token."
  • "Create a gateway rule that redirects legacy API calls to the new version of the payment service."

Tips & gotchas

Ensure your backend services are properly documented and accessible via the gateway before configuring routing rules. Be mindful of latency introduced by the gateway layer when designing real-time agent workflows.