Name: new-rails-project
Rating: 52.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

new-rails-project

Create a new Rails project

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

Quality

Content

65%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 a concise, well-organized spec of the target stack and conventions with a verification step, but it reads as a preference checklist rather than an executable, sequenced workflow and omits the actual scaffold commands needed to build the project.

Suggestions

Add the concrete generation sequence, e.g. the `rails new` command with the relevant flags and the order to integrate Inertia.js, Vite, React, Sidekiq, and Tailwind.

Restructure the guidance into an ordered workflow with checkpoints (generate -> configure database -> add stack -> run migrations -> verify) instead of topic-grouped bullets.

Drop the parenthetical glosses for well-known tools (React, Vite, Tailwind) to trim tokens Claude does not need.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet lists with a verify step, but includes brief parentheticals explaining well-known tools ("React ~19.2 - Frontend UI framework", "Tailwind CSS ~4 - Utility-first CSS framework") that Claude does not need, fitting the efficient-with-minor-trimmable-overexplanation anchor.	4 / 5
Actionability	Concrete specifics are present (exact versions, gem names, commands like `bundle exec rubocop -a` and `bundle exec brakeman`), but the actual scaffold/integration steps (e.g. the `rails new` invocation, wiring Inertia.js + Vite + React) are absent, leaving key executable details missing.	3 / 5
Workflow Clarity	The content is organized by topic rather than as an ordered sequence of steps, and while a verification checkpoint exists ("Verify ... by running bin/rails server"), the generation workflow has no explicit ordering or intermediate checkpoints, matching the steps-listed-but-validation-gaps anchor.	3 / 5
Progressive Disclosure	The body is under 50 lines, single-purpose (generate a Rails boilerplate), and uses well-organized section headers with no bundle files and no need for external references, satisfying the simple-skill exception for a top score.	5 / 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 is clear and specific about creating a Rails project but lacks any explicit trigger guidance for when to use it. It is concise and distinct but would benefit from a "Use when..." clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating a new Ruby on Rails project or scaffolding a Rails app."

Include natural synonyms like "Ruby on Rails", "Rails app", or "scaffold" to broaden trigger coverage.

Optionally hint at the stack to improve distinctiveness, e.g. "Create a new Rails 8 project with Inertia.js, React, and Tailwind."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Rails") and one concrete action ("Create a new Rails project"), matching the anchor that names a domain with 1-2 concrete actions; it is more concrete than the generic score-2 example but not comprehensive.	3 / 5
Completeness	It clearly states what the skill does ("Create a new Rails project") but provides no "Use when..." trigger guidance, so per the missing-trigger cap it cannot exceed 3 and matches the clear-what / missing-when anchor.	3 / 5
Trigger Term Quality	"Rails" is a natural keyword a user would say, but only that single term appears with no common synonyms or variations (e.g. "Ruby on Rails", "Rails app", "scaffold"), fitting the some-relevant-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	"Create a new Rails project" carves a distinct niche with low conflict risk versus other skills, with only minor overlap risk against other Rails-related skills, matching the mostly-distinct anchor rather than the fully-distinct score-5 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/new-rails-project/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.