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.

7.16x

Quality

66%

Does it follow best practices?

Impact

86%

7.16x

Average score across 8 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/find-skills/SKILL.md

Quality

Content

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides genuinely actionable guidance with concrete commands and realistic examples, which is its strongest aspect. However, it is significantly over-explained for its target audience (Claude), with verbose sections that describe concepts and workflows that could be conveyed in a fraction of the tokens. The content would benefit from aggressive trimming and better structural organization.

Suggestions

Cut the 'When to Use This Skill' and 'What is the Skills CLI?' sections down to 2-3 lines total — Claude doesn't need detailed trigger conditions or explanations of what a package manager is.

Collapse the 4-step workflow into a concise decision tree: search → present results with install command → handle no-results case. Remove the verbose example responses.

Move the categories table and search tips to a separate reference file or remove them entirely — Claude can infer appropriate search terms from user queries.

Add a post-install verification step (e.g., confirming the skill appears in the installed list) to strengthen the workflow.

Dimension	Reasoning	Score
Conciseness	Significant verbosity throughout. The 'When to Use This Skill' section explains triggering conditions Claude can infer. 'What is the Skills CLI?' explains package manager concepts Claude already knows. The 'How to Help Users Find Skills' section over-explains a simple search-present-install workflow with excessive example responses and step-by-step hand-holding. The common categories table and tips section add bulk without proportional value.	1 / 3
Actionability	Provides fully executable commands (`npx skills find [query]`, `npx skills add <owner/repo@skill> -g -y`), concrete examples mapping user requests to search queries, and realistic output examples. The commands are copy-paste ready with clear flag explanations.	3 / 3
Workflow Clarity	The 4-step workflow (understand → search → present → install) is clearly sequenced, but there's no validation checkpoint after installation (e.g., verifying the skill was installed correctly, testing it works). The 'When No Skills Are Found' fallback is a nice touch, but the main happy path lacks verification steps.	2 / 3
Progressive Disclosure	Monolithic wall of text with no bundle files or references to external documents. All content is inline including the categories table, tips, and example responses that could be separated. For a skill of this length (~100 lines of substantive content), the lack of any structural separation is a weakness.	1 / 3
	Total	7 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description with excellent trigger terms and clear 'when to use' guidance. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., searching a skill registry, listing available skills, running installation commands). The description effectively carves out a distinct niche that won't conflict with other skills.

Suggestions

Add more specific concrete actions like 'searches skill registries, lists available skills, compares options, and runs installation commands' to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (discovering and installing agent skills) and some actions (discover, install), but doesn't list specific concrete actions like searching a registry, listing available skills, comparing skills, or configuring installed skills.	2 / 3
Completeness	Clearly answers both 'what' (helps users discover and install agent skills) and 'when' (when users ask questions like 'how do I do X', 'find a skill for X', or express interest in extending capabilities). Explicit trigger guidance is provided.	3 / 3
Trigger Term Quality	Includes strong natural trigger phrases users would actually say: 'how do I do X', 'find a skill for X', 'is there a skill that can...', 'extending capabilities', 'install'. These closely match real user language patterns.	3 / 3
Distinctiveness Conflict Risk	This skill has a very clear niche — skill discovery and installation — that is unlikely to conflict with other skills. The trigger terms are specific to meta-level capability extension rather than any particular task domain.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: tibelf/ai_project_init
Commit: 56f4516

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

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.