CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ruby-upgrade

Use when upgrading the Ruby interpreter version of a Bundler/Rails app — especially "upgrade to Ruby 4", "bump Ruby to 4.0", "audit Ruby 4 compatibility", "what breaks on Ruby 4", or a specific target like "Ruby 4.0.5". Triggers on Ruby-major risk symptoms: CGI.parse/CGI::Cookie removal, Net::HTTP implicit Content-Type dropped, demoted default gems (ostruct/logger/benchmark/irb), SortedSet, Set#inspect changes, native-extension recompile crashes, openssl 4 pins, and error-tracker fingerprint drift. Also fires on ".ruby-version bump" and "ruby major upgrade". For Rails framework version bumps (6.x/7.x/8.x, config.load_defaults) use the rails-upgrade skill instead.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-engineered process skill: lean phased workflow with hard rules, concrete commands, explicit stop conditions and verification feedback loops, and an exemplary one-file reference split. The only weaknesses are minor — slight redundancy in the opening sections and a couple of instructions described rather than given verbatim.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows, but has minor trimmable redundancy: the Rails-upgrade disambiguation appears in both the Overview and the Common mistakes table, and Phase 3's docs/tmp fallback is awkwardly worded — anchor 4 ("efficient; minor instances of over-explanation").

4 / 5

Actionability

Concrete copy-paste commands throughout (`bundle update --ruby`, `bundle exec rubocop`, `bundle exec srb tc`, `rm -rf vendor/bundle && bundle install`) plus exact edit specs (`.ruby-version` → `4.0.5\n`, `AllCops: TargetRubyVersion: <major.minor>`), with minor gaps: the Explore subagent prompt is described but not given verbatim, and the non-RSpec fallback assumes Rails (`bundle exec rails test`).

4 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced with explicit validation checkpoints and feedback loops: bail if Gemfile missing, STOP on bundle resolution failure with a Blockers record, verification with fix-forward-or-stop and "Do not claim success without showing passing output", plus Phase 4 checkboxes and hard rules guarding the riskiest drift — a clear anchor-5 match.

5 / 5

Progressive Disclosure

The 217-line breaking-change inventory is properly externalized to a single one-level-deep reference (`references/ruby-4-0-changes.md`) that exists and whose change-01…change-14 anchors match the body's citations; it is well-signaled as the "source of truth" at three points, and the SKILL.md body stays a navigable process overview.

5 / 5

Total

18

/

20

Passed

Description

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

An excellent trigger-focused description with comprehensive natural phrasings, explicit symptom-based triggers, and explicit disambiguation from the Rails-upgrade skill. Its main weakness is that the capability side is compressed to a single action — the skill's actual workflow (risk audit, analysis report, mechanical edits, verification) is invisible from the description alone.

Suggestions

Compress the risk-symptom list slightly and use the freed tokens to state 2-3 concrete capabilities, e.g. "Runs a breaking-change risk audit, writes a stakeholder analysis report, applies toolchain edits (.ruby-version, Dockerfile, CI, RuboCop), and verifies via bundle/RuboCop/tests."

Move the detailed symptom triggers (CGI.parse removal, Set#inspect, fingerprint drift) into the skill body or reference inventory — users trigger on task phrasings like "upgrade to Ruby 4", not on internal change-entry names.

DimensionReasoningScore

Specificity

"Use when upgrading the Ruby interpreter version of a Bundler/Rails app" names one concrete action, but the rest of the description is trigger detail ("CGI.parse/CGI::Cookie removal", "openssl 4 pins") rather than a list of the skill's capabilities — matching anchor 3 ("1-2 concrete actions, but not comprehensive") rather than 4 ("lists several specific actions").

3 / 5

Completeness

The "when" is maximally explicit ("Use when…", "Triggers on…", "Also fires on…" with concrete phrases) and the "what" is present ("upgrading the Ruby interpreter version of a Bundler/Rails app"), but the what-side is thin — the audit/report/edit/verify operations from the body are never mentioned, so it falls just below anchor 5's "clearly and explicitly answers both".

4 / 5

Trigger Term Quality

Comprehensive natural phrasings with synonyms, question forms, and file names: "upgrade to Ruby 4", "bump Ruby to 4.0", "audit Ruby 4 compatibility", "what breaks on Ruby 4", "Ruby 4.0.5", ".ruby-version bump" — a clear anchor-5 match including file extensions.

5 / 5

Distinctiveness Conflict Risk

Ruby-interpreter vs Rails-framework is a clear niche, reinforced by the explicit boundary "For Rails framework version bumps (6.x/7.x/8.x, config.load_defaults) use the rails-upgrade skill instead"; triggers are highly Ruby-specific with minimal conflict risk.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

lucianghinda/superpowers-ruby

Path

skills/ruby-upgrade/SKILL.md

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.