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.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 'when to use' guidance. Its main weakness is that it describes the knowledge domain rather than specific actions Claude can perform with it. The comprehensive list of Rails subsystems makes it highly distinctive and easy to match against user queries.
Suggestions
Add concrete actions the skill enables, e.g., 'Provides API references, code examples, and configuration guidance from official Rails documentation' 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 a long list of Rails-specific terms. The phrase 'Official Rails documentation' and the enumeration of Rails-specific subsystems make it very unlikely to conflict with skills for other frameworks or general Ruby skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured reference index skill that excels at progressive disclosure and conciseness. It serves as a clean topic map pointing to detailed reference files, which is the ideal pattern for a large documentation corpus like Rails Guides. The only weakness is that the skill itself contains no directly actionable content — it's purely navigational, so Claude always needs to read a referenced file before it can help.
Suggestions
Consider adding a 2-3 line 'Quick Reference' section at the top with the most commonly needed patterns (e.g., a migration command, a common query pattern) so Claude can handle simple questions without loading a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean — it's purely a topic map with file references. No unnecessary explanations of what Rails is, what MVC means, or how any of these concepts work. Every line serves as a navigation pointer. | 3 / 3 |
Actionability | The skill provides clear navigation to reference files with brief descriptions, but contains no executable code, commands, or concrete guidance itself. It's a pure index/table of contents, which means Claude must always follow a reference to get actionable information. | 2 / 3 |
Workflow Clarity | This is a reference/lookup skill rather than a multi-step workflow skill. The topic map is logically organized into clear categories (Active Record, Controllers, Views, etc.) making it unambiguous which file to consult for any given Rails topic. For a reference-style skill, this is appropriately clear. | 3 / 3 |
Progressive Disclosure | This is an exemplary progressive disclosure pattern — a concise overview/index with well-signaled one-level-deep references organized by topic area. Each reference file is clearly labeled with a brief description of its contents, making navigation easy. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%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
cb03f92
- 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.