CtrlK
BlogDocsLog inGet started
Tessl Logo

ruby

Use when writing, reviewing, or debugging pure Ruby code — idiomatic patterns, modern 3.x+ features (pattern matching, Data.define, endless methods), error handling conventions (raise vs fail, result objects), memoization, and performance idioms. For Rails use rails-guides. For testing use minitest. For code style use sandi-metz-rules.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A dense, actionable conventions reference with excellent progressive disclosure and executable examples throughout. Weakness is workflow clarity — appropriate for a patterns reference, but it lacks an overall applied workflow and validation checkpoints.

Suggestions

Trim basic-Ruby explanations (safe navigation, predicate/bang suffixes, %w/%i, Hash#fetch) that Claude already knows, keeping only the opinionated non-obvious guidance.

Add a short 'When to apply this skill' workflow at the top (e.g. read conventions → apply to code → verify against the Common Mistakes table) to give the reference an explicit application sequence.

Consider moving the introductory idioms that Claude already knows (guard clauses, literal array constructors, safe navigation) entirely into a reference file to tighten the main body further.

DimensionReasoningScore

Conciseness

The body is largely lean and opinionated, but a few sections re-explain basic Ruby Claude already knows (safe navigation 'returns nil if any link is nil', predicate/bang suffix meaning, %w/%i, Hash#fetch) — minor over-explanation that could be trimmed.

4 / 5

Actionability

Nearly every convention is backed by copy-paste-ready, executable Ruby with good/bad contrasts, and the examples cover the common cases across error handling, modern features, performance, and layout.

5 / 5

Workflow Clarity

The method-ordering section gives a clear numbered 1-7 sequence with good/bad contrasts, but the skill is fundamentally a conventions reference rather than a multi-step workflow, and no validation checkpoints are present (none are required since there are no destructive or batch operations to cap the score).

3 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled, one-level-deep references (error_handling, modern_ruby, performance, method_ordering, ood-philosophy — all verified to exist), each introduced inline with a 'See references/X.md for ...' pointer and summarized in a final References list.

5 / 5

Total

17

/

20

Passed

Description

92%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.

A strong, specific description with explicit 'Use when' triggers and active conflict-avoidance redirects to neighboring skills. The only minor gap is missing synonyms and Ruby file-extension cues for trigger-term coverage.

DimensionReasoningScore

Specificity

Enumerates concrete actions (writing, reviewing, debugging) plus specific capability areas with named features — pattern matching, Data.define, endless methods, raise vs fail, result objects, memoization, performance idioms — giving comprehensive coverage rather than a couple of actions.

5 / 5

Completeness

It explicitly answers 'what' (idiomatic patterns, modern features, error handling, memoization, performance) and 'when' with a concrete 'Use when writing, reviewing, or debugging pure Ruby code' trigger phrase.

5 / 5

Trigger Term Quality

Natural terms users would say are present ('writing, reviewing, or debugging pure Ruby code', 'Ruby'), but it lacks common synonyms and file/extension cues (e.g. .rb, Gemfile, scripts) that would push it to full coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche ('pure Ruby code') and actively reduces conflict risk by redirecting Rails to rails-guides, testing to minitest, and code style to sandi-metz-rules.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
lucianghinda/superpowers-ruby
Reviewed

Table of Contents

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.