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

87%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

This skill excels as a documentation index — it's concise, well-organized, and provides excellent progressive disclosure through a clear topic map pointing to specific reference files. Its main weakness is the lack of any inline actionable content (quick examples, common patterns, or decision guidance) that would help Claude without needing to open reference files. The absence of bundle files makes it impossible to verify that the referenced paths actually exist.

Suggestions

Add a brief 'Quick Reference' section with the 3-5 most commonly needed patterns (e.g., basic model definition, route definition, migration command) so Claude can handle simple queries without loading reference files.

Add brief annotations to each reference link describing when to use it vs. similar references (e.g., when to consult action_controller_overview.md vs action_controller_advanced_topics.md).

Dimension	Reasoning	Score
Conciseness	The content is extremely lean — it's essentially a well-organized topic map with file references. No unnecessary explanations of what Rails, ActiveRecord, or any other concept is. Every line serves as navigation.	3 / 3
Actionability	The skill is a reference index, not an instructional guide. It provides clear pointers to specific files for specific topics, but contains no executable code, commands, or concrete examples itself. For a documentation index skill this is somewhat expected, but it still lacks any direct actionable guidance.	2 / 3
Workflow Clarity	This is a reference/lookup skill rather than a multi-step workflow skill. For its purpose (directing Claude to the right reference file for a given Rails topic), the single action is unambiguous: identify the topic, find the matching reference file, and consult it. The clear categorization makes this straightforward.	3 / 3
Progressive Disclosure	This is an exemplary progressive disclosure structure — a concise overview/topic map with well-organized categories and clearly signaled one-level-deep references to specific files. Navigation is intuitive with logical groupings (Active Record, Action Controller, Testing, etc.).	3 / 3
	Total	11 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger term coverage and clear 'Use when' guidance that makes it easy for Claude to select appropriately. Its main weakness is that it describes topic coverage rather than concrete actions—it says what it knows about but not what it does (e.g., look up docs, provide examples, explain APIs). Despite this, the comprehensive list of Rails subsystems and explicit trigger clause make it highly functional for skill selection.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Provides official Rails documentation references, code examples, and API details' instead of just 'Official Rails documentation'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Rails documentation) and lists many specific topic areas (ActiveRecord, routing, controllers, etc.), but it describes what it covers rather than what concrete actions it performs. It doesn't specify actions like 'look up API references', 'provide code examples', or 'explain configuration options'.	2 / 3
Completeness	Clearly answers both 'what' (official Rails documentation) and 'when' with an explicit 'Use when asked about any Rails-specific topic' clause followed by a comprehensive list of trigger topics.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'Rails', 'ActiveRecord', 'routing', 'controllers', 'views', 'mailers', 'jobs', 'Action Cable', 'Action Text', 'Active Storage', 'migrations', 'validations', 'callbacks', 'associations', 'caching', 'security'. These are all terms Rails developers naturally use.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Rails-specific topics with the qualifier 'Official Rails documentation' and a detailed enumeration of Rails-specific subsystems. This is unlikely to conflict with general Ruby skills, other framework skills, or generic documentation skills.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: lucianghinda/superpowers-ruby
Commit: 712d734

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