skills.rest
liuyu520
liuyu520COMMUNITY
Explore all skills by this author →
GitHub

api-request-pipeline-reuse

Centralize API request construction with retries, filtering, and Codex adapter support.

Updated Aug 23, 2026
Search Tags:#api#codex#pipeline#error-handling#anthropic#retry#protocol-adapter
One-click install
npx skills add https://github.com/liuyu520/cc_source --skill api-request-pipeline-reuse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-request-pipeline-reuse
Source: https://github.com/liuyu520/cc_source/tree/main/.claude/skills/api-request-pipeline-reuse
Command: npx skills add https://github.com/liuyu520/cc_source --skill api-request-pipeline-reuse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill codifies and protects the flow of API requests from parameter construction to transport, ensuring consistent retries, error handling, and compatibility with protocol adapters.

Core Features & Use Cases

  • Centralized paramsFromContext construction that runs on every retry
  • CapabilityFilter that strips unsupported parameters per provider capabilities
  • withRetry pipeline that handles auth refresh, rate limits, overloads, and protocol adapter errors
  • Codex adapter path support that translates to OpenAI-style interfaces while preserving the pipeline

Quick Start

Run the development environment to exercise the unified API request pipeline end-to-end.

Frequently Asked Questions about api-request-pipeline-reuse

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

FAQPage Schema
How do I handle API request retries and error handling across multiple providers?▼

API request retries across multiple providers are handled by a centralized pipeline that reconstructs parameters on every retry, filters unsupported capabilities, and manages auth refresh alongside rate limits.

What is the best way to standardize API requests when using Codex protocol adapters?▼

Standardizing API requests with Codex protocol adapters involves routing through a dedicated adapter path that translates to OpenAI-style interfaces while preserving the unified retry, filtering, and error-handling pipeline.

How does a CapabilityFilter work for API requests targeting different backends?▼

A CapabilityFilter works for API requests by stripping unsupported parameters per provider capabilities before transport, ensuring the request payload matches backend constraints and preventing protocol errors during transmission.

Do I need a paramsFromContext pipeline to ensure consistent API request construction?▼

A paramsFromContext pipeline is required to ensure consistent API request construction, as it centralizes parameter assembly and runs on every retry attempt to maintain a uniform, testable request flow.

Why does my API request fail when switching between providers with different parameter schemas?▼

API requests fail when switching providers due to unsupported parameter schemas, but a centralized pipeline with CapabilityFilter resolves this by dynamically stripping incompatible parameters based on each provider's capabilities.

Related Skills

Explore More Software Engineering Skills→
DevMHOneDevMHOne

omni-proxies

Configure HTTP/HTTPS/SOCKS proxies with per-provider or global rules.

Community
Intermediate
HmbownHmbown

time-bomb

Schedule payloads to execute at a future time or condition.

Community
Intermediate
dr-codedr-code

datadog-automation

Automate Datadog metrics, logs, monitors, dashboards, events, and downtimes.

Community
Intermediate
serverpodserverpod
8

riverpod-retry

Configure Riverpod provider retry logic with global and per-provider settings.

Official
Intermediate