rails-background-jobs

Use when adding or reviewing background jobs in Rails. Covers Active Job, Solid Queue (Rails 8+), Sidekiq, recurring jobs, idempotency, retry/discard strategies, and queue selection.

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./rails-background-jobs/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly communicates its scope and trigger conditions. Its main strength is the explicit 'Use when...' clause combined with comprehensive trigger terms covering major Rails background job technologies. The primary weakness is that the capabilities are described more as topic coverage than concrete actions (e.g., it could specify 'configure retry strategies' or 'set up recurring jobs' instead of just listing concepts).

Suggestions

Replace the topic list with concrete action verbs, e.g., 'Configures Active Job workers, sets up Solid Queue or Sidekiq, implements retry/discard strategies, ensures idempotency, and selects appropriate queues.'

Dimension	Reasoning	Score
Specificity	Names the domain (background jobs in Rails) and lists several relevant technologies and concepts (Active Job, Solid Queue, Sidekiq, idempotency, retry/discard strategies, queue selection), but doesn't describe concrete actions beyond 'adding or reviewing'. It reads more like a topic list than specific capabilities.	2 / 3
Completeness	Explicitly answers both 'what' (covers Active Job, Solid Queue, Sidekiq, recurring jobs, idempotency, retry/discard strategies, queue selection) and 'when' ('Use when adding or reviewing background jobs in Rails'). The 'Use when...' clause is present and clear.	3 / 3
Trigger Term Quality	Excellent coverage of natural keywords users would say: 'background jobs', 'Rails', 'Active Job', 'Solid Queue', 'Sidekiq', 'recurring jobs', 'idempotency', 'retry', 'discard', 'queue selection'. These are all terms a developer would naturally use when seeking help with this topic.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Rails background jobs with specific technology names (Solid Queue, Sidekiq, Active Job) that create a distinct niche. Unlikely to conflict with other skills unless there are multiple Rails-specific skills, and even then the background job focus is narrow enough.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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

This is a solid, actionable skill with excellent concrete examples covering the most important Rails background job patterns. Its main weaknesses are redundancy between sections (Quick Reference duplicates Core Rules, two HARD-GATE blocks) and a lack of explicit validation/verification workflow beyond the initial TDD gate. The content would benefit from deduplication and slightly better progressive disclosure for its length.

Suggestions

Remove the duplicate HARD-GATE section and consolidate the idempotency requirement into a single, prominent location

Merge the 'Quick Reference' table and 'Core Rules' section to eliminate redundancy — the table already captures the rules concisely

Add an explicit post-implementation verification step to the workflow (e.g., 'Run the full spec suite, verify job appears in queue dashboard, confirm idempotency by running twice')

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but has some redundancy: the 'Core Rules' section largely repeats the 'Quick Reference' table, and the bad/good examples with inline comments over-explain concepts Claude already understands. The two separate HARD-GATE sections also add unnecessary duplication.	2 / 3
Actionability	Provides fully executable Ruby code examples for job classes, retry/discard configuration, and recurring job YAML. The examples are copy-paste ready and cover the most common patterns (idempotency checks, argument passing, error handling).	3 / 3
Workflow Clarity	The TDD gate provides a clear 3-step sequence, but the overall job creation workflow lacks explicit validation checkpoints. For jobs performing destructive side effects (charging, emailing), there's no verify-after-implementation step or feedback loop beyond the initial test gate.	2 / 3
Progressive Disclosure	The Integration table references related skills nicely, but all content is inline in a single file. The recurring.yml config, detailed Sidekiq vs Solid Queue comparison, and examples could be split into referenced files. The skill is moderately long (~130 lines) with everything in one document.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: igmarin/rails-agent-skills
Commit: ae8ea63

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.