rails-project-starter

Scaffold a production-ready Rails 8.x API with Ruby 3.3+, ActiveRecord, Devise authentication, Pundit authorization, RSpec testing, service objects, and Sidekiq background jobs.

Quality

63%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./backend-ruby/rails-project-starter/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable Rails scaffold skill with excellent executable code examples and clear workflow steps. The main weakness is verbosity—it includes extensive boilerplate that Claude could generate from shorter specifications, and the Integration Notes section adds bulk that could be externalized. The skill succeeds at its core purpose of enabling rapid Rails API scaffolding.

Suggestions

Extract the full code examples (controller, service, policy, etc.) into a separate PATTERNS.md file, keeping only one representative example in the main skill

Move Integration Notes to a separate REFERENCE.md file and link to it from the main skill

Reduce redundant explanations—Claude knows what Pundit policies and Sidekiq jobs are; focus on project-specific conventions only

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some redundant explanations (e.g., explaining what Sidekiq does, what Pundit policies are). The extensive code examples are valuable but could be trimmed—Claude knows Rails patterns and doesn't need every file spelled out in full.	2 / 3
Actionability	Excellent actionability with fully executable scaffold commands, complete code examples for every major component (controllers, services, models, policies, specs), and copy-paste ready configurations. The 'First Steps After Scaffold' section provides clear sequential instructions.	3 / 3
Workflow Clarity	Clear sequential workflow from scaffold command through setup steps. The 'First Steps After Scaffold' section provides explicit numbered steps with verification (health endpoint check). Common commands section enables easy reference for ongoing development tasks.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document (~350 lines) that could benefit from splitting detailed patterns into separate reference files. The Integration Notes section at the end could be a separate REFERENCE.md file.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 excels at specificity with a detailed technology stack but critically lacks any 'Use when...' guidance, making it incomplete for skill selection purposes. The technical terms are appropriate for the target audience but could benefit from more natural language variations that users might employ when requesting this type of project setup.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'new Rails project', 'Rails API setup', 'scaffold Rails application', or 'create Rails backend'

Include common variations of terms users might say: 'Ruby on Rails', 'new API project', 'Rails starter', 'authentication setup'

Consider adding context about when NOT to use this skill (e.g., 'not for existing Rails projects or non-API applications') to further reduce conflict risk

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and technologies: 'Scaffold a production-ready Rails 8.x API' with specific components including 'Ruby 3.3+, ActiveRecord, Devise authentication, Pundit authorization, RSpec testing, service objects, and Sidekiq background jobs.'	3 / 3
Completeness	Describes WHAT it does (scaffold Rails API with specific stack) but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Contains good technical keywords like 'Rails 8.x', 'API', 'Devise', 'Pundit', 'RSpec', 'Sidekiq' that developers would use, but missing common variations like 'Ruby on Rails', 'auth', 'background processing', or simpler terms like 'new Rails project' or 'Rails scaffold'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche with distinct technology stack (Rails 8.x, Ruby 3.3+, specific gems). Unlikely to conflict with other skills due to the precise version requirements and comprehensive stack specification.	3 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (508 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: achreftlili/deep-dev-skills
Commit: 181fcbc

Reviewed: 4 months 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.