roborev-snooze

Use only when the user explicitly invokes /roborev-snooze

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./internal/skills/claude/roborev-snooze/SKILL.md

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 an efficient, fully actionable, well-structured instruction set for a simple skill, with concrete commands and clear conditional branches; only minor conciseness trimming is warranted.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence; the only mild excess is the 'Explicit invocation only' section, which restates the frontmatter trigger constraint, placing it just above the efficient midpoint rather than at fully lean.	4 / 5
Actionability	It gives copy-paste-ready commands ("roborev snooze on", "roborev snooze on --duration 2h", "roborev snooze off") covering the common on/off and duration cases with exact flag syntax.	5 / 5
Workflow Clarity	This is a simple single-purpose skill with unambiguous on/off branches, default-action and default-duration handling, and an explicit error branch for non-Git directories; the simple-skill exception applies and the operation is non-destructive, so no validation cap is triggered.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references, the content is organized into well-labeled sections (Usage, Explicit invocation only, Sandbox access, Instructions), satisfying the simple-skill progressive-disclosure exception.	5 / 5
	Total	19 / 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 functions as a precise trigger guard but fails to communicate what the skill actually does, so it is distinctive yet severely lacking in capability specificity and completeness.

Suggestions

Add a what-clause stating the capability, e.g. 'Temporarily silences or resumes roborev Agent Hook reminders for the current worktree and branch.'

Include natural trigger phrases users might say, such as 'snooze review reminders' or 'silence roborev notifications', alongside the slash command.

Keep the explicit-invocation constraint but pair it with a concise statement of the action so both 'what' and 'when' are explicit.

Dimension	Reasoning	Score
Specificity	The description ("Use only when the user explicitly invokes /roborev-snooze") names no concrete actions at all — it is purely a trigger clause, matching the 'Entirely vague; no concrete actions' anchor.	1 / 5
Completeness	Only the 'when' is present (explicit invocation); the 'what' (the skill silences/resumes Agent Hook reminders) is entirely absent, fitting the 'only when is present without what' anchor and staying under the missing-trigger cap of 3.	2 / 5
Trigger Term Quality	It contains only the slash-command token "/roborev-snooze" and omits the natural phrases a user would actually say (e.g. "snooze reminders", "silence review notifications"), landing just below the midpoint between 'one or two generic keywords' and 'some relevant keywords'.	2 / 5
Distinctiveness Conflict Risk	The trigger is a uniquely named explicit slash command, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	10 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: kenn-io/roborev
Path: internal/skills/claude/roborev-snooze/SKILL.md
Commit: a87c9af

Reviewed: 5 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.