skill-updater

Apply improvements to Claude Code skills systematically. Workflow for planning updates, implementing changes, validating improvements, and documenting changes. Use when applying review recommendations, updating skills based on feedback, enhancing existing skills, or implementing systematic improvements across multiple skills.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/skill-updater/SKILL.md

Quality

Content

60%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 reasonably clear, well-structured 5-step workflow with some executable code, but it is weakened by redundant workflow presentation and vague validation/application steps that lack concrete commands.

Suggestions

Eliminate the duplicate workflow listing — keep either the Overview summary or the detailed "Update Workflow" section, not both — to improve conciseness.

Replace vague validation guidance ("Run skill-validator", "Test after each change") with the actual commands or invocation syntax so each step is executable.

Add an explicit error-recovery feedback loop in Step 4 (e.g., "If validation fails: revert via backup or fix and re-validate before proceeding") to strengthen workflow clarity for a destructive/batch operation.

Dimension	Reasoning	Score
Conciseness	The 5-step workflow is presented twice (a compact list in the Overview and again in the detailed "Update Workflow" section) and the Quick Reference repeats it, adding redundant tokens; it is mostly efficient but could be tightened by keeping one presentation.	3 / 5
Actionability	It offers executable guidance for backup (cp -r / git commit) and a concrete documentation template, but key steps like "Run skill-validator (structure, content, pattern)" and "Test after each change" lack the actual commands or specifics needed to execute.	3 / 5
Workflow Clarity	The Plan → Backup → Apply → Validate → Document sequence is clear and includes an explicit validation step (Step 4 compares before/after and verifies no regressions), but the error-recovery feedback loop (what to do when validation fails) is only weakly implied.	4 / 5
Progressive Disclosure	No bundle files exist, so the single-file content is appropriately organized under clear section headers; the duplicated workflow listing is the main organization gap keeping it from a 5.	4 / 5
	Total	14 / 20 Passed

Description

83%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 well-constructed with a clear what/when structure, third-person imperative voice, and concrete trigger phrases. It is strong on completeness and only slightly generic on specific actions and overlap risk.

Dimension	Reasoning	Score
Specificity	Names the domain (Claude Code skills) and lists several concrete actions — "planning updates, implementing changes, validating improvements, and documenting changes" — but several actions like "implementing changes" remain generic, so it stops short of comprehensive coverage.	4 / 5
Completeness	It explicitly answers both what ("Apply improvements... planning updates, implementing changes, validating improvements, and documenting changes") and when ("Use when applying review recommendations, updating skills based on feedback...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are present — "review recommendations", "updating skills based on feedback", "enhancing existing skills", "systematic improvements" — giving good keyword coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The niche of systematically improving Claude Code skills is mostly distinct, but triggers like "enhancing existing skills" and "systematic improvements" create minor overlap risk with skill-reviewer and skill-validator.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/skill-updater/SKILL.md
Commit: 93ed392

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.