aigw-contrib-extproc-internals

Translate and route AI requests through Envoy ExtProc with EndpointSpec routing.

3|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/missBerg/envoy-skills --skill aigw-contrib-extproc-internals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aigw-contrib-extproc-internals
Source: https://github.com/missBerg/envoy-skills/tree/main/ai-gateway/contributors/skills/aigw-contrib-extproc-internals
Command: npx skills add https://github.com/missBerg/envoy-skills --skill aigw-contrib-extproc-internals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the complexity of ExtProc internals by documenting how to implement request lifecycle management, translator patterns, and EndpointSpec routing within an Envoy-powered AI gateway.

Core Features & Use Cases

  • Provides a clear translator matrix to map between client and backend schemas (e.g., OpenAI to custom backends).
  • Defines EndpointSpec-driven routing and authentication hooks to support multi-backend deployments.
  • Covers streaming Server-Sent Events (SSE) handling and error-resilient processing for long-lived AI responses.

Quick Start

Study the ExtProc internals guide to implement request translation, streaming SSE handling, and backend authentication in your Envoy-powered AI gateway.

Frequently Asked Questions about aigw-contrib-extproc-internals

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

FAQPage Schema
How do I handle streaming SSE responses in Envoy ExtProc?

Handle streaming SSE in Envoy ExtProc by implementing SSE processing logic within your translator to parse, buffer, and forward long-lived AI response chunks with error-resilient handling and traceability.

What is the best way to route AI requests to multiple backends using Envoy gateway?

Route AI requests to multiple backends by defining EndpointSpec-driven routing structures that map target endpoints and apply backend authentication hooks for each specific upstream service.

How do I translate OpenAI client schemas to custom backend APIs in an AI gateway?

Translate OpenAI client schemas to custom backend APIs by implementing source-to-target translator interfaces that map request and response fields between the client and backend formats.

Why does my ExtProc request lifecycle management fail across diverse backends?

ExtProc request lifecycle management fails across diverse backends when missing robust error handling, insufficient EndpointSpec routing configuration, or incomplete translator interfaces disrupt end-to-end processing.

Do I need specific config structures to implement backend authentication in Envoy ExtProc?

You need defined config structures and authentication hooks within the ExtProc implementation to properly inject and manage backend authentication credentials across diverse upstream backends.

Can I map multiple translator pairs for different AI models in a single Envoy gateway?

Map multiple translator pairs in a single Envoy gateway by defining a translator matrix that applies source-to-target translation logic and EndpointSpec routing for each model pair.