rails-expert

An agent skill by Jeffallan, from Jeffallan/claude-skills. Tags: architecture, automation, ruby, testing, web.

What it does

Rails 7+ specialist that optimizes Active Record queries with includes/eager_load, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building Rails 7+ web applications with Hotwire, real-time features, or background job processing. Invoke for Active Record optimization, Turbo Frames/Streams, Action Cable, Sidekiq, RSpec Rails.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add Jeffallan/claude-skills --skill rails-expert

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/Jeffallan/claude-skills
cp -r claude-skills/skills/rails-expert ~/.claude/skills/rails-expert

Safety box score

Grade B, low risk: 14 of 100 risk points, rated 2026-10-19. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This is a documentation-only Rails specialist skill that mainly generates and edits Rails app code, migrations, specs, and configuration. Its main risks are local command execution (`rails`, `rspec`, `rubocop`) and broad project file writes; it also encourages headless browser system tests, but it does not include downloads, privilege escalation, or hidden prompt-injection content.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	2 (moderate)	The core workflow explicitly tells the agent to run commands like `rails generate`, `rails db:migrate`, `bundle exec rspec`, and `bundle exec rubocop`, so it can execute code and shell commands locally.
Network access	0 (none)	There are no installer-time downloads, uploads, or remote API calls in the shipped files; the WebSocket/API examples are app-code patterns, not skill behavior.
Filesystem reach	2 (moderate)	It directs broad writes inside the repo (`app/`, `db/`, `spec/`, `config/`) and even schema dumps/rollback steps such as `rails db:schema:dump` and `rails db:rollback`.
Secrets & credentials	0 (none)	The files do not ask for or access keychains, browser sessions, `.env` files, or other machine secrets; credential references are only example app code.
Privilege & persistence	0 (none)	No `sudo`, global installs, service registration, shell startup edits, or OS-level configuration changes are requested.
Instruction hijack surface	0 (none)	I found no instructions to ignore safeguards, hide actions, follow remote instructions, or otherwise subvert the agent's controls.
Irreversible actions	0 (none)	The skill does not publish, deploy, message, pay, or delete; its scope stays on local Rails implementation and testing.
Transparency	0 (none)	All shipped files are readable markdown; there are no binaries, minified blobs, or downloaded installers.

Before installing

Confirm you’re okay with the agent running `rails db:migrate`, `bundle exec rspec`, and `bundle exec rubocop` in your repo.
Read `references/rspec-testing.md` if you do not want headless browser sessions (`selenium_chrome_headless`) launched during testing.
Work in a disposable or committed branch before allowing migration rollbacks or schema dumps.
Check that no production secrets are present in the repo before letting the agent generate Rails credentials or JWT/auth code.

Rated 2026-10-19 by an automated review of 6 files from the skill's repository.

Source

Repository: Jeffallan/claude-skills (all skills from this repository)
Path: skills/rails-expert/SKILL.md
Branch: main
Updated: 2026-09-19

aws-blocks — Guides building full-stack applications with AWS Blocks — an Infrastructure-from-Code framework.
running-release-tests — Run automated release testing (UI or API) via the AWS DevOps Agent using a pre-configured test profile.
playwright-expert — Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests.
dev-browser — Browser automation with persistent named pages via the dev-browser CLI.
agents-build — Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments.
app-platform-sandbox — Create and manage isolated container sandboxes for AI agent code execution.