api-rest-collection
Use when creating or modifying REST API endpoints (Rails controllers, engine routes, API actions). Requires generating or updating an API Collection file (e.g., Postman Collection v2.1) so the new or changed endpoints can be tested. Trigger words: endpoint, API route, controller action, API collection, request collection.
86
82%
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 strong skill description that clearly communicates both what the skill does and when to use it. It provides specific technical context (Rails, Postman Collection v2.1) and explicit trigger terms, making it easy for Claude to select appropriately. The description is concise yet comprehensive, covering the dual nature of the skill (endpoint creation + collection file generation).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating or modifying REST API endpoints', 'Rails controllers, engine routes, API actions', 'generating or updating an API Collection file', and specifies the format 'Postman Collection v2.1'. | 3 / 3 |
Completeness | Clearly answers both 'what' (creating/modifying REST API endpoints and generating API Collection files) and 'when' (explicit 'Use when' clause at the start plus trigger words listed at the end). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger words that users would say: 'endpoint, API route, controller action, API collection, request collection'. Also includes domain terms like 'REST API endpoints', 'Rails controllers', and 'Postman Collection' throughout the description. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche combining REST API endpoint creation with API collection file generation, specifically mentioning Rails controllers and Postman Collection v2.1. Unlikely to conflict with generic coding or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that clearly defines when and how to generate/update API collection files alongside REST endpoint changes. Its main strengths are the concrete JSON example and clear rules table. Its weaknesses are redundancy across sections (language rule repeated 3x, location guidance repeated) and the lack of an explicit validation step for the generated collection file.
Suggestions
Add a validation step to the workflow — e.g., 'Validate the generated JSON against the Postman v2.1 schema or attempt an import to verify correctness before committing.'
Consolidate the repeated language and file-location guidance into single authoritative locations rather than restating them in Quick Reference, dedicated sections, and Common Mistakes.
Consider moving the detailed Collection Structure and Example Snippet into a separate reference file (e.g., COLLECTION-FORMAT.md) and linking to it, keeping SKILL.md as a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy — the language requirement is stated three times (quick reference table, dedicated section, and common mistakes), and the file location guidance is also repeated. Some sections like 'Red Flags' largely duplicate 'Common Mistakes'. However, it doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | Provides a concrete, copy-paste-ready JSON example of the Postman collection format, specific file paths, clear rules for what each request item must contain (method, URL with variables, headers, body), and a well-structured quick reference table. The guidance is specific enough to execute immediately. | 3 / 3 |
Workflow Clarity | The HARD-GATE section establishes a clear trigger (endpoint change → update collection), but there's no explicit validation step — e.g., no instruction to validate the generated JSON against the Postman v2.1 schema, or to verify the collection imports correctly. For a skill involving file generation that must stay in sync, a validation/verification checkpoint is missing. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections and tables, and references external skills (rails-graphql-best-practices, rails-engine-author, etc.). However, the integration table references skills without links, and the content is somewhat long for a SKILL.md — the collection structure details and example could potentially be split into a reference file. The skill does stay at one level of reference depth though. | 2 / 3 |
Total | 9 / 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
- igmarin/rails-agent-skills
- Commit
ae8ea63
- 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.