batch-sync-fixtures

Capture real sync-API and provider batch responses into committed JSONL test fixtures.

7|12|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/OpenRouterTeam/docs --skill batch-sync-fixtures-openrouterteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: batch-sync-fixtures
Source: https://github.com/OpenRouterTeam/docs/tree/main/.agents/skills/batch-sync-fixtures
Command: npx skills add https://github.com/OpenRouterTeam/docs --skill batch-sync-fixtures-openrouterteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Batch API tests are only as honest as their fixtures, and hand-written or fake-provider fixtures drift from real provider behavior. This Skill captures real sync-API responses and provider batch output, redacts them safely, and turns them into committed JSONL fixtures with provenance for parity tests. ## Core Features & Use Cases - Real-API capture: Record sync responses from OpenRouter chat completions and provider-native APIs (Anthropic Messages, Gemini generateContent) plus real provider batch output lines, including error lines. - Deterministic redaction with provenance: Rewrite identifiers to stable placeholders, reject secret-like values, Zod-validate redacted output, and emit a provenance manifest per fixture. - Loader and parity-test wiring: Expose fixtures through a Zod-validated loader with shape-guard tests, then assert batch output against captured sync golden vectors field-by-field. - Use Case: When onboarding a new batch provider like Anthropic, capture matched sync/batch pairs for text, tool, and truncated scenarios, redact them, and commit fixtures that the skin's parity tests compare against. ## Quick Start Capture a real sync response and provider batch output for the target provider, then run the capture template to redact and commit the JSONL fixtures with a provenance manifest.

Frequently Asked Questions about batch-sync-fixtures

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

FAQPage Schema
How do I create batch API test fixtures from real provider responses?▼

Submit a small batch to the provider's real batch API, download the output file, and capture the matching sync response. Then run the capture template to redact identifiers, validate against the provider Zod schema, and commit the JSONL with a provenance manifest.

How do I capture Anthropic or Gemini sync responses for parity tests?▼

Call the provider-native API directly, such as Anthropic Messages with an x-api-key header or Gemini generateContent with an API key, using a tiny deterministic prompt. Save the JSON response verbatim as the golden vector the parity test compares batch output against.

Why should batch fixtures not come from a fake provider?▼

The fake provider is built from real captures, so using its output as a fixture is circular and hides drift from actual provider behavior. Fixtures must come from real provider batch runs, including error lines triggered against the live API.

How are secrets and identifiers handled in committed fixtures?▼

The capture template deterministically rewrites org, user, file, and job IDs to stable placeholders and fails loudly if any line matches secret patterns like sk-, Bearer, or long base64 runs. Real customer content is replaced with tiny deterministic prompts before committing.

What scenarios should a batch fixture matrix cover?▼

Capture matched pairs for plain text, tool calls, truncated max_tokens responses, and reasoning or structured-output variants where the provider supports them, plus at least one error line. Use the same deterministic prompt across each pair so parity tests compare like for like.