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.
49
55%
Does it follow best practices?
Impact
—
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 its niche around Rails routing with concrete techniques. However, it lacks an explicit 'Use when...' clause, which is important for Claude to know when to select this skill. The trigger terms could also be expanded to include more natural user language variations.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Rails routes, routes.rb, URL paths, routing configuration, or endpoint definitions.'
Include common user-facing trigger terms like 'routes.rb', 'routing', 'URL paths', 'endpoints', or 'config/routes' to improve matching with natural user requests.
| 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 'config/routes'. Users might say 'add a route' or 'fix my routes file' which aren't well covered. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Rails routes specifically, with distinct terminology like 'route concerns', 'shallow nesting', and 'RESTful resource routing' that would not easily conflict with other skills. | 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 Rails routing examples and covers the topic comprehensively, which is its main strength. However, it is severely bloated—explaining concepts Claude already knows, including redundant descriptive sections (like 'Common Routing Patterns' which just restates earlier code in prose), and dumping everything into a single monolithic file. The workflow sections lack validation checkpoints that would ensure route changes don't break the application.
Suggestions
Cut the 'Purpose', 'Context', 'Benefits', 'Why This Matters', and 'Common Routing Patterns' prose sections entirely—Claude knows what RESTful routing and shallow nesting are, and the code examples already demonstrate the patterns.
Split into multiple files: keep SKILL.md as a concise overview with the complete example and review checklist, then move anti-patterns to ANTI_PATTERNS.md, advanced patterns to ADVANCED.md, and detailed examples to EXAMPLES.md with clear references.
Integrate validation steps into the workflows: after generating or updating routes, explicitly instruct to run `rails routes | grep <resource>` to verify the output matches expectations before proceeding.
Remove the 'Last Updated: February 2026' date stamp—time-sensitive information without deprecation context adds no value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. It explains basic Rails concepts Claude already knows (what RESTful routing is, what shallow nesting means, what singular resources are), includes lengthy 'Benefits' and 'Why This Matters' sections with obvious points, and the 'Common Routing Patterns' section near the end is pure description with no code—just restating what was already shown. The 'Purpose' and 'Context' sections at the top are pure filler. | 1 / 3 |
Actionability | The skill provides extensive, executable Ruby code examples throughout—concern definitions, resource declarations, route resolver syntax, bash commands for testing routes, and a complete example routes file. All code is copy-paste ready and specific to Rails routing conventions. | 3 / 3 |
Workflow Clarity | The 'Usage Instructions for AI Agents' section provides clear numbered steps 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. For route changes that could break an application, explicit verify-then-proceed steps should be embedded in the workflows. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files despite being well over 300 lines. The anti-patterns section, advanced patterns, common routing patterns descriptions, and complete example structure could all be split into separate reference files. Everything is inline, making it a large context burden with no navigation structure beyond flat headings. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (616 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
- Repository
- RoleModel/rolemodel-skills
- Commit
72e8136
- 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.