capture-api-response-test-fixture

Capture API response test fixture.

0.55x

Quality

67%

Does it follow best practices?

Impact

50%

0.55x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/capture-api-response-test-fixture/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

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

The content is a lean, well-structured guide with executable examples for capturing both generateText and streamText fixtures. Its main weakness is prose-described workflows that could be numbered with a verification step.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, with complete code and no padding about concepts; only the opening fixture-storage sentence is slightly verbose and could be trimmed, placing it just below a 5.	4 / 5
Actionability	It provides two complete, copy-paste-ready code examples with concrete file paths, helper imports, and an explicit run command ('pnpm tsx src/stream-text/<provider>/<script>.ts'), covering the common generateText and streamText cases.	5 / 5
Workflow Clarity	Each section gives a clear sequence (place script, run, capture output, copy/rename into the fixtures folder), but steps are prose rather than numbered and lack explicit verification checkpoints; this is not a destructive/batch operation, so the 3-cap does not apply.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files and no need for external references, and content is organized under clear headers ('generateText', 'streamText'), meeting the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

48%Weight 40%Scale 1-5

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 label that identifies a clear niche but lacks trigger guidance and concrete capability detail. It answers 'what' weakly and omits 'when' entirely.

Suggestions

Expand the description to list concrete actions, e.g. 'Capture, store, and regenerate provider API response test fixtures for response-parsing tests.'

Add an explicit trigger clause such as 'Use when adding or updating provider response test fixtures for parsing tests.'

Include natural synonyms users might say (e.g. 'test fixtures', 'recorded API responses', 'response snapshots') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Capture API response test fixture' names the domain and a single minimal action, reading more like a label than a description of capabilities; it is below the 3 anchor which expects 1-2 concrete, comprehensive actions.	2 / 5
Completeness	It states a clear 'what' (capture API response test fixtures) but has no 'Use when...' trigger clause, so per the guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	It contains relevant keywords ('API response', 'test fixture') a developer might say, but offers no synonyms or common variations, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The niche of provider API response test fixtures is fairly distinct with only minor overlap risk against general testing skills, matching the 'mostly distinct; minor overlap' anchor; it is not a 5 because no explicit triggers sharpen the niche.	4 / 5
	Total	12 / 20 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
Path: skills/capture-api-response-test-fixture/SKILL.md
Commit: c3c189c

Reviewed: ~3 hours 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.