update-nanoclaw

Efficiently bring upstream NanoClaw updates into a customized install, with preview, selective cherry-pick, and low token usage.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/update-nanoclaw/SKILL.md

Quality

Content

77%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 highly actionable with a clearly sequenced, well-validated workflow, but it is held back by overview/detail duplication and a referenced diagnostics file that does not exist in the bundle.

Suggestions

Collapse the 'How it works' overview into the Step 0–8 detail (or move it to a separate reference) to remove the restated buckets and rollback lines.

Either ship the referenced .claude/skills/update-nanoclaw/diagnostics.md in the bundle or remove the Diagnostics pointer so navigation is not dead-ended.

Move the breaking-change parsing format and AskUserQuestion option specs into a referenced file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	It assumes Claude's git knowledge (no padding about what git is) but duplicates content — the 'How it works' overview restates the Steps 0–8 flow, and file buckets/rollback are repeated — so it could be tightened, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Fully executable throughout: concrete git commands, a chained dry-run command, explicit AskUserQuestion option lists, and copy-paste rollback instructions covering the common cases.	5 / 5
Workflow Clarity	A clear Step 0–8 sequence with explicit validation checkpoints (dirty-tree preflight, dry-run conflict preview, npm build/test) and feedback loops (rebase abort after 3 rounds, build-fail-then-fix), matching the anchor for explicit validation and error recovery.	5 / 5
Progressive Disclosure	The skill is a single inlined file with the overview restated as detailed steps, and its only file pointer (diagnostics.md) is not present in the bundle, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

58%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 specific and well-scoped to a distinct niche, but it omits any explicit 'Use when…' trigger guidance and relies on technical jargon rather than the natural phrases users would actually say.

Suggestions

Add an explicit 'Use when…' clause naming concrete triggers, e.g. 'Use when keeping a customized NanoClaw fork in sync with upstream, or when the user asks to pull or merge upstream changes.'

Include natural-language synonyms users would say ('sync', 'pull updates', 'merge upstream') alongside the technical terms ('cherry-pick', 'upstream').

Mention the default merge path so the 'what' covers all update modes, not just cherry-pick.

Dimension	Reasoning	Score
Specificity	Names the domain (NanoClaw updates) and several concrete actions — 'preview', 'selective cherry-pick', 'low token usage' — leaving only minor coverage gaps, matching the 'lists several specific actions' anchor.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when…' or equivalent trigger clause; per the rubric a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant terms ('upstream updates', 'cherry-pick') but leans on git jargon and misses the natural phrases a user would say ('sync', 'pull', 'merge', 'update nanoclaw'), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Scoped to a specific product niche ('NanoClaw', 'customized install') with distinct triggers and only minor overlap risk with generic git skills, matching 'mostly distinct'.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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: jbaruch/nanoclaw-telegram
Path: .claude/skills/update-nanoclaw/SKILL.md
Commit: 7454673

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.