CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rake-tasks

Write Rake tasks in apps that use the rolemodel_rails gem with its `Rolemodel::Utility::TaskTools` mixin, for migration-style console output, a progress spinner, a `DRY_RUN` preview mode, and optional positional arguments. Use when writing or changing a rake task, data backfill, one-off data fix, cleanup or purge job, or dev seed task, or when a task needs a dry run, a preview, progress output, or optional arguments.

Quality

94%

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

93%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 an exemplary lean skill: it assumes Claude's competence, delegates API documentation to the gem's README with a concrete lookup command, and concentrates entirely on executable patterns and genuinely non-obvious gotchas. Its only weakness is that the DRY_RUN preview loop, while correctly built into the task pattern, is never made explicit as a run-preview-then-execute sequence for the operator.

DimensionReasoningScore

Conciseness

The body is lean and delegates lookup-able material ('The gem's README is the API documentation: run `bundle info rolemodel-rails --path`... This skill doesn't restate it') while spending its tokens only on non-obvious, project-specific rules and gotchas. Nothing can be trimmed without losing information, matching anchor 5 rather than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Guidance is fully executable: a complete copy-paste-ready task example in the Shape section, a second runnable snippet for batched progress (`in_batches` with `report_interval: 1`), a concrete command to locate the gem docs, and a real invocation example (`rake users:dev[_,jdoe@example.com]`). This matches anchor 5's 'copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The destructive/batch validation requirement is met via the DRY_RUN preview pattern ('Guard every write... with `unless dry_run?`. Keep the reads and the `say` output outside the guard so the preview reports what the real run would do'), and the single action — write a task following the Shape and Rules — is unambiguous. It sits at anchor 4 rather than 5 because the preview→verify→execute loop is designed into the task code but never stated as an explicit operational sequence for the person running it.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no content that belongs in separate files; sections (Shape, Rules, Gotchas) are well-organized, and its one external reference — the gem README — is clearly signaled one level deep with the exact command to find it. Per the simple-skill guideline this warrants anchor 5.

5 / 5

Total

19

/

20

Passed

Description

95%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 a strong exemplar: it pairs a concrete, scoped 'what' with an explicit and richly synonymed 'Use when' clause, and the frontmatter's triggers list adds file extensions and API names for discovery. The only minor gap is that capabilities are listed as features rather than as comprehensive concrete actions, which keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

The description names several concrete capabilities ('migration-style console output, a progress spinner, a `DRY_RUN` preview mode, and optional positional arguments') tied to a specific gem and mixin, matching anchor 4's 'several specific actions; minor gaps'. It falls short of anchor 5 because the capabilities are phrased as features rather than a comprehensive action list (e.g., sanitize_arguments-based argument handling is only implied).

4 / 5

Completeness

It explicitly answers both questions: the first sentence states what the skill does ('Write Rake tasks... with its `Rolemodel::Utility::TaskTools` mixin, for migration-style console output...') and the second gives an explicit 'Use when...' clause with concrete trigger phrases. This is an exact match for anchor 5's exemplar pattern.

5 / 5

Trigger Term Quality

The 'Use when' clause covers natural phrases users would say — 'rake task, data backfill, one-off data fix, cleanup or purge job, or dev seed task... dry run, a preview, progress output' — and the frontmatter's triggers metadata adds file extensions and paths ('.rake', 'lib/tasks') plus API names ('TaskTools', 'say_with_time'). This comprehensively covers synonyms and extensions per anchor 5, well beyond anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — rake tasks in apps using the rolemodel_rails gem's TaskTools mixin — with triggers anchored to rake task authoring. Only closely-related rake-task work could trigger it, which is exactly the intended scope, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

RoleModel/rolemodel-skills

Path

skills/rake-tasks/SKILL.md

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.