npx skills add vercel/ai --skill capture-api-response-test-fixture
muxinc/ai · Archived
capture-api-response-test-fixture
Capture API response test fixture.
Installation
npx skills add muxinc/ai --skill capture-api-response-test-fixture
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
Capture conversations and decisions into structured Notion pages; use when turning chats/notes …
2.8K installscapture-api-response-test-fixture — an installable skill for AI agents, published by vercel/ai.
1.6K installsGuides exploration of $autocapture events captured by posthog-js to understand user interaction…
310 installsSave the current conversation as a permanent, structured wiki note. Use this skill when the use…
2.7K installsSimilar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsPre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsRetrieve and review responses from a Google Form.
27.1K installsGoogle Model Armor: Sanitize a model response through a Model Armor template.
26.5K installsMore details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
npx skills add smithery/vercel --skill capture-api-response-test-fixture
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,022 B -
docs
SUMMARY.md75 B
History
- First seen on skills.sh
- First recorded snapshot · 1 installs
SKILL.md
API Response Test Fixtures
For provider response parsing tests, we aim at storing test fixtures with the true responses from the providers (unless they are too large in which case some cutting that does not change semantics is advised).
The fixtures are stored in a fixtures subfolder, e.g. packages/openai/src/responses/fixtures. See the file names in packages/openai/src/responses/fixtures for naming conventions and packages/openai/src/responses/openai-responses-language-model.test.ts for how to set up test helpers.
You can use our examples under /examples/ai-functions to generate test fixtures.
generateText (doGenerate testing)
For generateText, log the raw response output to the console and copy it into a new test fixture.
import { openai } from "@ai-sdk/openai";
import { generateText } from "ai";
import { run } from "../lib/run";
run(async () => {
const result = await generateText({
model: openai("gpt-5-nano"),
prompt: "Invent a new holiday and describe its traditions.",
});
console.warn(JSON.stringify(result.response.body, null, 2));
});
streamText (doStream testing)
For streamText, you need to set includeRawChunks to true and use the special saveRawChunks helper. Run the script from the /example/ai-functions folder via pnpm tsx src/stream-text/script-name.ts. The result is then stored in the /examples/ai-functions/output folder. You can copy it to your fixtures folder and rename it.
import { openai } from "@ai-sdk/openai";
import { streamText } from "ai";
import { run } from "../lib/run";
import { saveRawChunks } from "../lib/save-raw-chunks";
run(async () => {
const result = streamText({
model: openai("gpt-5-nano"),
prompt: "Invent a new holiday and describe its traditions.",
includeRawChunks: true,
});
await saveRawChunks({ result, filename: "openai-gpt-5-nano" });
});