CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-rails-upgrade

Analyze Rails apps and provide upgrade assessments

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/skill-rails-upgrade/SKILL.md

The canonical home for this skill is skill-rails-upgrade in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

Strong operational content: concrete commands, well-sequenced steps, genuine validation checkpoints and error handling for a destructive-leaning workflow. It is undermined by verbatim duplicated sections and a monolithic single-file layout with no progressive disclosure.

Suggestions

Delete the duplicated 'When to Use This Skill' blocks (lines 9-13, 227-231, 391-395); keep at most one and drop the garbled 'Use this skill when working with analyze rails apps and provide upgrade assessments.' filler.

Move Step 7 (JavaScript dependencies, ~75 lines) and Step 9 (selective file update, ~140 lines) into references/ files, leaving short summaries with clearly signaled pointers in SKILL.md.

Make Step 9.4 concrete: replace 'Then copy needed files' with the actual copy command for extracting files from the temporary fresh Rails app (e.g. cp /tmp/rails_template/config/initializers/... ).

DimensionReasoningScore

Conciseness

The body is mostly efficient — dense command blocks and tables — but carries padding: the 'When to Use This Skill' block ('Analyze Rails apps and provide upgrade assessments' / 'Use this skill when working with analyze rails apps and provide upgrade assessments.') is repeated verbatim three times, and that filler sentence is also garbled. Not a 2 because the padding is confined to ~10 lines out of ~410; not a 4 because duplicated sections are pure noise that should be trimmed.

3 / 5

Actionability

Concrete, mostly copy-paste-ready commands throughout ('gh api repos/rails/rails/releases/latest --jq '.tag_name'', 'bin/rails db:migrate', 'npm outdated @hotwired/turbo-rails', 'bin/importmap pin @hotwired/turbo-rails') plus specific package tables and a worked merge example. Not a 5 because a few steps stay abstract ('Then copy needed files', 'Extract and summarize the relevant sections'); not a 3 because the guidance is executable, not pseudocode.

4 / 5

Workflow Clarity

Ten clearly sequenced steps with explicit validation checkpoints and feedback loops: verify Rails app first (Step 1), stop if customizations would be overwritten (Error Handling), user confirms the upgrade plan before execution (9.3/9.4), verify via server/console/test suite/deprecation logs (9.6), and 'Enable each new default one by one, testing after each' (Step 10). Not a 4 because checkpoints are explicit rather than minor-gapped, and an Error Handling section covers recovery paths.

5 / 5

Progressive Disclosure

All ~410 lines are inlined in SKILL.md with no bundle files (no references/, scripts/, or assets/ exist) and no internal references; the JS dependency audit (Step 7, ~75 lines) and selective file update (Step 9, ~140 lines) are content that clearly belongs in separate reference files, and the triplicated 'When to Use This Skill' blocks disrupt navigation. Not a 2 because section headers give real structure; not a 4 because nothing is split out and no references are signaled at all.

3 / 5

Total

15

/

20

Passed

Description

53%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 names a distinct, framework-specific niche but is thin: it lists only generic actions and omits any 'when to use' trigger guidance. Adding an explicit trigger clause and the concrete deliverables would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about upgrading Rails, updating the Rails version, or mentions rails app:update or new_framework_defaults.'

Enumerate the concrete actions: compare current vs latest Rails versions, fetch the official upgrade guide and railsdiff, audit JavaScript dependencies, and selectively merge config files instead of running rails app:update.

Include natural synonyms users would actually say — 'Ruby on Rails', 'update Rails', 'bump Rails version' — so the description matches varied phrasing.

DimensionReasoningScore

Specificity

The description 'Analyze Rails apps and provide upgrade assessments' names the domain ('Rails apps') and 1-2 actions ('Analyze', 'provide upgrade assessments'), but the verbs are generic and no concrete capabilities are listed (version comparison, guide/diff fetching, dependency audit, selective file merging). Not a 4 because it doesn't list several specific actions; not a 2 because it does more than name the domain.

3 / 5

Completeness

The 'what' is present ('Analyze Rails apps and provide upgrade assessments') but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because no trigger clause exists at all; not a 2 because the 'what' is clear rather than vague.

3 / 5

Trigger Term Quality

It contains the two core natural keywords ('Rails', 'upgrade') users would say, but misses common variations and synonyms: 'Ruby on Rails', 'update Rails version', 'migrate', 'rails app:update'. Matches the anchor 'Some relevant keywords but missing common variations or synonyms' ('Works with PDF files'). Not a 4 because several natural phrasings are absent; not a 2 because more than one or two generic keywords are present.

3 / 5

Distinctiveness Conflict Risk

'Rails apps' pins a specific framework and 'upgrade assessments' narrows the task, giving a clear niche with only minor overlap risk against general Rails development skills. Not a 5 because 'Analyze Rails apps' is broad enough to attract general Rails analysis queries; not a 3 because the upgrade framing is considerably more specific than 'Works with document files'.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/skill-rails-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.