rails-upgrade
Use when upgrading a Rails application from one version to another, assessing upgrade readiness, planning a multi-hop upgrade path, or investigating breaking changes, deprecation warnings, gem compatibility issues, or config.load_defaults transitions between any Rails versions from 5.2 through the latest release.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 description with excellent trigger term coverage and completeness, clearly specifying when Claude should select this skill. Its main weakness is that the capabilities lean slightly toward categories of concerns rather than listing concrete discrete actions the skill performs. Overall, it would perform very well in a multi-skill selection scenario.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Rails upgrades) and mentions several relevant actions like 'assessing upgrade readiness', 'planning a multi-hop upgrade path', and 'investigating breaking changes', but these read more like categories of concerns than concrete discrete actions (e.g., it doesn't say 'updates Gemfile', 'modifies config files', 'runs rails app:update'). | 2 / 3 |
Completeness | The description opens with an explicit 'Use when' clause that clearly answers both what (upgrading Rails, assessing readiness, planning upgrade paths, investigating breaking changes/deprecations/gem compatibility/config transitions) and when (upgrading between Rails versions, encountering deprecation warnings, dealing with gem compatibility issues). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'upgrading a Rails application', 'upgrade readiness', 'breaking changes', 'deprecation warnings', 'gem compatibility', 'config.load_defaults', specific version references ('5.2 through the latest release'). These are highly natural phrases a developer would use when seeking upgrade help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Rails', 'upgrade', specific version ranges, 'config.load_defaults', and 'multi-hop upgrade path' creates a very clear niche that is unlikely to conflict with other skills like general Ruby development or Rails new-project scaffolding. | 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 strong, well-architected skill that provides a comprehensive Rails upgrade workflow with excellent validation gates, concrete commands, and appropriate progressive disclosure to reference files. The workflow clarity is particularly impressive with its HARD GATE pattern preventing common upgrade mistakes. Minor conciseness improvements could be made by trimming the overview paragraph and tightening some explanatory text, but overall the content earns its token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and well-structured, but includes some unnecessary content like the overview paragraph explaining what the skill does (Claude doesn't need this meta-description), and the attribution section which, while nice, consumes tokens. The Ruby compatibility table and report template are valuable, but the 'Announce at start' instruction and some framing text could be tighter. | 2 / 3 |
Actionability | The skill provides highly concrete, executable guidance throughout: specific URLs for API fetches, exact commands to run (bundle exec rspec, git checkout -b, bundle update rails, bin/rails app:update), specific file paths to check, and a complete report template with placeholders. The detection workflow references specific tools (Grep, Glob, Read) and specific reference files. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit HARD GATE checkpoints at Steps 1 (test suite must pass), 4 (load_defaults verification), and 6 (user approval before changes). Clear sequencing with numbered steps, feedback loops (run tests → fix → rerun), and explicit stop conditions. Multi-step upgrade handling includes 'do NOT proceed until tests pass' gates. | 3 / 3 |
Progressive Disclosure | The skill is a clear overview that appropriately delegates detailed content to one-level-deep reference files (7 reference files + 1 script + 1 cross-reference, all clearly described in a summary table). The main SKILL.md contains the workflow and decision logic while pointing to specific files for breaking changes, detection patterns, gem compatibility, etc. | 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.