Name: skill-rails-upgrade
Rating: 55.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

skill-rails-upgrade

Analyze Rails apps and provide upgrade assessments

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

71%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 highly actionable with concrete commands and a well-sequenced upgrade workflow including user confirmation and verification, but it is hurt by duplicated 'When to Use' blocks and a monolithic single-file structure that should be split into references.

Suggestions

Remove the two duplicate 'When to Use This Skill' blocks (and the broken 'Use this skill when working with analyze rails apps...' sentence) to eliminate padding.

Extract the JavaScript-dependency checklist (Step 7) and the selective-merge process (Step 9) into reference files (e.g. JS_DEPENDENCIES.md, SELECTIVE_MERGE.md) linked from the body.

Make the verify step an explicit feedback loop: 'if tests fail, fix the issue and re-run bin/rails test before proceeding'.

Dimension	Reasoning	Score
Conciseness	Mostly actionable and efficient, but the 'When to Use This Skill' block is duplicated three times verbatim with broken phrasing, and several summary-template blocks repeat information already covered, so it cannot reach the lean 4-5 anchors.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (gh api, npm view, bin/rails db:migrate, grep pipelines) plus concrete URLs and tables covering the common upgrade cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Ten steps are clearly sequenced with a user-confirmation checkpoint and a verify-upgrade step (9.6) for this destructive/batch workflow, but the explicit validate-fix-retry feedback loop is only implied rather than stated, fitting 'clear sequence with most checkpoints, minor gaps'.	4 / 5
Progressive Disclosure	Has good section/step structure but ~400 lines are inlined in a single file with no references; the JS-dependency and selective-merge detail could live in separate reference files, fitting the 'some structure, content that should be separate is inline' anchor.	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 states a clear domain and purpose but is terse and lacks an explicit 'Use when...' trigger clause, which caps completeness and trigger-term quality at the midpoint. It is reasonably distinct but would benefit from synonyms and explicit trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when upgrading a Rails app, bumping the Rails version, or assessing upgrade compatibility'.

Include natural synonyms users say ('Rails version', 'migrate Rails', 'Ruby on Rails') to improve trigger-term coverage.

Expand the action list beyond 'analyze' and 'provide assessments' to concrete capabilities like 'detect current version, fetch the upgrade guide, diff configs, and merge files selectively'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Rails apps') with two concrete actions ('Analyze', 'provide upgrade assessments'), matching the anchor for 1-2 concrete actions but not the comprehensive multi-action list of a 4 or 5.	3 / 5
Completeness	Provides a clear 'what' (analyze Rails apps, provide upgrade assessments) but no explicit 'Use when...' trigger clause; per the judging guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms like 'Rails apps' and 'upgrade' that a user might say, but misses common variations such as 'Rails version', 'migrate', 'bump', or 'Ruby on Rails', fitting the 'some relevant keywords, missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The Rails-upgrade niche is mostly distinct with only minor overlap risk against general Ruby/Rails skills, though brevity and lack of trigger phrasing keep it just short of the clear-niche 5 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 57c135b

Reviewed: 18 hours ago

Table of Contents

Discovery Implementation Validation

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.