validating-api-schemas

Quick Review

The skill has significant misalignment between its stated purpose (validating existing API schemas against specs like OpenAPI/JSON Schema/GraphQL) and its actual content (which focuses on building/implementing new APIs). The description promises schema validation but the instructions cover API development tasks like 'implement endpoint handlers', 'add authentication middleware', and 'configure database connections'. For descriptionCoverage (2): the description is too vague for a CLI agent to know what validation tasks to perform or what outputs to expect. For taskKnowledge (3): while it references external files that may contain details, the main instructions don't align with validation tasks—no mention of validation tools, error reporting formats, or how to check schema compliance. For structure (5): the organization is clear with logical sections and references to external files, though the content itself is mismatched. For novelty (4): automated schema validation could be useful and save tokens, but the actual implementation appears generic. The skill needs refocusing: either rename/redescribe it as 'API development' or rewrite it to actually validate schemas using tools like Spectral, ajv, or GraphQL validators.