Fixtures are organized in __fixtures__ subfolders within provider packages, using naming conventions documented in existing examples
Supports two testing patterns: generateText (log raw response to console and copy into fixture) and streamText (use includeRawChunks and saveRawChunks helper to capture streaming chunks)
Recommends storing true provider responses unless size constraints require semantic-preserv
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncapture-api-response-test-fixtureExecute the skills CLI command in your project's root directory to begin installation:
Fetches capture-api-response-test-fixture from vercel/ai and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate capture-api-response-test-fixture. Access via /capture-api-response-test-fixture in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
23.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.3K
stars
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.
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.log(JSON.stringify(result.response.body, null, 2));
});
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' });
});
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
cexll/myclaude
github/awesome-copilot
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
kostja94/marketing-skills
Keeps context tight: capture-api-response-test-fixture is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: capture-api-response-test-fixture is the kind of skill you can hand to a new teammate without a long onboarding doc.
capture-api-response-test-fixture has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: capture-api-response-test-fixture is focused, and the summary matches what you get after install.
capture-api-response-test-fixture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
capture-api-response-test-fixture has been reliable in day-to-day use. Documentation quality is above average for community skills.
capture-api-response-test-fixture has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: capture-api-response-test-fixture is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: capture-api-response-test-fixture is focused, and the summary matches what you get after install.
capture-api-response-test-fixture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 54