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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with strong, sequenced workflows and verification steps, but it is over-long for a single file: redundant examples and basic-concept explanations inflate the token budget and no detail is offloaded to reference files.

Suggestions

Move Advanced Patterns, Common Routing Patterns, and the Complete Example into reference files (e.g. references/advanced-patterns.md, references/common-patterns.md) and link to them one level deep to improve progressive disclosure.

De-duplicate the commentable concern example — present it once and reference back rather than repeating it across four sections.

Cut explanations of Rails basics Claude already knows (what singular resources are, collection vs member semantics) and keep only the non-obvious guidance.

Dimension	Reasoning	Score
Conciseness	The body is ~600 lines with notable redundancy — the commentable concern example recurs in sections 1, the complete example, anti-patterns, and advanced patterns — and re-explains concepts Claude already knows (singular vs plural resources, collection vs member routes). It is mostly valuable but could be tightened substantially.	2 / 3
Actionability	Dozens of executable Ruby snippets, concrete `only:`/`except:`/`shallow:` directives, and copy-paste-ready `rails routes` verification commands make the guidance immediately actionable.	3 / 3
Workflow Clarity	The "Usage Instructions for AI Agents" section gives clearly sequenced numbered workflows for review/generate/update, backed by a review checklist and a "Testing Routes" verification step that forms a validate-after-change feedback loop.	3 / 3
Progressive Disclosure	Everything lives in one ~600-line SKILL.md with no bundle files; sections like Advanced Patterns, Common Routing Patterns, and the Complete Example are well-organized but content that would benefit from being split into referenced files is kept inline.	2 / 3
	Total	10 / 12 Passed

Description

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 specific and well-targeted to a clear Rails-routing niche, but it lacks an explicit "Use when..." trigger clause, leaving the "when" half of completeness only implied. Adding natural trigger terms inline would round it out.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing or writing config/routes.rb, adding nested or resourceful routes, or fixing route helper issues."

Surface a few natural trigger terms in the description itself (routes.rb, route helpers, nested routes) rather than only in metadata.triggers.

Trim "following professional patterns and best practices" — it is mild fluff that adds little signal beyond the concrete technique list.

Dimension	Reasoning	Score
Specificity	"Review, generate, and update Rails routes" lists multiple concrete actions, further itemized as "RESTful resource routing, route concerns... shallow nesting strategies, and advanced route configurations."	3 / 3
Completeness	It clearly answers "what" (review/generate/update Rails routes with named techniques) but never says "when" to use it; no "Use when..." clause is present, which caps completeness at 2.	2 / 3
Trigger Term Quality	"Rails routes" is a natural term, but the description omits common variations a user would say (routes.rb, route helpers, nested routes) and relegates triggers to metadata rather than stating them inline.	2 / 3
Distinctiveness Conflict Risk	The Rails routing niche is specific and unlikely to trigger for unrelated skills; the named techniques (concerns, shallow nesting) reinforce a distinct scope.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: RoleModel/rolemodel-skills
Commit: f61959b

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.