CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 an operational, well-structured upgrade workflow with explicit hard-gate validation checkpoints and error-recovery loops, backed by real one-level-deep reference files. It is highly actionable, with only minor conciseness and inline-command gaps keeping it from a perfect score.

Suggestions

Tighten the 'Upgrading to Rails 8.2 (Unreleased)' section — its rationale is valuable but could be trimmed to the two numbered reasons and a one-line re-verify instruction.

Where Step 3/4 sub-steps say 'Read references/X.md', consider inlining the single most critical pattern or threshold so the agent can act without a file round-trip in common cases.

DimensionReasoningScore

Conciseness

The body is dense and operational — version tables, hard-gate blocks, exact URLs and grep targets — without explaining concepts Claude already knows, but the unreleased-Rails-8.2 section and some time-sensitive tables could be tightened slightly, so it sits noticeably above the 3 anchor (efficient with minor trim possible) but short of the fully lean 5 anchor.

4 / 5

Actionability

Provides concrete executable guidance — exact GitHub API compare URLs, `bundle exec rspec`/`bundle exec rails test`, `git checkout -b rails-{TARGET}-upgrade`, `bin/rails app:update`, `./scripts/fetch-changelogs.sh main ./changelogs`, and a ready WebFetch prompt — with only minor gaps where sub-steps defer to reading reference files, matching the 4 anchor rather than the fully copy-paste 5 anchor.

4 / 5

Workflow Clarity

Steps 0 through 6 are explicitly sequenced with multiple HARD GATE validation checkpoints (green test baseline, load_defaults verification, explicit user approval before any file change) and error-recovery feedback loops ('If tests fail: STOP. Report failures. Do NOT proceed until baseline is green'), matching the 5 anchor for clear sequencing with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview/workflow pointing to seven real reference files and one script, all verified to exist and only one level deep, each signaled inline at its point of use and summarized in a Reference Files table, matching the 5 anchor for a clear overview with well-signaled one-level-deep references and easy 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.

The description is specific, trigger-rich, and explicitly pairs a 'what' with a 'Use when...' clause scoped to Rails upgrades from 5.2 to latest. It is highly distinct and unlikely to fire for unrelated skills.

DimensionReasoningScore

Specificity

Lists four-plus concrete actions — 'upgrading a Rails application from one version to another', 'assessing upgrade readiness', 'planning a multi-hop upgrade path', and 'investigating breaking changes, deprecation warnings, gem compatibility issues, or config.load_defaults transitions' — giving comprehensive coverage of the upgrade domain with no minor gaps, matching the 5 anchor rather than the 4 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (upgrading/assessing/planning/investigating) and 'when' via an explicit 'Use when...' clause with concrete trigger phrases, matching the 5 anchor and exceeding the 4 anchor whose 'when' is only weakly specified.

5 / 5

Trigger Term Quality

Includes the natural phrases a Rails developer would actually say — 'upgrading a Rails application', 'breaking changes', 'deprecation warnings', 'gem compatibility', 'config.load_defaults', 'multi-hop upgrade path' — with domain synonyms, approaching the comprehensive coverage of the 5 anchor rather than the 'a few natural terms missing' 4 anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche scoped to Rails version upgrades (5.2 through latest) with unmistakable triggers like 'config.load_defaults transitions' and 'multi-hop upgrade path', giving minimal conflict risk per the 5 anchor.

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
lucianghinda/superpowers-ruby
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.