capture-api-response-test-fixture

Capture API response test fixture.

2.02x

Quality

—

Does it follow best practices?

Impact

99%

2.02x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and highly actionable, with executable code and concrete paths for both capture workflows. Its only gap is implicit rather than explicit validation checkpoints in the fixture-capture sequence.

Suggestions

Add an explicit verification step after capturing a fixture, e.g. confirm it parses with the test helper before committing it under __fixtures__.

Briefly note how to validate that trimmed large responses still preserve parsing semantics.

Dimension	Reasoning	Score
Conciseness	The body is lean: one orienting sentence on fixture storage plus two complete, purposeful code blocks, with no padding explaining what a test fixture is or how libraries work, matching the level-3 anchor where every token earns its place.	3 / 3
Actionability	It provides fully executable TypeScript examples for both generateText and streamText, with specific paths, the run command 'pnpm tsx src/stream-text/script-name.ts', and the output folder, making it copy-paste ready as in the level-3 anchor.	3 / 3
Workflow Clarity	The two sub-workflows are clearly sequenced and separated by headers, but checkpoints are only implicit (e.g. no 'verify the fixture parses before using it'), fitting the level-2 anchor of steps present with implicit validation.	2 / 3
Progressive Disclosure	This is a sub-50-line single-purpose skill with no bundle files and clear section organization, which the rubric notes can score 3 on progressive disclosure with well-organized sections alone.	3 / 3
	Total	11 / 12 Passed

Description

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a terse single-action label that names its niche but omits any 'when to use' trigger guidance and provides only one concrete action. It is distinguishable but sparse on both completeness and trigger-term coverage.

Suggestions

Expand to multiple concrete actions, e.g. 'Capture, trim, and store API response test fixtures for provider response parsing tests.'

Add an explicit trigger clause such as 'Use when writing or updating provider response parsing tests and you need realistic fixture data.'

Include natural trigger variations users would say (e.g. 'test fixtures', 'response parsing tests', 'provider response samples').

Dimension	Reasoning	Score
Specificity	The phrase 'Capture API response test fixture' names a concrete action ('Capture') and a domain ('API response test fixture'), but only one action rather than a comprehensive list, matching the level-2 anchor.	2 / 3
Completeness	It gives only a thin 'what' ('Capture API response test fixture') and entirely lacks any 'when' / 'Use when...' trigger guidance; the missing trigger clause leaves it at the level-1 anchor where one of what/when is absent.	1 / 3
Trigger Term Quality	It includes relevant technical keywords ('API response', 'test fixture') but is sparse and leans on jargon, missing common natural variations a user would say, so it fits the level-2 anchor rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The description targets a specific niche (provider test fixtures) and is unlikely to broadly conflict, but its terseness means it could still overlap with general testing skills, matching the level-2 anchor.	2 / 3
	Total	7 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: vercel/ai
Commit: 184dc39

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.