routing-patterns
Review, generate, and update Rails routes following professional patterns and best practices. Covers RESTful resource routing, route concerns for code reusability, shallow nesting strategies, and advanced route configurations.
63
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/routing-patterns/SKILL.mdQuality
Discovery
67%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 is strong in specificity and distinctiveness, clearly identifying Rails routes as its domain and listing concrete techniques. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing some natural user trigger terms. Adding trigger guidance and common user phrasings would elevate this from good to excellent.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Rails routing, routes.rb, URL paths, RESTful endpoints, or route configuration in a Ruby on Rails application.'
Include more natural user-facing trigger terms like 'routes.rb', 'routing', 'URL paths', 'endpoints', 'Ruby on Rails', and 'namespace' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Review, generate, and update Rails routes' along with specific techniques like 'RESTful resource routing, route concerns for code reusability, shallow nesting strategies, and advanced route configurations.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions and techniques, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'Rails routes', 'RESTful', 'route concerns', 'shallow nesting', but misses common user-facing variations like 'routes.rb', 'routing', 'URL paths', 'endpoints', or 'Ruby on Rails'. Users might say 'add a route' or 'fix my routes file' which aren't well covered. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Rails routes specifically, with distinct terminology like 'route concerns', 'shallow nesting', and 'RESTful resource routing' that would not overlap with other skills. This is a well-defined niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable Ruby code examples and covers Rails routing comprehensively, which is its main strength. However, it is excessively verbose—explaining many concepts Claude already knows, including descriptive sections with no code, and cramming everything into a single monolithic file. The workflow sections lack validation checkpoints integrated into the process, and the sheer length undermines its utility as a quick-reference skill.
Suggestions
Cut the 'Purpose', 'Context', and 'Common Routing Patterns' (descriptive) sections entirely—Claude already knows what RESTful routing and these patterns are. Remove explanatory prose like 'This keeps your routes DRY and maintainable' throughout.
Split into multiple files: keep SKILL.md as a concise overview with the complete example and review checklist, then move detailed patterns (concerns, shallow nesting, anti-patterns, advanced patterns) into separate reference files like CONCERNS.md, PATTERNS.md, ANTI_PATTERNS.md.
Integrate validation into workflows: after each generate/update instruction, add an explicit step like 'Verify: run `rails routes | grep <resource>` and confirm expected routes appear'.
Remove the 'Common Routing Patterns' prose section (lines describing Commentable, Duplicatable, etc. without code)—the code examples earlier already demonstrate these patterns far more effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Explains basic Rails concepts Claude already knows (what RESTful routing is, what singular resources are, what collection vs member routes do). The 'Common Routing Patterns' section is pure description with no code. The 'Purpose' and 'Context' sections restate the obvious. Many sections could be cut by 50%+ without losing actionable content. | 1 / 3 |
Actionability | Provides fully executable Ruby code examples throughout, concrete route definitions, specific bash commands for testing, and a complete example structure that is copy-paste ready. The anti-patterns section with before/after examples is particularly actionable. | 3 / 3 |
Workflow Clarity | The 'Usage Instructions for AI Agents' section provides clear step sequences for review/generate/update workflows, and the review checklist is helpful. However, there are no validation checkpoints or feedback loops - the 'Testing Routes' section is tacked on at the end rather than integrated into the workflows (e.g., 'after generating routes, verify with rails routes | grep <resource>'). | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. The content covers basic patterns, advanced patterns, anti-patterns, common patterns, usage instructions, and testing all in one massive document. Advanced patterns, the complete example, and the common routing patterns descriptions should be split into separate reference files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (614 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- RoleModel/rolemodel-skills
- Commit
097ad6b
- 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.