rails-guides

Official Rails documentation. Use when asked about any Rails-specific topic including ActiveRecord, routing, controllers, views, mailers, jobs, Action Cable, Action Text, Active Storage, migrations, validations, callbacks, associations, caching, security, or internals.

Quality

93%

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

Quality

Content

86%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.

A well-structured reference-router skill: token-efficient, organized into a clear topic map pointing one level deep to real bundle files. Its main gap is the absence of an explicit instruction to read the chosen reference file before answering, which leaves actionability and workflow clarity just below the top anchor.

Suggestions

Add a one-line usage instruction near the top, e.g. 'When a Rails question arises, find the closest topic below and read that reference file before answering.'

Deduplicate association_basics.md — it appears under both Active Record and Advanced; keep it in one section or cross-reference explicitly.

For topics spanning multiple files (e.g. querying + associations for eager loading), note companion references so Claude reads all relevant material.

Dimension	Reasoning	Score
Conciseness	The body is a lean categorized index of reference files with terse one-line annotations ('Finders, scopes, joins, includes, explain'); no padding, no over-explanation of concepts Claude already knows, and every line earns its place.	5 / 5
Actionability	Concrete file pointers with specific topic annotations give mostly actionable navigation ('references/active_record_querying.md — Finders, scopes, joins'), but there is no explicit usage instruction telling Claude to read the referenced file before answering, leaving a minor gap.	4 / 5
Workflow Clarity	As a simple single-purpose index skill the lookup action is reasonably unambiguous and well-organized by category, but the body never explicitly states the read-then-answer sequence, so it stops just short of a fully explicit workflow.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references grouped by topic area; all referenced paths (verified against the references/ directory) are real files, and navigation is easy. The only blemish is association_basics.md being listed twice (Active Record and Advanced), which does not impair navigation.	5 / 5
	Total	18 / 20 Passed

Description

100%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.

A strong, third-person description that explicitly states both what the skill is and when to use it, with comprehensive coverage of Rails sub-system names as natural triggers. No verbosity or over-claims.

Dimension	Reasoning	Score
Specificity	Names the domain ('Official Rails documentation') and lists many concrete sub-systems — ActiveRecord, routing, controllers, views, mailers, jobs, Action Cable, Action Text, Active Storage, migrations, validations, callbacks, associations, caching, security, internals — giving comprehensive coverage of capabilities rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' ('Official Rails documentation') and 'when' ('Use when asked about any Rails-specific topic including ...') with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	'Use when asked about any Rails-specific topic including ActiveRecord, routing, controllers, ...' covers the natural component names users actually say, with 'Rails-specific topic' as a broad catch-all trigger phrase.	5 / 5
Distinctiveness Conflict Risk	Scoped to 'Rails-specific topic' with Rails-named components, carving a clear niche with minimal risk of triggering for non-Rails skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: lucianghinda/superpowers-ruby
Path: skills/rails-guides/SKILL.md
Commit: 99fac3d

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