CtrlK
BlogDocsLog inGet started
Tessl Logo

learn

Distill a reusable skill from anything — a directory, a URL, pasted notes, or what you just did together — or refine an existing skill with new learnings. Use when the user says '/learn', 'learn this', 'turn this into a skill', 'capture this workflow', 'make a skill from <source>', or 'improve/update the <name> skill'. Produces or updates a .claude/skills/<name>/SKILL.md authored to NanoClaw's skill guidelines. (This CREATES or REFINES a skill from a source; it does not install existing skills from a registry.)

80

Quality

100%

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

100%Weight 40%Scale 1-3

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

A well-structured, instruction-only meta-skill: lean prose, concrete tool- and path-level guidance, a sequenced five-step workflow with a verify step, and tidy single-file organization. It avoids explaining concepts Claude already knows and provides a copy-paste frontmatter template plus a worked example.

DimensionReasoningScore

Conciseness

The body is lean and procedural — it never explains basics Claude already knows (e.g. what a skill or a directory is) and each section earns its tokens; the only mild redundancy is the opening paragraph restating the description, which does not rise to verbosity.

3 / 3

Actionability

Names exact tools to use ("Glob the structure", "Read the key files", "Grep for the important entry points", "WebFetch the page"), gives concrete file paths (`.claude/skills/<kebab-name>/SKILL.md`), ships a copy-paste frontmatter template, and lists specific house rules — actionable guidance that is not penalized for lacking code as an instruction-only skill.

3 / 3

Workflow Clarity

A clearly numbered five-step workflow (identify source → gather → distill → author → place/verify) with an explicit decision branch (refine vs. new) and validation in step 5 ("confirm the folder name matches the name frontmatter and the YAML parses"; dry-run the procedure).

3 / 3

Progressive Disclosure

No bundle files are present, so the single self-contained SKILL.md is judged on organization; it is cleanly split into When to use, Workflow, Example, and Notes with one inline pointer to docs/skill-guidelines.md and no nested reference chains.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that states concrete capabilities, surfaces natural trigger phrases, and explicitly disambiguates creation/refinement from skill installation. Voice is correctly third person with no first/second-person slip, and it answers both what and when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Distill a reusable skill from anything — a directory, a URL, pasted notes", "refine an existing skill", and "Produces or updates a .claude/skills/<name>/SKILL.md" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (distill/refine a skill into SKILL.md) and when ("Use when the user says…"), with an explicit trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Cites natural phrases a user would actually say — "/learn", "learn this", "turn this into a skill", "capture this workflow", "make a skill from <source>", "improve/update the <name> skill" — giving broad coverage of likely triggers.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche and actively prevents mis-triggering via "This CREATES or REFINES a skill from a source; it does not install existing skills from a registry," making conflict with an install/registry skill unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nanocoai/nanoclaw
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.