Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit CLI. Supports browsing official partner collections (Anthropic, Vercel, Supabase, Stripe, and more) and community repositories, searching by domain or technology, and installing specific skills from GitHub. Use when the user wants to find, browse, or install new agent skills, plugins, extensions, or add-ons; asks 'is there a skill for X' or 'find a skill for X'; wants to explore a skill store or marketplace; needs to extend agent capabilities in areas like React, testing, DevOps, security, or APIs; or says 'browse skills', 'search skill marketplace', 'install a skill', or 'what skills are available'.
85
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 an excellent skill description that thoroughly covers what the skill does, when to use it, and includes rich trigger terms. It names specific actions, tools (SkillKit CLI), partners, and provides multiple natural-language trigger phrases. The description is comprehensive without being padded, and occupies a clear, distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: discovers, searches, installs skills; browsing official partner collections (with named partners); searching by domain or technology; installing from GitHub. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (discovers, searches, installs skills from marketplaces using SkillKit CLI, supports browsing collections and repositories) and 'when' with an explicit 'Use when...' clause listing multiple specific trigger scenarios and exact phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'find a skill for X', 'is there a skill for X', 'browse skills', 'search skill marketplace', 'install a skill', 'what skills are available', plus synonyms like 'plugins', 'extensions', 'add-ons'. Also includes domain examples like React, testing, DevOps. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on skill marketplace discovery and installation via SkillKit CLI. The specific mention of skill marketplaces, partner collections, and CLI tooling makes it highly distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with concrete CLI commands and good use of tables for reference data. Its main weaknesses are the lack of validation/error-handling steps in the workflow (what happens when install fails or a skill isn't found?) and some verbosity in sections that coach Claude on interaction patterns it already understands. The content would benefit from trimming the 'How to Help Users' section and adding error recovery guidance.
Suggestions
Add validation steps after installation (e.g., run `npx skillkit@latest list` to confirm the skill installed, handle common error messages like network failures or invalid repo paths).
Trim or remove the 'How to Help Users' step-by-step section — Claude already knows how to understand user needs and present results; replace with just the key decision points or edge cases.
Move the Official Partners and Community Collections tables to a separate SOURCES.md reference file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but includes some unnecessary sections like 'How to Help Users' which walks Claude through a basic interaction pattern it already knows (understand need → search → present → install). The 'Common Searches' table is somewhat redundant given the search command is already shown. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout. Every CLI command is concrete with real arguments, the install commands use actual repository paths, and the --skills flag usage is clearly demonstrated with specific examples. | 3 / 3 |
Workflow Clarity | The 4-step 'How to Help Users' workflow is clearly sequenced, but lacks validation checkpoints — there's no guidance on verifying a skill installed correctly, handling installation failures, or confirming the skill is functional after install. For operations that modify the user's environment, this is a gap. | 2 / 3 |
Progressive Disclosure | Content is reasonably well-organized with clear sections and tables, but everything is inline in a single file that runs fairly long. The official partners and community collections tables could be in a separate reference file. No bundle files are provided, so there's no progressive structure to leverage. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
a9e5c83
Table of Contents
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.