CtrlK
BlogDocsLog inGet started
Tessl Logo

update-skills

Re-apply your installed skills to pull their latest code from upstream.

63

Quality

73%

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

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.

The body is a well-structured, lean, command-driven workflow with clear sequencing, explicit validation and feedback loops, and clean section organization requiring no external references.

DimensionReasoningScore

Conciseness

The body is lean and command-driven (e.g. 'git status --porcelain', 'git fetch origin channels providers --prune'), assumes Claude's competence with no git tutorials, and its explanatory prose (such as the Step 4 container-rebuild rationale) earns its place by clarifying a non-obvious ordering rule.

3 / 3

Actionability

It provides concrete, executable commands throughout ('git rev-parse --short HEAD', 'pnpm run build', './container/build.sh') plus specific detection instructions ('read src/channels/index.ts and collect each import'), reaching the copy-paste-ready anchor at 3.

3 / 3

Workflow Clarity

Steps 0-5 are clearly sequenced with an explicit validation checkpoint in Step 4 (build + test, container rebuild gated on git diff) and an error-recovery feedback loop ('If build fails... If unclear, ask the user'), matching the clear-sequence-with-feedback anchor at 3.

3 / 3

Progressive Disclosure

The skill is a single well-organized SKILL.md with clearly labeled sections (About, How it works, Goal, Operating principles, Steps 0-5) and no external bundle files or nested references, so organization scores at the top anchor.

3 / 3

Total

12

/

12

Passed

Description

47%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.

The description conveys a concrete maintenance action and occupies a distinct niche, but it lacks an explicit 'when to use' trigger and leans on technical jargon rather than natural user terms, and its second-person voice incurs a specificity penalty.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases, e.g. 'Use when the user wants to update or refresh installed skills, pull the latest skill code, or mentions skills being out of date.'

Rephrase in third person ('Re-applies installed skills to pull their latest code from upstream') to avoid the second-person voice penalty.

Broaden natural trigger terms to include common variations like 'update skills', 'refresh skills', and 'pull latest skill code' rather than only 're-apply' and 'upstream'.

DimensionReasoningScore

Specificity

The description names the domain ('installed skills') and one concrete action ('pull their latest code from upstream'), which would normally anchor at 2; however the second-person phrasing 'your installed skills' triggers the voice penalty, reducing specificity by 1.

1 / 3

Completeness

It clearly states what the skill does but provides no 'Use when...' trigger clause, and the rubric caps completeness at 2 when explicit when-to-use guidance is missing.

2 / 3

Trigger Term Quality

It has some relevant keywords ('installed skills', 'pull their latest code') but relies on technical jargon ('re-apply', 'upstream') and lacks the common natural variations a user would actually say, so it sits at 2 rather than 3.

2 / 3

Distinctiveness Conflict Risk

The niche of re-applying installed skills to refresh upstream code is distinct and unlikely to trigger for unrelated content-handling skills, matching the clear-niche anchor at 3.

3 / 3

Total

8

/

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.