CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-snooze

Use only when the user explicitly invokes /roborev-snooze

Quality

72%

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/droid/roborev-snooze/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exemplar of a small command-wrapping skill: exact commands with all variants, tight prose with genuinely non-obvious operational guidance (sandbox escalation, scope limits), and explicit error-handling behavior. Organization is clean and self-contained with no bundle files required.

DimensionReasoningScore

Conciseness

Every section carries non-obvious operational detail ('Do not start or restart the daemon because a sandboxed status probe cannot reach it'; 'Reviews continue to enqueue and run while reminders are snoozed') with zero explanation of concepts Claude already knows. Nothing can be trimmed without losing information, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The guidance is fully executable and copy-paste ready: exact commands for every argument variant ('roborev agent hook snooze --from-skill on', '--duration <duration>', the 'off' form) plus a three-example bash block covering the common cases.

5 / 5

Workflow Clarity

A single-action skill with unambiguous argument mapping ('With no action, or with on... With off...') and explicit failure-handling branches for both sandbox denial and untracked directories. The destructive/batch validation cap does not apply, and the simple-skill exception holds since the single action is unambiguous.

5 / 5

Progressive Disclosure

Roughly 50 lean lines organized into clear sections (Usage, Explicit invocation only, Sandbox access, Instructions, Examples) with no external references needed; the body references no bundle files and no references/, scripts/, or assets/ directories exist, so there are no dangling or buried references.

5 / 5

Total

20

/

20

Passed

Description

31%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 pure invocation guard: it answers 'when' with maximal precision but omits any statement of what the skill does, and it contains no natural trigger vocabulary. Its one strength is distinctiveness — explicit-invocation-only gating eliminates conflict risk.

Suggestions

State the capability in the description, e.g. 'Temporarily silences or resumes roborev Agent Hook reminder notifications for the current worktree and branch; reviews continue to enqueue and run while reminders are snoozed.'

Include natural trigger vocabulary such as 'snooze', 'silence', or 'mute review reminders' so the description documents the skill's purpose even though invocation is explicit-only.

Pair the invocation constraint with the 'what' in one line, e.g. 'Temporarily silences roborev Agent Hook reminders for the current worktree and branch. Use only when the user explicitly invokes /roborev-snooze.'

DimensionReasoningScore

Specificity

The description 'Use only when the user explicitly invokes /roborev-snooze' states no capability or action — there is no verb describing what the skill does, only an invocation constraint. It is not level 2 because even the domain function (silencing reminders) is never named.

1 / 5

Completeness

The 'when' is explicit and precise ('Use only when the user explicitly invokes /roborev-snooze') but the 'what' is entirely missing, matching the anchor 'only when is present without what'. It is not level 3 because that anchor requires a clear 'what'.

2 / 5

Trigger Term Quality

The only specific token is the literal command '/roborev-snooze' alongside 'explicitly invokes', which is a meaningful trigger and above pure jargon, but natural phrases users would say ('snooze', 'silence', 'mute review reminders') are entirely absent, keeping it below level 3.

2 / 5

Distinctiveness Conflict Risk

Triggering is restricted to explicit invocation of a uniquely named command, so it cannot fire on ambiguous phrasing and has minimal conflict risk with any other skill. Not level 4, because there is no overlap risk to weigh at all.

5 / 5

Total

10

/

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/droid/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.