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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The skill is well-structured with excellent progressive disclosure and a clear step sequence, but it stays at an abstract procedural level: no executable code in the body and no explicit validation feedback loop in the main workflow limit actionability and workflow clarity.

Suggestions

Add at least one complete, executable code example in the body (e.g., an Ajv-based validator snippet or a contract-test stub) so Claude can act directly rather than infer implementation.

Make the validation feedback loop explicit in the numbered workflow (e.g., 'run contract tests -> on violation, inspect failure -> fix serializer/schema -> re-run -> only pass when clean') rather than leaving it to middleware.

Tighten the dense instruction steps into imperative, command-oriented phrasing to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with no concept-explanation padding, but the 8-step instruction list is dense and somewhat abstract ('Compile JSON Schema validators... enabling strict mode'), leaving room to tighten into more direct, imperative guidance.	2 / 3
Actionability	It names specific tools (Ajv, jsonschema) and concrete config options ('additionalProperties: false', strict/warn envs), but the body contains no executable code or copy-paste commands — only procedural descriptions of files to generate — so it falls short of fully actionable.	2 / 3
Workflow Clarity	Eight clearly sequenced steps plus an error-handling table provide a real sequence, but for build-gating validation there is no explicit validate->fix->re-run checkpoint loop in the main workflow, leaving validation implicit via middleware rather than an enforced checkpoint.	2 / 3
Progressive Disclosure	The body is a concise overview with well-signaled, one-level-deep references to implementation.md, errors.md, and examples.md — all of which exist in the bundle — and content is appropriately split across them.	3 / 3
	Total	9 / 12 Passed

Description

90%

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 clearly answers both what the skill does and when to use it, with natural trigger phrases and a distinct niche. Its only weak spot is specificity, where a single verb ('validate') stands in for a broader list of concrete actions.

Suggestions

Expand the capability description beyond a single 'validate' verb to list concrete actions (e.g., detect schema drift, flag undocumented fields, enforce required headers) to lift specificity.

Consider adding a couple more natural trigger variations (e.g., 'API contract testing', 'response shape check') to broaden the trigger surface.

Dimension	Reasoning	Score
Specificity	Names the domain ('API responses', 'schemas', 'contract compliance and data integrity') and the core action 'validate', but does not enumerate multiple distinct concrete actions in the way the score-3 anchor does, so it lands at 'names domain and some actions, not comprehensive'.	2 / 3
Completeness	Explicitly states both what it does ('Validate API responses against schemas to ensure contract compliance and data integrity') and when to use it ('Use when ensuring API response correctness') with explicit trigger phrases.	3 / 3
Trigger Term Quality	Provides natural user phrases ('validate responses', 'check API responses', 'verify response format') with good coverage of variations a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (API response schema validation) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 2cafb23

Reviewed: 2 days 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.