CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

acquiring-skills

Discover and install skills from Hermes, ClawHub, GitHub, and other registries. Load this skill whenever a user asks for a capability you don't already have — image generation, social media, email, calendar, finance, DevOps, search, browser automation, etc.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A highly actionable, well-structured skill with concrete executable commands for every source and sensible safety gates, resulting in strong workflow clarity. The main costs are token efficiency — duplicated source lists and two near-identical worked examples — and missed opportunities to move per-registry detail into separate reference files.

Suggestions

Consolidate the two 'Complete Example' walkthroughs into one, or compress the second to a one-line variant showing only the ClawHub install command — the ask/review/invoke steps are already demonstrated.

Deduplicate the trusted-source repositories: list them once (in SAFETY or section 4) and cross-reference from the other spot.

Add a brief error-recovery note for the install workflow (e.g., slug not found, prefix required for ClawHub, retry with `--force` on name collision) to close the validation gap.

Move the Hermes hub source table and per-registry search detail into a references file (e.g., references/registries.md) to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly commands and specifics, but contains real redundancy: the trusted-source repos are listed in the SAFETY section and again in section 4, and two structurally identical "Complete Example" walkthroughs repeat the same ask/install/review steps. It could be tightened into one example without losing information, matching 'mostly efficient but could be tightened' rather than the leaner 4.

3 / 5

Actionability

Guidance is copy-paste ready throughout: concrete search commands (`hermes skills search <query>`, `clawhub search "calendar"`, `curl -s "https://clawhub.ai/api/v1/skills?q=calendar"`), all install forms with prefixes and version pinning, a flags table, and manual-install commands. These cover the common cases fully.

5 / 5

Workflow Clarity

The Search Strategy gives an ordered 1-4 sequence and the worked examples lay out a clear 6-step flow with checkpoints (ask user, `hermes skills inspect` before installing, read SKILL.md for compatibility before invoking). It is not a 5 because there is no error-recovery guidance (e.g., what to do when an install fails or a slug does not resolve), only the one footnote about the bare-slug ClawHub case.

4 / 5

Progressive Disclosure

The single SKILL.md is well organized with clear section headers (Safety, Sources, CLI reference, Locations, Search Strategy, Examples) and no nested or buried references. It falls short of 5 because at ~280 lines the per-source detail (Hermes hub source table, ClawHub specifics) would benefit from being split into one-level-deep reference files.

4 / 5

Total

16

/

20

Passed

Description

83%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.

A strong description that clearly states what the skill does and gives an explicit, trigger-rich 'when to load' clause with natural capability keywords. The main weaknesses are limited action specificity beyond discover/install and a somewhat broad trigger condition with minor overlap risk.

DimensionReasoningScore

Specificity

The description names two concrete actions ("Discover and install skills") and enumerates specific sources ("Hermes, ClawHub, GitHub, and other registries"), going beyond a bare domain statement. It falls short of a 5 because the action list is limited to discover/install with no further operational specifics.

4 / 5

Completeness

It explicitly answers both questions: what ("Discover and install skills from Hermes, ClawHub, GitHub, and other registries") and when ("Load this skill whenever a user asks for a capability you don't already have") with concrete trigger examples. This matches the anchor for a clear what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered — "image generation, social media, email, calendar, finance, DevOps, search, browser automation" are terms users would actually say when lacking a capability. A few natural variants (e.g., "add a skill", "plugins", "extend capabilities") are missing, so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

Skill discovery/installation from external registries is a clear niche with distinct triggers, but the broad trigger "a capability you don't already have" could overlap with general skill-management or search skills, leaving minor conflict risk rather than minimal.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

letta-ai/letta-code

Path

src/skills/builtin/acquiring-skills/SKILL.md

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.