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.

96

4.66x
Quality

83%

Does it follow best practices?

Impact

98%

4.66x

Average score across 11 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 well-structured, highly actionable body with concrete commands, quality-verification checkpoints, and fallback handling. Its only weaknesses are minor: a couple of trimmable concept-explanation sentences and inline template content that could be offloaded to reference files.

DimensionReasoningScore

Conciseness

Efficient overall — commands, thresholds, and examples are dense and useful — with only minor trimmable padding such as 'Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.' Fits anchor 4; not anchor 3 since unnecessary explanation is limited to a couple of sentences, not sections.

4 / 5

Actionability

Fully executable throughout: copy-paste commands ('npx skills find [query]', 'npx skills add <owner/repo@skill> -g -y') with flag explanations, worked search examples ('react performance', 'pr review', 'changelog'), concrete quality thresholds (1K+ installs, <100 stars), and ready-to-use response templates. Matches anchor 5.

5 / 5

Workflow Clarity

A clearly sequenced 6-step workflow with an explicit validation checkpoint (Step 4: 'Do not recommend a skill based solely on search results' with specific criteria) and a fallback error path ('When No Skills Are Found'). No destructive or batch operations, so no cap applies. Matches anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist and the body references none; the single file is well-sectioned with clear headers. At ~140 lines, content like the example-response templates and the category table could plausibly live in reference files — minor organization gaps matching anchor 4 rather than the fully split structure of anchor 5.

4 / 5

Total

18

/

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 strong description with an explicit what/when structure and natural quoted trigger phrases. Its main gaps are limited action coverage (only 'discover and install') and one overly broad trigger phrase that raises minor conflict risk.

Suggestions

Expand the action list to reflect the full workflow, e.g. 'Helps users discover, evaluate, and install agent skills' — this would lift specificity from 2 named actions to several.

Drop or qualify the trigger 'how do I do X' (e.g. 'how do I do X where X is a common task with an existing skill') to reduce firing on generic how-to questions.

Add common synonyms such as 'skill marketplace', 'install a skill', or 'extend agent capabilities' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('agent skills') and two concrete actions ('discover and install'), but stops short of the several specific actions (search, verify, update) the skill actually performs. Matches anchor 3 — not anchor 4, which requires a broader list of specific actions.

3 / 5

Completeness

Explicitly answers both: what ('discover and install agent skills') and when ('This skill should be used when the user is looking for functionality that might exist as an installable skill') with concrete quoted trigger phrases. Matches the anchor 5 pattern exactly.

5 / 5

Trigger Term Quality

Includes natural quoted phrases users would say ('how do I do X', 'find a skill for X', 'is there a skill that can...', 'extending capabilities'). Good coverage, but missing common synonyms like 'skill marketplace', 'install a skill', or 'plugin', so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (skill discovery/installation) with mostly distinct triggers, but the trigger 'how do I do X' is broad enough to fire on nearly any how-to question, creating more than the 'minimal conflict risk' of anchor 5. Not anchor 3 — the what-clause is specific and unlikely to collide with unrelated skills.

4 / 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
AIPentest/CyberStrikeAI
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.