capture-api-response-test-fixture
Capture API response test fixture.
Install with Tessl CLI
npx tessl i github:vercel/ai --skill capture-api-response-test-fixtureOverall
score
69%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too terse to effectively guide skill selection. While it identifies a specific domain (API test fixtures), it lacks concrete actions, explicit trigger conditions, and natural keyword variations that would help Claude confidently choose this skill over alternatives.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to save API responses for testing, create mock data, or record HTTP responses as fixtures'
Expand the action description to include specific capabilities like 'Records HTTP responses, saves JSON/XML payloads, generates mock data files for unit tests'
Include natural keyword variations users might say: 'mock', 'stub', 'snapshot testing', 'record API', 'save response'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain (API response test fixtures) and implies an action (capture), but lacks detail on what 'capture' entails or what formats/outputs are involved. | 2 / 3 |
Completeness | Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains relevant terms like 'API response', 'test fixture' that users might say, but missing common variations like 'mock data', 'stub', 'snapshot', 'record response', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'API response' and 'test fixture' provides some specificity, but could overlap with general testing skills, mocking skills, or API documentation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
88%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, focused skill that efficiently teaches how to capture API response test fixtures. The code examples are executable and the content respects token budget. The main weakness is the implicit workflow - steps could be more explicitly sequenced, especially for the streamText flow which involves multiple actions.
Suggestions
Add explicit numbered steps for the streamText workflow: 1) Create script, 2) Run from specific folder, 3) Copy output file, 4) Rename appropriately
Consider adding a brief validation step to verify the fixture was captured correctly before committing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, providing only necessary information about fixture storage, naming conventions, and code examples without explaining basic concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for both generateText and streamText scenarios with specific file paths and commands. | 3 / 3 |
Workflow Clarity | Steps are present but implicit; the streamText section mentions running via 'pnpm tsx' and copying output, but lacks explicit numbered steps or validation checkpoints for the overall fixture creation workflow. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections for each use case, references existing fixtures and test files for naming conventions without deep nesting, appropriate for a focused skill under 50 lines. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
69%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- Reviewed
Table of Contents
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.