api-contract-review
Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when user asks "review API", "check endpoints", "REST review", or before releasing API changes.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a well-crafted skill description that excels across all dimensions. It provides specific review criteria (HTTP semantics, versioning, backward compatibility, response consistency), includes natural trigger terms users would actually say, and has an explicit 'Use when' clause with both keyword triggers and situational context. The REST API focus creates a clear, distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency.' These are distinct, concrete review aspects rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what (review REST API contracts for HTTP semantics, versioning, backward compatibility, response consistency) AND when (explicit 'Use when' clause with trigger phrases and situational context 'before releasing API changes'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'review API', 'check endpoints', 'REST review', 'API changes'. These are realistic phrases a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on REST API contract review with distinct triggers like 'REST review', 'check endpoints', and specific review criteria. Unlikely to conflict with general code review or other API-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable API review skill with excellent concrete examples and clear anti-patterns. The checklist format and grep commands make it immediately usable. However, it's somewhat verbose for a skill file and could be more token-efficient by assuming Claude's knowledge of basic HTTP concepts and splitting detailed reference material into separate files.
Suggestions
Remove or condense basic HTTP verb definitions (idempotent, safe) that Claude already knows - keep only the decision table
Split detailed sections (HTTP Status Codes, Error Response Format) into separate reference files and link from main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory content Claude already knows (e.g., basic HTTP verb definitions, what idempotent means). The tables and examples are useful but could be tighter in places. | 2 / 3 |
Actionability | Excellent concrete guidance with fully executable Java code examples, clear ❌/✅ patterns, specific bash commands for pattern detection, and copy-paste ready code snippets throughout. | 3 / 3 |
Workflow Clarity | Clear review checklist with explicit validation steps, logical progression from quick reference through detailed sections, and a token optimization workflow with specific grep commands for systematic review. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a quick reference table, but it's a monolithic document (~300 lines) that could benefit from splitting detailed sections (like HTTP Status Codes, Error Response Format) into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- piomin/claude-ai-spring-boot
- Commit
d9fda23
- 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.