ruby-pro

Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks.

Quality

35%

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 ./skills/ruby-pro/SKILL.md

Quality

Content

17%Scale 1-5

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

This skill is essentially a generic role description for a Ruby developer with no actionable, concrete, or executable content. It explains what Ruby development involves (metaprogramming, Rails, testing) without providing any specific guidance, code examples, or workflows that would help Claude perform better than it already would by default. The content adds almost no value beyond what Claude already knows about Ruby.

Suggestions

Add concrete, executable Ruby code examples for key patterns (e.g., a metaprogramming DSL example, an ActiveRecord query optimization pattern, a proper RSpec test structure).

Replace vague principles like 'Use blocks and enumerables effectively' with specific patterns showing preferred vs. anti-pattern code side by side.

Either provide the referenced 'resources/implementation-playbook.md' bundle file or inline the most critical content from it.

Remove the generic boilerplate sections ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') that apply to any skill and add no Ruby-specific value.

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') that adds no Ruby-specific value. The 'Use this skill when' and 'Do not use this skill when' sections are tautological. The Focus Areas and Output sections list things Claude already knows about Ruby development without adding actionable detail.	2 / 5
Actionability	There is no concrete code, no executable examples, no specific commands, and no copy-paste ready snippets. Everything is abstract direction like 'Use blocks and enumerables effectively' and 'Follow Ruby and Rails conventions' — entirely vague guidance that doesn't tell Claude anything it doesn't already know.	1 / 5
Workflow Clarity	The 'Approach' section lists a rough sequence of principles but they are not actionable steps with clear sequencing. There are no validation checkpoints, no feedback loops, and no concrete workflow for any Ruby task. The numbered list reads more like philosophical guidelines than a workflow.	2 / 5
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' but no bundle files are provided, so this reference is unverifiable and potentially broken. The content that is present is a flat list of bullet points with no meaningful structure or navigation to deeper resources.	2 / 5
	Total	7 / 20 Passed

Description

53%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 identifies the domain and several areas of specialization but remains at a high level without listing concrete actions or providing explicit trigger guidance. It lacks a 'Use when...' clause, which is critical for skill selection among many options. The Ruby/Rails focus provides reasonable distinctiveness but the description would benefit from more specific actions and natural trigger terms.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Ruby', 'Rails app', 'gem', 'RSpec', 'ActiveRecord', '.rb files', or 'Gemfile'.

Replace high-level categories with concrete actions, e.g., 'Write ActiveRecord migrations, configure routes, build custom gems, set up RSpec test suites, optimize N+1 queries'.

Include common synonyms and file extensions users might mention, such as '.rb', '.gemspec', 'Rakefile', 'bundler', 'Sidekiq', 'Rails API'.

Dimension	Reasoning	Score
Specificity	Names the domain (Ruby/Rails) and mentions a few concrete areas like metaprogramming, Rails patterns, performance optimization, gem development, and testing frameworks, but these are still fairly high-level categories rather than specific actions (e.g., 'write migrations', 'configure ActiveRecord associations').	3 / 5
Completeness	Has a clear 'what' (write idiomatic Ruby code with specific patterns) but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords like 'Ruby', 'Rails', 'metaprogramming', 'gem development', and 'testing frameworks', but misses many natural user terms like 'RSpec', 'ActiveRecord', 'Sidekiq', '.rb files', 'bundler', 'rake', 'migrations', or 'Ruby on Rails app'.	3 / 5
Distinctiveness Conflict Risk	Fairly distinct due to the specific mention of Ruby, Rails, metaprogramming, and gem development, which narrows the domain well. Minor overlap risk with generic coding skills or testing-focused skills, but the Ruby/Rails focus provides reasonable differentiation.	4 / 5
	Total	13 / 20 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/ruby-pro/SKILL.md
Commit: 57c135b

Reviewed: 2 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.