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/codex/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 tight, fully executable instruction sheet: exact commands, explicit error handling, and clear scope boundaries (what snooze must not touch). The only slack is mild redundancy between the invocation-policy section, the frontmatter, and the Examples block. No external references are needed at this size, and structure is clean.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but the 'Explicit invocation only' section largely restates the frontmatter description, and the Examples block repeats commands already fully specified in Instructions. This matches anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than 5, where every token would earn its place.

4 / 5

Actionability

Every variant is given as an exact, copy-paste-ready command with precise flags ('roborev agent hook snooze --from-skill on --duration 2h'), covering the common on/off/duration cases. This matches anchor 5 ('fully executable; copy-paste ready; specific examples cover the common cases').

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose action is unambiguous, and the conditionals (on/off, optional duration) plus error-recovery paths (retry with sandbox_permissions on permission denied; report non-git-repo errors without attempting registration) are explicitly handled. The simple-skill exception applies and the operation is neither destructive nor batch, so 5 is warranted.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear, well-labeled sections (Usage, Explicit invocation only, Sandbox access, Instructions, Examples). Per the rubric guideline, this earns a 5 with just well-organized sections.

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 distinctive and unambiguous about when to trigger, but it omits any statement of what the skill does, forcing the reader to open the body to learn its purpose. It also lacks the natural-language trigger phrases users might use. Adding a one-clause capability statement and a few natural trigger terms would move it firmly into good-example territory.

Suggestions

Add a 'what' clause to the description, e.g. 'Temporarily silences or resumes roborev Agent Hook reminders for the current worktree and branch. Use only when the user explicitly invokes $roborev-snooze.'

Include natural trigger phrasing users would actually say, such as 'silence review reminders' or 'snooze roborev notifications', so the skill is discoverable beyond the literal invocation token.

Mention key operational details (duration syntax like '30m'/'2h', on/off actions) briefly so the description conveys scope without opening the body.

DimensionReasoningScore

Specificity

The description names the skill domain ('$roborev-snooze') but states no concrete actions whatsoever — it is a trigger guard, not a capability description. It falls between anchor 1 (pure abstraction) and anchor 2 (domain named, actions minimal); it is not pure abstraction because it expresses a concrete invocation condition, so 2 is the best fit.

2 / 5

Completeness

Only 'when' is present ('Use only when the user explicitly invokes $roborev-snooze'); the 'what' — temporarily silencing roborev Agent Hook reminders — is entirely absent from the description. This is exactly anchor 2 ('only when is present without what') and clearly below anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

The literal invocation token '$roborev-snooze' is an unambiguous trigger, but no natural phrases a user would say (e.g. 'silence review reminders', 'snooze notifications', 'pause reminders') or synonyms appear. This matches anchor 3 ('some relevant keywords but missing common variations'), not 4, which requires broader natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

Explicit-invocation-only gating gives the skill a clear niche with minimal conflict risk — it cannot fire from ambiguous natural-language requests. Re-checking anchor 4 ('minor overlap risk') confirms this description is even more isolated than that, fitting anchor 5.

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