CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup

Run initial NanoClaw setup. Use when user wants to install NanoClaw, configure it, or go through first-time setup. Triggers on "setup", "install", "configure nanoclaw", or first-time setup requests.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 content is an exemplary lean skill body: one concrete command, a one-line summary of what the script covers, and a clear statement of the error-recovery path, with no padding or irrelevant explanation. Its only weakness is a small amount of missing detail around how the user locates/obtains nanoclaw.sh and what to do for partial or component-specific setup requests.

DimensionReasoningScore

Conciseness

The body is three lean sentences with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the anchor for lean, efficient content that assumes Claude's competence.

5 / 5

Actionability

It gives a concrete, executable command ("bash nanoclaw.sh") plus what the script covers, so the guidance is mostly copy-paste ready. Minor gaps keep it below anchor 5: the script's location/how the user obtains it is not stated, and there is no guidance for component-specific requests (e.g., reconfiguring just the credential).

4 / 5

Workflow Clarity

This is a simple single-action skill and the action is unambiguous: tell the user to run the script, which handles everything end-to-end. The error path is also addressed ("Claude-assisted recovery inline and resumes from where it stopped"), so the simple-skill exception for a 5 applies; nothing is incoherent or missing that would justify 4.

5 / 5

Progressive Disclosure

The body is well under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and no content that needs offloading to separate files. Per the small-skill guideline, a short, self-contained, well-organized body like this scores at the top of the scale.

5 / 5

Total

19

/

20

Passed

Description

66%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 follows the correct pattern: it states what the skill does and includes an explicit 'Use when' clause with a trigger list, all in third person and concisely. Its weaknesses are a minimal what (a single action with no scope detail) and generic trigger terms ("setup", "install") that create conflict risk with setup skills for other tools.

Suggestions

Expand the what clause to name the concrete setup steps (e.g., "Installs dependencies, builds the container image, configures the Anthropic credential and OneCLI vault, launches the service, and creates the first agent") to raise specificity.

Qualify the generic triggers to reduce conflict risk, e.g. "Triggers on 'setup', 'install', or 'configure nanoclaw' when the user mentions NanoClaw" rather than bare "install".

Add natural trigger variations such as "get started with NanoClaw" or "initialize NanoClaw" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Run initial NanoClaw setup" names the domain and a single action, but does not enumerate what the setup covers (dependencies, credentials, service, agents). This matches the anchor for naming the domain with 1-2 concrete actions without being comprehensive; it falls short of anchor 4, which expects several specific listed actions.

3 / 5

Completeness

Both halves are present: the what ("Run initial NanoClaw setup") and an explicit when ("Use when user wants to install NanoClaw, configure it, or go through first-time setup"), plus a concrete trigger list. The what is thin relative to anchor 5's example, which spells out multiple capabilities alongside concrete trigger phrases.

4 / 5

Trigger Term Quality

Triggers include natural phrases users would say: "setup", "install", "configure nanoclaw", "first-time setup". Coverage is good but misses common variations like "get started" or "initialize", matching the anchor for good keyword coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

While the NanoClaw name anchors it, the bare triggers "setup" and "install" are generic and would fire on setup/install requests for any tool, so overlap risk with other setup-type skills remains. This is somewhat specific but could still overlap, rather than anchor 4's "minor overlap risk with closely related skills".

3 / 5

Total

14

/

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

nanocoai/nanoclaw

Path

.claude/skills/setup/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.