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 Rails routes as its domain and listing concrete techniques. Its main weaknesses are the absence of an explicit 'Use when...' clause and missing some natural trigger terms users might use when asking about routing. Adding explicit trigger guidance would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Rails routing, routes.rb, path helpers, or URL configuration.'
Include additional natural trigger terms like 'routes.rb', 'config/routes', 'path helpers', 'URL helpers', 'namespace', and 'scope' to improve matching with common user queries.
| 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 caps this dimension at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'Rails routes', 'RESTful', 'route concerns', 'shallow nesting', but misses common user phrasings like 'routes.rb', 'routing', 'config/routes', 'namespace', 'scope', or 'path helpers' that users would naturally mention. | 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 Ruby code examples covering a comprehensive range of Rails routing patterns, which is its primary strength. However, it is severely bloated — explaining basic Rails concepts Claude already knows, repeating patterns in anti-pattern sections, and including descriptive prose sections (like 'Common Routing Patterns') that add no actionable value. The entire content is crammed into one file with no progressive disclosure, making it a poor use of context window budget.
Suggestions
Cut the file by at least 50%: remove the Purpose/Context sections, the 'Common Routing Patterns' prose descriptions, and reduce anti-patterns to a brief table rather than full before/after code blocks that repeat earlier examples.
Extract the 'Complete Example Structure', 'Advanced Patterns', and 'Anti-Patterns' sections into separate referenced files (e.g., EXAMPLE.md, ADVANCED.md, ANTI_PATTERNS.md) to improve progressive disclosure.
Add a validation checkpoint to the 'update routes' workflow: after making changes, run `rails routes | grep <resource>` to verify the generated routes match expectations before proceeding.
Remove explanations of basic Rails concepts (what singular resources are, what collection vs member means, what shallow nesting does) — Claude already knows these. Focus only on the specific patterns and conventions to follow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Includes extensive explanations of concepts Claude already knows (RESTful routing, what shallow nesting is, what singular resources are, basic Rails routing concepts). The 'Common Routing Patterns' section near the end is pure description with no code, restating what was already shown. The 'Purpose' and 'Context' sections are unnecessary preamble. Anti-patterns section largely repeats earlier content. | 1 / 3 |
Actionability | Provides fully executable Ruby code examples throughout, concrete route definitions, specific bash commands for testing routes, and clear patterns that can be directly copied into a routes.rb file. The complete example structure is copy-paste ready. | 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 — for example, no step to run `rails routes` after changes to verify correctness, and no error recovery guidance if routes conflict or fail. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files to offload content. Everything is inline in a single massive file. The anti-patterns, advanced patterns, common routing patterns descriptions, and complete example structure could all be separate referenced files. No external references are provided despite the content length warranting them. | 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
4d83977
- 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.