clawhub
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 is concise and identifies a clear niche (ClawHub skill registry), making it distinctive. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and could benefit from more trigger terms that users would naturally use when looking for new skills or plugins.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to find, browse, or install new agent skills, or mentions ClawHub, skill registry, or adding capabilities.'
Include additional natural trigger terms like 'find skills', 'add skill', 'browse plugins', 'download skill', 'skill marketplace' to improve matching.
Consider listing more specific actions beyond search and install, such as 'browse categories', 'view skill details', or 'manage installed skills'.
| 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 completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'when' is entirely missing so it scores 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'skills', 'install', 'ClawHub', and 'skill registry', but misses common user variations like 'find skills', 'add skill', 'browse skills', 'plugin', 'marketplace', or 'download skill'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'ClawHub' as a specific named registry and the focus on skill installation creates a very clear niche that is 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 a verification step (e.g., running `list` after `install` to confirm success). Overall it's a strong skill that respects token budget while delivering clear, executable guidance.
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.
Include a validation checkpoint after install, such as running `clawhub list` to confirm the skill appears in the workspace.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what a registry is or how npx works. The 'When to use' section is tight and useful for trigger matching. Notes are all actionable gotchas rather than filler. | 3 / 3 |
Actionability | All four operations (search, install, update, list) have complete, copy-paste-ready commands with correct flags. The `<slug>` placeholder is clearly explained, and the critical `--workdir` flag is emphasized. | 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 (e.g., checking the list after install). | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized into clearly labeled sections (Search, Install, Update, List, Notes) that are easy to scan. | 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 | |
- Repository
- HKUDS/nanobot
- Commit
2666582
- 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.