CtrlK
BlogDocsLog inGet started
Tessl Logo

update-skills

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

56

Quality

64%

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

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.

The body is a well-structured, actionable git workflow with explicit validation and conflict-recovery feedback loops. Tightening the redundant overview and consolidating the detection alternatives would push conciseness and actionability to full marks.

DimensionReasoningScore

Conciseness

Relies on direct git commands and assumes Claude's competence, but the 'How it works' overview partly duplicates the numbered steps and the detection step lists multiple alternative approaches that could be trimmed.

4 / 5

Actionability

Provides concrete, executable git commands at each step that are largely copy-paste ready; minor gaps come from offering competing detection alternatives without a single recommended path.

4 / 5

Workflow Clarity

A clear Step 0–5 sequence with conflict-resolution feedback loops and post-merge build/test validation; validation is batch-level (after all merges) rather than per-merge, leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

Well-organized into labeled sections (About, Goal, Operating principles, Steps) in a self-contained file with no external references needed; no content clearly belongs in a separate file.

4 / 5

Total

16

/

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 is concise, third-person, and clearly states the skill's purpose, but it lacks an explicit 'when to use' trigger clause and uses somewhat technical language. Adding natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause with natural user phrasing, e.g. 'Use when the user wants to update installed skills or pull the latest skill versions from upstream.'

Include common synonyms/extensions users might say, such as 'update skills', 'pull skill updates', or 'sync skills'.

Specify one more concrete action (e.g. 'resolve merge conflicts') to broaden coverage and raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('installed skill branches from upstream') and two concrete actions ('Check for' and 'apply updates'), but the coverage is narrow rather than comprehensive.

3 / 5

Completeness

Clearly states what the skill does, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes some natural terms ('updates', 'skill branches') but leans on technical jargon ('upstream', 'branches') and lacks common synonyms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (updating installed skill branches from upstream) with low conflict risk; only minor overlap with general git-maintenance skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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