CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

find

Use when you or the user are about to pick a tool, library, framework, CLI or app for a need, before naming one from memory, or when asked to find one.

Quality

70%

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/find/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 unusually tight, high-signal instruction set: lean to the point of telegraphic, with concrete sources, a checkable four-rule gate, and a fully specified output template. Its main defects are a broken external reference (author-gate.json is missing from the bundle, undermining the author gate and actionability), unspecified commands for two of the six sources, and an execution order that must be assembled from section layout.

Suggestions

Ship author-gate.json beside SKILL.md (with the establishedOwner and popularRepo entries rule 4 depends on) or inline its content, since the referenced file is absent from the bundle and the author gate cannot run as written.

Give concrete invocations for sources 3–4, e.g., the actual `gh api search/repositories?q=<need>` query and the npm/PyPI/crates.io lookup URLs, matching the specificity of the MCP and HN Algolia entries.

State the end-to-end sequence explicitly (skip check → search sources in order → gate each candidate on rules 1–4 → rank → output) and say what happens when a candidate fails (advance to the next candidate or source).

DimensionReasoningScore

Conciseness

The ~68-line body is relentlessly lean — every line is operative instruction ('Memory never fills in', 'Newness is no criterion: show age, never gate on it', the four-rule table, the output template), with zero explanation of concepts Claude already knows and no padding; it matches 'every token earns its place'. Not a 4 because no over-explained or trimmable passage was found.

5 / 5

Actionability

Mostly executable: concrete commands and URLs are given ('npx skills find <need>', the MCP registry URL, the HN Algolia URL, the read-only gh/curl constraints), the rules are checkable criteria, and the output block is a copy-paste template. It falls short of fully-executable because sources 3–4 ('GitHub through gh api', 'The npm, PyPI and crates.io registries') name no specific query command or URL, and the `author-gate.json` data the author check depends on is not in the bundle.

4 / 5

Workflow Clarity

A clear sequence exists in execution order (write memory pick → Skip check → Sources in order → four-rule gate with author check → Rank → Output) with explicit checkpoints ('Check all four before rejecting a candidate, and list every rule that fails', 'Check each name against its registry before naming it') and early exits ('say which and stop', 'say so and stop'). Not a 5 because the end-to-end order must be inferred from section layout rather than stated, and there is no instruction for what to do after a candidate fails the rules (move to the next candidate or source).

4 / 5

Progressive Disclosure

Sections are well organized for a single ~68-line file, but the body's only external reference — 'establishedOwner in author-gate.json, beside this file' — points to a file that does not exist in the bundle (no references/, scripts/, assets/, or author-gate.json anywhere), so the one reference it makes is broken and rule 4's (a)/(b) checks cannot be executed as written. Scored against the actual bundle structure per the guideline, this lands at 'some structure but could be better organized' rather than the 'minor organization gaps' of a 4, since the missing data file is more than a minor gap.

3 / 5

Total

16

/

20

Passed

Description

47%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 has strong, explicit trigger guidance with good natural keywords and a mostly distinct niche, but it is a 'when'-only description: it never says what the skill actually does, and it uses second-person voice, which the rubric penalizes. Scores concentrate at the middle-low band because capability specificity and the what-half of completeness are absent.

Suggestions

Lead with a third-person statement of what the skill does, e.g., 'Surfaces the current best tool for a need from sources fetched this run (registries, repos, web), with license, author, and evidence checks', so the description answers both 'what' and 'when'.

Rewrite the trigger clause in third person ('Use when the user is about to pick...') to remove the second-person 'you or the user' phrasing the rubric penalizes on specificity.

Add one or two concrete capability keywords (e.g., 'checks licenses and author reputation', 'ranks by manual work removed') and synonyms like 'choose' or 'recommend a library' to lift specificity and trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates the domain ("a tool, library, framework, CLI or app") and states the picking/finding operation, but names no concrete action the skill itself performs (no registry checks, license verification, or ranking), fitting the 'names the domain but actions are minimal or generic' anchor; the second-person phrasing "Use when you or the user are about to pick" additionally incurs the rubric's −1 voice penalty from an anchor fit of 3.

2 / 5

Completeness

Only the 'when' is present: the description is entirely trigger conditions ("Use when you or the user are about to pick... before naming one from memory, or when asked to find one") and never states what the skill does (e.g., surfaces the best-matching tool from freshly fetched sources with evidence), matching the anchor 'only when is present without what'. It is not a 3 because that anchor requires a clear 'what', and not a 1 because the 'when' is explicit and detailed.

2 / 5

Trigger Term Quality

Good natural keyword coverage — "pick a tool", "library", "framework", "CLI", "app", "asked to find one" — phrases a user would naturally say; common synonyms like "choose", "recommend", "which one should I use", or "package" are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The trigger carves a fairly distinct niche — choosing a tool/library/framework/CLI/app before naming one from memory — with minor overlap risk against closely related skills (generic web search, package installation, dependency management); it lacks the sharp 'clear niche with distinct triggers' character of a 5 because 'pick a tool... for a need' spans many domains.

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