CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

find-skills

Find and install agent skills when the user asks for a capability that may already exist as a skill.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/find-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 delivers an exceptionally actionable, well-sequenced workflow with explicit quality-verification and install-intent checkpoints and concrete tool-call examples throughout. Its only real weakness is redundancy: the anti-npx/git warning is stated three times and a tips section covers search basics Claude already knows.

Suggestions

State the "do not run npx skills add / git clone" rule once (in the tools section) and cut its two repetitions in Step 6, keeping only the unique detail about installing exactly one skill deterministically.

Delete or merge the "Tips for Effective Searches" section — advice like "use specific keywords" and "try alternative terms" assumes Claude lacks basic search judgment.

Consider moving the Common Skill Categories table into a reference file if the skill grows, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient step-by-step guidance, but the prohibition on shelling out to "npx skills"/"git" is repeated three times (tools intro and twice in Step 6), and the "Tips for Effective Searches" section explains basic search strategy Claude already knows. This matches anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened") better than anchor 4's "minor instances".

3 / 5

Actionability

Guidance is fully executable: exact tool calls with literal arguments (search_skills("react performance"), install_skill("claude-plugins:vercel-labs/agent-skills/skills/react-best-practices")), numeric quality thresholds (1K+ installs, <100 stars skepticism), and copy-paste-ready response templates covering common cases plus the no-results fallback.

5 / 5

Workflow Clarity

The six steps are clearly sequenced with explicit checkpoints: Step 4 verifies quality before recommending, and Step 6 gates installation on expressed user intent ("A search-only request must not mutate the skill library"). No destructive or batch operation is involved, so the validation cap does not apply; this matches anchor 5's "clear sequence with explicit validation steps".

5 / 5

Progressive Disclosure

This is a single-file skill (no references/, scripts/, or assets/ exist) with well-organized headers and a category table kept inline. At ~155 lines it exceeds the under-50-line simple-skill exception, and supplementary content like the category table and search tips remain inline, matching anchor 4 ("good structure; most content is appropriately placed; minor organization gaps") rather than anchor 5's appropriately-split profile.

4 / 5

Total

17

/

20

Passed

Description

70%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 cleanly answers both what the skill does and when to use it in third person with a reasonable set of natural trigger terms. Its main weaknesses are limited action coverage (two verbs) and an abstract rather than concrete trigger clause, which leave it just short of the top anchors.

Suggestions

Add concrete trigger phrases to the description, e.g. "Use when the user says 'find a skill', 'is there a skill for X', or asks for a capability that may already exist as a skill".

Mention the search/browse dimension explicitly (e.g., "Search the skills marketplace, verify quality, and install") to raise specificity from two actions to several.

Consider naming the ecosystem ("agent skills marketplace") to sharpen distinctiveness against skill-authoring skills.

DimensionReasoningScore

Specificity

"Find and install agent skills" names the domain plus exactly two concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage; it omits search, quality verification, and presentation facets that anchor 4's "several specific actions" would require.

3 / 5

Completeness

"Find and install agent skills" clearly answers what, and "when the user asks for a capability that may already exist as a skill" explicitly answers when; it falls short of anchor 5 because the trigger is one abstract phrase rather than concrete trigger phrases users would actually say.

4 / 5

Trigger Term Quality

Terms like "find", "install", "skills", and "capability" are natural phrases users would say when needing this skill, but common variations such as "search", "browse", or "plugin" are missing, matching anchor 4's "good keyword coverage; a few natural terms missing" rather than anchor 3's missing-synonyms profile.

4 / 5

Distinctiveness Conflict Risk

Skill discovery and installation is a distinct niche, but the broad term "capability" creates minor overlap risk with closely related skills such as skill authoring/creation, matching anchor 4 rather than anchor 5's "minimal conflict risk".

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

CherryHQ/cherry-studio

Path

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