CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stack

Find a tool for each step this project still does by hand, and write the picks into CLAUDE.md under `## Tools` for you to review in the diff.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./sound/skills/stack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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, well-structured instruction skill: it defines an unambiguous workflow, constrains blast radius (edit only CLAUDE.md, install nothing), and specifies the output format precisely. Its only weaknesses are a couple of underspecified inputs and the absence of a worked example of a completed pick line.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — every line instructs ('Edit nothing except...', 'Write your own pick... before any search', 'Run `sound:find` once per gap') and it explains nothing Claude already knows, matching the every-token-earns-its-place anchor.

5 / 5

Actionability

Guidance is mostly executable: an exact output-line template, a concrete parallel-subagent procedure, and an explicit read-only-first-command safety rule ('never `npx` or `curl | sh`'); it falls short of 5 only for lacking a worked example of a filled-in pick line and for slightly vague inputs like 'the goals in the instruction files'.

4 / 5

Workflow Clarity

The sequence (Gaps → Picks → Write → Chat) is clear with an explicit review checkpoint ('for you to review in the diff') and a closing settled/open summary; the write target is non-destructive (CLAUDE.md only), so no destructive cap applies, but intermediate checkpoints like reconciling memory picks with found tools are only implied by the Chat section, fitting the minor-validation-gaps anchor.

4 / 5

Progressive Disclosure

At ~38 lines with no external references needed and well-organized sections (Gaps, Picks, Write, Chat), this meets the under-50-line simple-skill exception for scoring 5 on well-organized structure alone.

5 / 5

Total

18

/

20

Passed

Description

46%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 communicates a concrete, distinctive task but reads like an instruction to the agent rather than a discovery description. It completely lacks 'when to use' trigger guidance and natural trigger terms, and uses second person ('for you to review'), which limits discovery effectiveness.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user asks to automate manual steps, find tools for recurring chores, or modernize the project's workflow').

Include natural keyword variations users would say, such as 'manual steps', 'automate', 'tooling gaps', and 'CLAUDE.md', to improve trigger matching.

Rewrite in third person and drop the second-person 'for you to review' phrasing (e.g., '...writes the picks into CLAUDE.md under `## Tools` for review in the diff').

DimensionReasoningScore

Specificity

The description lists concrete actions ('Find a tool for each step this project still does by hand', 'write the picks into CLAUDE.md under `## Tools`', 'review in the diff'), which matches the several-specific-actions anchor (4), but the second-person phrase 'for you to review' triggers the mandated 1-point penalty, landing at 3.

3 / 5

Completeness

The 'what' is clear and specific (find tools for manual steps, write picks into CLAUDE.md), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Only generic keywords appear ('tool', 'by hand', 'CLAUDE.md', 'diff') with no natural trigger phrases a user would actually say when needing this skill, matching the one-or-two-generic-keywords anchor.

2 / 5

Distinctiveness Conflict Risk

The niche is distinct — tool discovery for manually-performed project steps recorded in CLAUDE.md — with only minor overlap risk against other tooling/discovery skills, fitting the 'mostly distinct' anchor; it lacks the crisp trigger phrasing of a 5.

4 / 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

saadshahd/moo.md

Path

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