CtrlK
BlogDocsLog inGet started
Tessl Logo

clawhub

Search and install agent skills from ClawHub, the public skill registry.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./nanobot/skills/clawhub/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

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

The body is an exemplary lean skill page: fully executable commands for every operation, no token waste on concepts Claude already knows, and well-organized sections that surface non-obvious operational pitfalls. The only gap is the absence of a post-install verification step.

DimensionReasoningScore

Conciseness

The body is lean — every section is a command block or an operational fact Claude could not infer (the --workdir pitfall, the new-session requirement, login being publish-only). It matches 'Lean and efficient; assumes Claude's competence; every token earns its place' with no padded or redundant explanation.

5 / 5

Actionability

Every operation (search, install, update, list) has a fully executable, copy-paste-ready command with the critical --workdir flag included, and the <slug> placeholder is explained with a pointer to search results. This matches 'Fully executable; copy-paste ready code or commands' covering all common cases.

5 / 5

Workflow Clarity

The flow is clearly sequenced (search, then install using the slug from results, then remind the user to start a new session) and even flags the failure mode of omitting --workdir. It falls short of 5 because there is no post-install verification step (e.g., running list to confirm the skill landed), leaving a minor validation gap rather than an explicit checkpoint.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose around one CLI, requires no external references, and is organized into clearly headed sections (When to use, Search, Install, Update, List installed, Notes). Per the rubric's simple-skill exception, this earns a 5 for well-organized sections without external file references.

5 / 5

Total

19

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 states a clear, specific capability against a distinct niche, but it omits any trigger guidance and misses natural user phrasings and several of the skill's actual operations. Adding a 'Use when...' clause with concrete user phrases would lift completeness and trigger-term quality substantially.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. "Use when the user asks to find, search, install, update, or list agent skills".

Include natural user phrasings such as "find a skill", "browse skills", or "add a skill" that users would actually say.

Mention the other supported operations (update, list) so the 'what' covers the skill's actual capability set.

DimensionReasoningScore

Specificity

"Search and install agent skills from ClawHub" names the domain and two concrete actions, but stops there — update, list, and publish operations from the body are omitted, matching 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because coverage of the skill's actual capabilities has more than minor gaps.

3 / 5

Completeness

The description has a clear 'what' ("Search and install agent skills from ClawHub, the public skill registry") but no 'Use when...' or equivalent trigger guidance at all, which per the judging guidelines caps completeness at 3. It fits anchor 3 exactly; it cannot be 4 since 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

"Search", "install", and "skills" are relevant keywords, but natural user phrasings like "find a skill" or "browse available skills" and common synonyms are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Not a 4 because a few clearly natural terms are absent.

3 / 5

Distinctiveness Conflict Risk

Naming a specific registry ("ClawHub, the public skill registry") establishes a clear niche that is unlikely to trigger for unrelated skills, with only minor overlap risk against other skill-marketplace or plugin-registry skills. It falls just short of 5 because "search and install skills" alone, without the registry qualifier, could collide with similar package-manager skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
HKUDS/nanobot
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.