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

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/routing-patterns/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

The body is highly actionable with comprehensive executable Rails routing examples and a clear review/generate/update workflow plus verification commands, but it is a long monolithic file with repeated pattern sections and no reference files for progressive disclosure.

Suggestions

Move Advanced Patterns, Common Routing Patterns, and the Complete Example into reference files (e.g., ADVANCED.md, PATTERNS.md) referenced one level deep from SKILL.md to improve progressive disclosure.

De-duplicate the commentable/duplicatable/archivable/searchable patterns shown in §1, Anti-Patterns, and Common Routing Patterns to tighten conciseness.

Embed an explicit validate→fix→retry checkpoint inside the generate/update workflows (e.g., 'run `rails routes` and confirm new routes before finishing') rather than only at the end.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable code rather than concept explanation, but patterns (commentable, duplicatable, archivable, searchable, versioned, taggable) are repeated across §1, Anti-Patterns, and Common Routing Patterns, which is tightening-eligible padding.	3 / 5
Actionability	Copy-paste-ready Ruby blocks cover concerns, shallow nesting, only/except, custom params, resolvers, constraints, and a full routes.rb, plus executable `rails routes` verification commands, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Numbered review/generate/update procedures and a 'Testing Routes' verification section give a clear sequence with checkpoints, but validation is a standalone tail section rather than an embedded validate→fix→retry loop within each workflow.	4 / 5
Progressive Disclosure	No bundle files exist and the ~620-line SKILL.md inlines content that could be split (Advanced Patterns, Common Routing Patterns, Complete Example); section headers provide structure but there are no one-level-deep references to offload detail.	3 / 5
	Total	15 / 20 Passed

Description

58%Weight 40%Scale 1-5

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 clearly states what the skill does and covers a well-scoped Rails-routing niche, but it lacks an explicit 'when to use' trigger clause and leans on a single natural keyword, leaving trigger guidance and completeness mid-range.

Suggestions

Append an explicit 'Use when ...' clause naming concrete triggers (e.g., 'Use when editing routes.rb, adding nested resources, or refactoring repeated route patterns').

Surface natural user phrases like 'routes.rb', 'nested routes', and 'route helpers' directly in the description rather than only in metadata.triggers.

Replace the abstract 'advanced route configurations' with one or two concrete capabilities to lift specificity toward a 5.

Dimension	Reasoning	Score
Specificity	Names the Rails-routing domain and three concrete verbs (review, generate, update) plus four coverage areas (RESTful routing, concerns, shallow nesting, advanced configs); 'advanced route configurations' stays abstract, keeping it just below a 5.	4 / 5
Completeness	The 'what' is clear (review/generate/update Rails routes with named patterns), but there is no 'Use when...' clause or explicit trigger guidance in the description, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	The description contains the natural phrase 'Rails routes' but omits common variations users say ('routes.rb', 'nested routes', 'route helper') that only appear in metadata.triggers, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Rails route authoring/review is a clear niche with distinct triggers; only minor overlap risk with a generic Rails skill, fitting the 'mostly distinct' anchor better than the fully-distinct 5.	4 / 5
	Total	14 / 20 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 (621 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: RoleModel/rolemodel-skills
Path: skills/routing-patterns/SKILL.md
Commit: 6d600e9

Reviewed: 5 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.