skill-finder

This skill should be used when the user asks to "find a skill", "discover plugins", "search for an MCP", "what plugins exist for X", "fill my skill gaps", "improve my setup", or when Claude recognizes it lacks tools for a task. Searches GitHub and marketplaces to suggest installations.

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skill-management/skills/skill-finder/SKILL.md

Quality

Discovery

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 description excels at trigger term coverage and completeness, providing numerous natural phrases users would say and clearly stating both what the skill does and when to use it. Its main weakness is that the 'what it does' portion is somewhat thin — 'Searches GitHub and marketplaces to suggest installations' could be more specific about the concrete actions performed (e.g., comparing options, checking compatibility, providing install commands).

Suggestions

Expand the capability description with more specific actions, e.g., 'Searches GitHub repositories and plugin marketplaces, compares options, checks compatibility, and provides installation instructions.'

Dimension	Reasoning	Score
Specificity	The description mentions 'Searches GitHub and marketplaces to suggest installations' which names the domain and a general action, but doesn't list specific concrete actions like 'search repositories', 'compare plugins', 'install skills', or 'analyze compatibility'.	2 / 3
Completeness	Clearly answers both 'what' (searches GitHub and marketplaces to suggest installations) and 'when' (explicit trigger phrases listed, plus the meta-trigger of Claude recognizing it lacks tools for a task). The 'Use when' equivalent is front-loaded with specific trigger scenarios.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'find a skill', 'discover plugins', 'search for an MCP', 'what plugins exist for X', 'fill my skill gaps', 'improve my setup'. These are phrases users would naturally say when looking for this functionality.	3 / 3
Distinctiveness Conflict Risk	This skill occupies a clear niche — skill/plugin discovery and installation suggestion. The trigger terms like 'find a skill', 'discover plugins', 'search for an MCP', and 'fill my skill gaps' are highly specific and unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

27%

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

This skill is far too verbose for its purpose, repeating search patterns and templates across multiple sections and explaining concepts Claude already understands (GitHub stars, npm, repository evaluation). While it has a reasonable logical structure and some actionable install commands, the sheer volume (~350+ lines) undermines usability. The content would benefit enormously from being split into a concise overview with references to detailed sub-files for search templates, MCP discovery, and gap categories.

Suggestions

Reduce to ~80-100 lines by eliminating redundant search query sections (currently repeated 3-4 times), removing obvious quality signal explanations, and cutting the common gap categories tables into a separate reference file.

Remove tables explaining what GitHub stars mean, what 'archived' means, and other concepts Claude already knows — focus only on the decision thresholds (e.g., '>100 stars = recommend').

Split into SKILL.md (core workflow + triggers + result format) with references to SEARCH_TEMPLATES.md, GAP_CATEGORIES.md, and MCP_DISCOVERY.md for the detailed lookup tables.

Add a concrete validation step after installation (e.g., 'Verify install: run claude mcp list and confirm [name] appears') to close the feedback loop on the workflow.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Contains massive amounts of redundant tables, repeated search query templates across multiple sections, and information Claude already knows (how to evaluate GitHub repos, what stars mean, how npm works). The same search patterns are restated 3-4 times in different formats. The quality/warning signals tables explain obvious concepts.	1 / 3
Actionability	Provides concrete search query templates and install commands, but much of the guidance is templated placeholders rather than truly executable examples. The search queries are text patterns rather than actual tool invocations, and many install commands reference fictional tools/marketplaces (e.g., 'claude plugins add' doesn't exist). The MCP configuration JSON is a useful concrete example.	2 / 3
Workflow Clarity	Has a clear multi-step framework (analyze gaps → identify category → search → evaluate → present), but lacks validation checkpoints. There's no verification step after installation to confirm the plugin works, no error handling for failed installs, and no feedback loop if search results are poor. The 'Verify Compatibility' step is listed but has no concrete validation commands.	2 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files. Everything is inline — the common gap categories tables, MCP discovery details, marketplace priority, quality signals, and post-discovery actions could all be separate reference files. The skill tries to be comprehensive in a single file, resulting in overwhelming length that defeats its purpose as a quick-reference skill.	1 / 3
	Total	6 / 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: back1ply/LLM-Skills
Commit: b573078

Reviewed: 14 days 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.