CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-skills

Check for and apply updates to installed skill branches from upstream.

Quality

74%

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 ./.claude/skills/update-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a well-sequenced, command-driven procedure with strong validation and error-recovery loops. Minor improvements are possible: consolidate the redundant merge-detection alternatives into one recommended check and trim the overlapping intro sections.

Suggestions

Collapse Step 1's three alternative 'has this skill been merged' checks into a single recommended method to remove ambiguity and save tokens.

Trim the '# About'/'How it works' preamble, which restates content covered by the Goal and Step sections.

DimensionReasoningScore

Conciseness

The body is lean and command-first with no explanations of git concepts Claude already knows; the only trimmable redundancy is Step 1's three overlapping 'merged before?' detection methods, which fits 'efficient; minor instances that could be trimmed' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete, copy-paste-ready git commands appear at every step (git status --porcelain, git fetch upstream --prune, git merge upstream/skill/<name> --no-edit, git merge --abort), but Step 1 presents three alternative detection checks without committing to one recommended path, leaving a minor gap versus fully executable guidance.

4 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced with an explicit preflight (clean-tree check), a conflict-resolution feedback loop, an abort-and-continue recovery path for failed merges, and post-merge validation via npm run build/test — satisfying the batch-operation validation requirement and matching the explicit-checkpoints-with-recovery anchor.

5 / 5

Progressive Disclosure

A single-file skill with well-organized sections and no external files needed; the '# About'/'How it works' preamble partially duplicates the Goal/Operating-principles and step sections, a minor organization gap consistent with 'good structure; minor organization gaps'.

4 / 5

Total

17

/

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 states a clear, domain-specific capability in the third person with two concrete actions, but it omits any explicit trigger guidance ('Use when...') and natural user phrasings, which limits discoverability and completeness.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks to update skills, sync skill branches, or bring installed skills up to date with upstream.'

Include natural synonyms users would say (e.g., 'update skills', 'skill updates', 'sync skills') to improve trigger-term coverage.

Optionally name a third concrete action (e.g., 'resolves conflicts and validates with build + test') to raise specificity from 1-2 actions to several.

DimensionReasoningScore

Specificity

Names the domain ('installed skill branches', 'upstream') and exactly two concrete actions ('Check for' and 'apply updates'), matching the 1-2-actions anchor; it does not list several actions, so it falls short of level 4.

3 / 5

Completeness

The 'what' is clear (check for and apply updates to installed skill branches), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'updates' is a term users would naturally say, but the description offers no synonyms or common phrasings (e.g., 'update my skills', 'skill updates', 'new versions'), matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'installed skill branches from upstream' defines a clear niche with minimal overlap against other skills, but the terse phrasing leaves minor overlap room with generic git/update skills, fitting 'mostly distinct; minor overlap risk' rather than the fully distinct anchor.

4 / 5

Total

13

/

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

jbaruch/nanoclaw-telegram

Path

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