capture-api-response-test-fixture

Capture API response test fixture.

2.02x

Quality

70%

Does it follow best practices?

Impact

99%

2.02x

Average score across 3 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 body is a tight, actionable guide with two executable code examples and concrete file-path references for a simple fixture-capture task. Its main gap is the absence of verification steps, though the task is not destructive.

Dimension	Reasoning	Score
Conciseness	The body is efficient and project-specific rather than padded with generic knowledge, though phrasing like "unless they are too large in which case some cutting that does not change semantics is advised" could be trimmed; not quite lean enough for 5.	4 / 5
Actionability	Two complete, copy-paste-ready code examples with imports and exact run commands ("pnpm tsx src/stream-text/script-name.ts") cover the common generateText and streamText cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Each subsection gives a clear sequenced procedure with concrete commands and output locations, but there are no validation or verification checkpoints, which keeps it below 5.	4 / 5
Progressive Disclosure	The skill is under 50 lines, has no bundle files, and is well-organized into clear sections (overview plus generateText/streamText subsections), qualifying for the simple-skill exception at score 5.	5 / 5
	Total	18 / 20 Passed

Description

53%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 concise and names a specific niche but is bare-bones: a single action verb with no trigger guidance and few keyword variations. It answers "what" clearly while omitting "when" entirely.

Suggestions

Add a "Use when..." clause naming concrete trigger situations, e.g. writing or updating provider response parsing tests.

Expand the action list beyond "Capture" (e.g. capture, store, trim, and rename provider response fixtures) to improve specificity.

Include natural keyword variants such as "test fixtures", "response snapshots", or "__fixtures__" to strengthen trigger terms.

Dimension	Reasoning	Score
Specificity	"Capture API response test fixture." names a specific domain and one concrete action (capture), matching the anchor for 1-2 concrete actions without being comprehensive; it is too minimal for score 4 and too concrete for score 2.	3 / 5
Completeness	It clearly states the "what" (capture API response test fixture) but provides no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	The phrases "API response" and "test fixture" are relevant and somewhat natural, but common variations or synonyms are missing, fitting the score-3 anchor rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	"API response test fixture" denotes a clear niche mostly distinct from other skills with only minor overlap risk against general testing skills; it lacks the rich trigger phrasing needed for a 5.	4 / 5
	Total	13 / 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: 86892f3

Reviewed: about 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.