request-translation-sanitization

Translate and sanitize API request parameters across Anthropic, Codex, and OpenAI endpoints.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/liuyu520/cc_source --skill request-translation-sanitization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-translation-sanitization
Source: https://github.com/liuyu520/cc_source/tree/main/.claude/skills/request-translation-sanitization
Command: npx skills add https://github.com/liuyu520/cc_source --skill request-translation-sanitization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates and sanitizes request parameters when moving between Anthropic and Codex/OpenAI-compatible APIs to reduce errors and ensure endpoint compatibility.

Core Features & Use Cases

  • Policy-preserving translation: Reuse existing translator logic to preserve policy while adapting parameter shapes.
  • Default-value governance: Omit default values unless explicitly gated, preventing accidental surface area expansion.
  • Endpoint compatibility: Aligns with Codex/OpenAI endpoints and third-party APIs by mapping fields to supported names and formats.

Quick Start

Run the translator to sanitize a sample Anthropic request before sending it to a Codex-compatible endpoint.

Frequently Asked Questions about request-translation-sanitization

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

FAQPage Schema
How do I translate API requests between Anthropic and OpenAI compatible endpoints?

API request translation between Anthropic and OpenAI compatible endpoints adapts parameter shapes and maps unsupported fields to supported formats. This sanitization process ensures compatibility when moving requests across third-party APIs while preserving safety rules.

What is API request sanitization for endpoint compatibility?

API request sanitization is the process of aligning request parameters before sending them to Codex or OpenAI endpoints. It handles default values and thinking-related fields, omitting unsupported parameters to enforce strict endpoint compatibility.

Why are default values omitted during API request translation?

Default values are omitted during API request translation to prevent accidental surface area expansion. Unless explicitly gated, removing these values ensures the translated request contains only necessary parameters, maintaining endpoint compatibility.

Does request sanitization preserve safety rules when translating to Codex endpoints?

Request sanitization preserves safety rules when translating to Codex endpoints. It reuses existing translator logic to maintain policy constraints while adapting parameter shapes and handling endpoint-specific unsupported parameters.

How do I handle unsupported parameters in Anthropic API requests?

Handling unsupported parameters in Anthropic API requests involves mapping them to supported names and formats or omitting them entirely. The sanitization process enforces omission for unsupported fields to ensure third-party endpoint compatibility.