CtrlK
BlogDocsLog inGet started
Tessl Logo

find-skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

61

Quality

73%

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

67%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.

A genuinely actionable, well-sequenced skill body with concrete tool usage and appropriate security validation around a risky install operation. The main weakness is mild verbosity in the auxiliary categories/tips sections that could be trimmed or omitted.

Suggestions

Trim or remove the "Common Skill Categories" table and "Tips for Effective Searches" section; their examples are largely derivable from the search workflow and add token cost without proportional guidance.

Add a brief recovery note for when install_skill fails (e.g., expired source, network error) to close the validation feedback loop.

Tighten the security block in Step 6 — the "would install the whole repo, scatter symlinks" rationale can be shortened to a single clause without losing the prohibition.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete tool calls and examples, but the "Common Skill Categories" table and "Tips for Effective Searches" sections pad the body without adding proportionate value.

3 / 5

Actionability

Provides concrete, near-copy-paste tool calls (e.g. search_skills("react performance"), install_skill("claude-plugins:vercel-labs/agent-skills/skills/react-best-practices")) with query-to-call mappings and a response template; minor gap is the opaque install_source value.

4 / 5

Workflow Clarity

Clear six-step sequence (understand → leaderboard → search → verify → present → install) with explicit checkpoints for quality verification and a security/intent gate before the risky install; lacks an explicit install-failure recovery loop.

4 / 5

Progressive Disclosure

Single self-contained file (no bundle files present) with well-organized sections and clear headers; content is appropriately placed, though slightly long for one file with no offloaded detail.

4 / 5

Total

15

/

20

Passed

Description

78%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.

A well-crafted description that clearly answers both what and when, using natural third-person voice and genuine user-facing trigger phrases. Specificity is the only soft spot — it names just two actions rather than a fuller inventory.

DimensionReasoningScore

Specificity

Names the domain (agent skills) and two concrete actions — "discover and install" — but stops there; not the several specific actions needed for a 4.

3 / 5

Completeness

Explicitly states what it does ("discover and install agent skills") and when to use it ("This skill should be used when the user is looking for functionality that might exist as an installable skill") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes several natural phrases users actually say ("how do I do X", "find a skill for X", "is there a skill that can...", "extending capabilities"); strong coverage, just shy of comprehensive synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (skill discovery/installation) with distinct triggers, but "how do I do X" is generic enough to create minor overlap with other skills.

4 / 5

Total

16

/

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.

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