validating-api-responses

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill validating-api-responses

Validate API responses against schemas to ensure contract compliance and data integrity. Use when ensuring API response correctness. Trigger with phrases like "validate responses", "check API responses", or "verify response format".

48%

Overall

Validation — 81%

Implementation — 7%

Activation — 82%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

This skill content fundamentally misses its stated purpose. Despite being titled 'Validating API Responses', the content describes general API development (creating endpoints, controllers, models) rather than response validation. There are no schema validation examples, no validation libraries mentioned, and no concrete guidance on checking API responses against contracts.

Suggestions

Replace the generic API development instructions with actual response validation content: show how to validate responses using libraries like Ajv (JSON Schema), Zod, or similar

Add executable code examples demonstrating schema validation, such as validating a response object against a JSON Schema or OpenAPI spec

Include a clear workflow for response validation: define schema → validate response → handle validation errors → report mismatches

Remove irrelevant prerequisites (database services, auth strategies) and replace with validation-specific requirements (schema definitions, validation library installation)

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that doesn't relate to API response validation. Prerequisites list general API development concerns (database services, auth strategies) rather than validation-specific needs. The instructions describe general API development, not response validation.	1 / 3
Actionability	No concrete code examples for validating API responses. No schema validation libraries mentioned, no executable validation code, no specific commands. Instructions are vague ('Add input validation and schema enforcement') without showing how.	1 / 3
Workflow Clarity	The numbered steps describe general API development workflow, not response validation workflow. No validation checkpoints for the actual task (validating responses). Steps are disconnected and don't form a coherent validation process.	1 / 3
Progressive Disclosure	References to external files (implementation.md, errors.md, examples.md) are present and one-level deep, but the main content is poorly organized. The skill offloads all useful content to external files while the main file contains irrelevant boilerplate.	2 / 3
	Total	5 / 12 Passed

Activation

82%

This is a solid description with explicit trigger guidance and clear 'Use when' clause. The main weakness is the somewhat generic capability statement - it tells us the purpose (validate responses against schemas) but doesn't enumerate specific validation actions or supported schema formats. The trigger terms are well-chosen and natural.

Suggestions

Add specific concrete actions like 'detect missing required fields, validate data types, check nested object structures, verify array formats'

Specify supported schema types (e.g., JSON Schema, OpenAPI) to improve distinctiveness from other validation skills

Dimension	Reasoning	Score
Specificity	Names the domain (API responses, schemas) and the core action (validate), but lacks comprehensive specific actions. Could list concrete capabilities like 'compare response fields against schema definitions, detect missing required fields, validate data types'.	2 / 3
Completeness	Clearly answers both what (validate API responses against schemas for contract compliance and data integrity) and when (explicit 'Use when' clause plus 'Trigger with phrases' providing concrete examples).	3 / 3
Trigger Term Quality	Explicitly lists natural trigger phrases users would say: 'validate responses', 'check API responses', 'verify response format'. Also includes domain terms like 'schemas', 'contract compliance', and 'data integrity' that users might mention.	3 / 3
Distinctiveness Conflict Risk	Reasonably specific to API response validation, but could overlap with general API testing skills, schema validation skills, or data validation skills. The focus on 'responses' specifically helps, but 'contract compliance' is somewhat broad.	2 / 3
	Total	10 / 12 Passed

Reviewed

17 days ago

Table of Contents

Validation Implementation Activation

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.