CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-snooze

Use only when the user explicitly invokes /roborev-snooze

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./internal/skills/grok/roborev-snooze/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a model of operational density: exact commands, defaults, failure modes, and scope guardrails with no filler. The only nit is slight semantic overlap between the intro and the Instructions section, which costs a single conciseness point.

DimensionReasoningScore

Conciseness

The body is lean and operational — sandbox failure handling, exact commands, and invocation guardrails are non-obvious information Claude does not already know. Minor redundancy between the intro ("Reviews continue to enqueue and run while reminders are snoozed") and the Instructions bullet ("Snooze affects only Agent Hook reminders in the current worktree and branch") keeps it from a 5.

4 / 5

Actionability

Fully executable, copy-paste ready commands with exact flags for all three invocation forms (on, on with --duration, off), specified defaults, Go duration syntax examples, and a complete examples block. Failure paths (permission denied, untracked git repo) are also concretely handled.

5 / 5

Workflow Clarity

A single-task skill with an unambiguous action: explicit decision branches for no-action/on/off, duration flag handling, and defined error-recovery behavior (sandbox escalation retry; report untracked-repo errors without initializing). No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines, single task, no bundle files needed — the body is appropriately self-contained with well-organized sections (Usage, invocation guardrail, Sandbox access, Instructions), satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

43%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 highly precise about when to invoke the skill and carries virtually zero conflict risk, but it omits any statement of what the skill actually does. It reads as a pure invocation guardrail rather than a capability description.

Suggestions

Add a 'what' clause stating the capability, e.g. "Temporarily silences or resumes roborev Agent Hook reminders for the current worktree and branch" followed by the existing invocation condition.

Include natural trigger phrasing such as "snooze review reminders" or "mute roborev notifications" so the description also communicates the skill's purpose in the user's vocabulary.

Mention the duration control (e.g. default eight hours, Go duration syntax) so the capability scope is explicit in the description.

DimensionReasoningScore

Specificity

The description names the domain ("roborev-snooze") but lists no concrete actions — nothing states it silences or resumes Agent Hook reminders. It is not pure abstraction (so not 1), but anchor 3 requires 1-2 concrete actions and none appear.

2 / 5

Completeness

The 'when' is maximally explicit ("Use only when the user explicitly invokes /roborev-snooze") but the 'what' is entirely absent — the description never says what the skill does. This matches the anchor "only 'when' is present without 'what'"; score 3 would require a clear 'what'.

2 / 5

Trigger Term Quality

The single trigger term "/roborev-snooze" is exactly what a user would type, but no natural-language variations or synonyms (e.g. "snooze reminders", "mute review notifications") are included. The keyword is precise rather than generic (not 2), but coverage is only one term (not 4).

3 / 5

Distinctiveness Conflict Risk

A unique command name serving as the sole trigger creates a clear niche with minimal conflict risk; no other skill would plausibly match this trigger.

5 / 5

Total

12

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

kenn-io/roborev

Path

internal/skills/grok/roborev-snooze/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.