CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup

Use when installing or refreshing sound taste rules in a project — an explicit "sound setup", starting work in a repo with no .claude/sound/, or a taste-not-defined nudge. Also use to re-run after a stack change (new framework, new package in a monorepo).

Quality

83%

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

85%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 disciplined operational spec: four sequenced phases, explicit validation gates ('No citation, no install', corpus-missing STOP), a failure-mode checklist, and copy-paste-ready hook wiring for five hook managers. Its main defect is progressive disclosure — the two referenced branch files are absent from the bundle, so propose-only mode and re-runs cannot actually be executed as shipped — with minor repetition of the no-tag-pre-filter rule keeping conciseness just short of lean.

Suggestions

Ship propose-only.md and re-runs.md inside the skill bundle (e.g., references/) or state their exact location relative to SKILL.md — both are named as required reading for whole modes of operation but do not exist in the bundle, so Phase 3's propose-only branch and the Re-runs branch dead-end.

Consolidate the three statements of the no-tag-pre-filter rule ('never a tag-wide dump', 'There is no tag pre-filter', 'A fired tag earns NOTHING by itself') into one canonical statement plus the Redis example to trim redundant tokens.

State where the corpus's Detect:/Not-when: rule format is documented or include one short example rule, since selection correctness hinges on a file format the skill only describes secondhand.

DimensionReasoningScore

Conciseness

Quotes: "probe the stack, select ONLY rules whose subject the repo's code actually shows — evidence-cited per rule, never a tag-wide dump — confirm with the user, then install each confirmed rule's corpus prose verbatim" — the body is lean with zero padding and no explanations of concepts Claude already knows. It falls short of anchor 5 because the no-tag-pre-filter rule is stated three times ("never a tag-wide dump", "There is no tag pre-filter", "A fired tag earns NOTHING by itself") and several triple-clause sentences could be tightened; it is above anchor 3 because every repetition carries new operational nuance rather than filler.

4 / 5

Actionability

Quotes: "pre-commit: commands: <rule-name>: run: <gate>", "a `<gate>` line in `.husky/pre-commit`", "`.tsx`/`.jsx` files, JSX or react imports in real source", "`.publish(`, `.send(`, `.create(`…", ".claude/sound/<topic>/<rule-name>.md" — exact paths, copy-paste-ready wiring per hook tool, concrete detection cues, and worked judgment examples (next-auth EmailProvider as email-sending, redis-as-cache vs. store, sqlite as embedded db). Fully executable for an instruction-only skill, so no code-absence penalty applies.

5 / 5

Workflow Clarity

Quotes: "Phase 1 — Probe" through "Phase 4 — Write" give a named, ordered sequence; validation is explicit ("If `corpus/` is missing or unreadable, STOP and say so", "No citation, no install"); error recovery is a feedback loop ("a corrected set replaces yours without argument; redo the affected phases"), and "Failure modes to keep loud" is a five-entry checklist with prescribed responses. This matches anchor 5: clear sequence, explicit validation steps, feedback loops, and a checklist.

5 / 5

Progressive Disclosure

Quotes: "read `propose-only.md` and follow it instead of confirming or writing", "read `re-runs.md` before writing anything" — the deferral strategy is right (conditional branches externalized, one level deep, clearly signaled at point of use), but neither referenced file exists in the bundle (no references/, scripts/, or assets/ directories, no sibling files), so both references dead-end as shipped. Not anchor 4 because broken references are more than a minor organization gap; not anchor 2 because nothing that belongs in separate files is inlined and the signaling is clear.

3 / 5

Total

17

/

20

Passed

Description

73%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's trigger guidance is its strength: an explicit 'Use when…' clause with several concrete, natural triggers (explicit 'sound setup', a repo lacking .claude/sound/, a stack change) and a highly distinctive niche that makes misfiring unlikely. Its weakness is an underspecified 'what' — 'installing or refreshing sound taste rules' is the only capability stated, leaving the probe/select/confirm/write pipeline the body defines implicit.

Suggestions

Name one or two more concrete operations in the description (e.g., 'probes the stack, selects evidence-cited rules, writes them to .claude/sound/') so the 'what' reflects the skill's actual scope, not just its bookends.

Add a user-natural synonym or two for the trigger (e.g., 'set up taste rules', 'add sound rules') alongside ecosystem terms like 'taste-not-defined nudge'.

DimensionReasoningScore

Specificity

Quotes: "installing or refreshing sound taste rules in a project", "re-run after a stack change" — the domain (sound taste rules) and 1–2 concrete actions (install, refresh/re-run) are named, but the body's other concrete operations (stack probing, evidence-cited rule selection, writing to .claude/sound/, pre-commit gate wiring) are absent. Matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); not 4 because several specific actions are missing, not 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

Both parts are present: what = "installing or refreshing sound taste rules in a project"; when = an explicit "Use when…" clause plus "Also use to re-run after a stack change" with concrete triggers. Not anchor 5 because the 'what' is thin — where the rules land and what the install involves (probe, select, confirm, write) stay implicit; not 3 because the when is explicit and concrete, well above 'weakly implied'.

4 / 5

Trigger Term Quality

Quotes: "an explicit \"sound setup\"", "starting work in a repo with no .claude/sound/", "a taste-not-defined nudge", "new framework, new package in a monorepo" — good natural trigger coverage with several concrete variants users would actually say. Not anchor 5 because 'taste-not-defined nudge' is an ecosystem-internal term rather than a user-spoken phrase and common synonyms ('set up taste rules', 'add sound rules') are missing; not 3 because multiple natural phrasings and conditions are covered.

4 / 5

Distinctiveness Conflict Risk

Quotes: "sound setup", ".claude/sound/", "sound taste rules" — a clear niche with distinct, proprietary trigger phrases that no other skill category would claim; conflict risk is minimal, matching anchor 5 exactly.

5 / 5

Total

16

/

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

saadshahd/moo.md

Path

sound/skills/setup/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.