Search and install agent skills from ClawHub, the public skill registry.
54
63%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./nanobot/skills/clawhub/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear and distinctive niche (ClawHub skill registry) with two concrete actions, but it lacks a 'Use when...' clause and could benefit from more natural trigger terms users might say. Its distinctiveness is its strongest quality due to the unique ClawHub identifier.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to find, browse, or install new agent skills, or mentions ClawHub, skill registry, or adding capabilities.'
Include more natural trigger term variations such as 'find skills', 'add skill', 'browse skills', 'plugin', 'marketplace', or 'download skill'.
Expand the capability list slightly, e.g., 'Search, browse, and install agent skills from ClawHub, the public skill registry. Lists available skills, shows details, and manages installation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (agent skills from ClawHub) and two actions (search and install), but doesn't elaborate on additional capabilities like browsing, filtering, updating, or managing installed skills. | 2 / 3 |
Completeness | Describes what it does (search and install skills from ClawHub) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'skills', 'ClawHub', 'install', and 'skill registry', but misses common user variations like 'find skills', 'add skill', 'plugin', 'marketplace', 'browse skills', or 'download skill'. | 2 / 3 |
Distinctiveness Conflict Risk | ClawHub is a very specific and unique proper noun, and the concept of searching/installing skills from a public registry is a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides fully actionable commands for all ClawHub operations. Its main weakness is the lack of an explicit end-to-end workflow sequence with validation (e.g., confirming installation succeeded before advising a session restart). The notes section adds genuinely useful non-obvious details like the critical --workdir flag.
Suggestions
Add a brief end-to-end workflow sequence (e.g., '1. Search → 2. Install → 3. Verify with `list` → 4. Remind user to restart session') to make the typical usage flow explicit and include a validation checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what a registry is or how npx works. The notes section contains only non-obvious, critical information (like the --workdir requirement and session restart reminder). | 3 / 3 |
Actionability | All four operations (search, install, update, list) have complete, copy-paste-ready commands. The placeholder `<slug>` is clearly explained. The --workdir flag is specified in every command where needed. | 3 / 3 |
Workflow Clarity | The individual commands are clear, but the typical workflow (search → install → remind user to restart) is not explicitly sequenced as a numbered flow. There's no validation step to confirm a skill was installed correctly before telling the user to restart. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines. The content is well-organized into clearly labeled sections (Search, Install, Update, List, Notes) with no need for external references. Navigation is straightforward. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
ab9f499
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.