gateway-api

Route API design and implementation tasks to specialized library skills.

11|2|Updated Apr 7, 2026

Search Tags:#design #api #routing #orchestration #governance #gateway #intents

Ready to run

npx skills add https://github.com/porcupine-md/jonggrang --skill gateway-api-porcupine-md

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gateway-api
Source: https://github.com/porcupine-md/jonggrang/tree/main/skills/core/gateway-api
Command: npx skills add https://github.com/porcupine-md/jonggrang --skill gateway-api-porcupine-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route API design/implementation tasks to the right library skill to ensure consistent execution and governance across the pipeline.

Core Features & Use Cases

Intent-based routing: automatically map API design and implementation intents to the correct specialized library skill.
Extensible mappings: accommodate new API standards (REST, GraphQL) and lifecycle events (versioning, deprecation, webhooks).
Use case: coordinate large teams by delegating route-specific tasks to the most capable library, reducing handoffs and errors.

Quick Start

Define routing rules that send API design/implementation tasks to the appropriate library skill.

Frequently Asked Questions about gateway-api

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

FAQPage Schema

How does intent-based API routing work for design tasks?▼

Intent-based API routing automatically maps design and implementation intents to specialized library skills by evaluating routing rules and returning a structured gateway routing decision for consistent execution.

When do I need a gateway to route API tasks to libraries?▼

You need a gateway to route API tasks when coordinating large teams and managing multiple API standards like REST and GraphQL, ensuring tasks delegate to the most capable library to reduce handoffs and errors.

How do I route webhook and versioning tasks to the correct skill?▼

You route webhook and versioning tasks by defining extensible intent-to-skill mappings within the gateway configuration, which directs lifecycle events to the appropriate specialized library skill.

Can I use this gateway for GraphQL and REST API orchestration?▼

Yes, the gateway supports API orchestration for both GraphQL and REST standards by applying intent-to-skill mappings that route specific design and implementation tasks to specialized libraries.

What are the limitations of using a gateway skill for API governance?▼

The gateway skill limits API governance to routing decisions and intent mappings, requiring specialized library skills to execute the actual REST, GraphQL, versioning, or webhook implementation tasks.

Do I need specific frontmatter fields to route API tasks?▼

Yes, the gateway requires specific frontmatter fields to process routing rules and generate the output structure needed to map API design intents to the correct library skill.