CtrlK
BlogDocsLog inGet started
Tessl Logo

auto-updater

Automatically apply improvements to skills and the ecosystem based on system-reviewer findings and best-practices-learner insights. Workflow for automated improvement identification, priority assessment, safe application, validation, and rollback capability. Use when applying systematic improvements, automating enhancement cycles, bulk updating multiple skills, or implementing ecosystem-wide improvements.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/auto-updater/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A clear, well-structured workflow document with explicit validation and rollback for a batch/destructive operation. Its main weaknesses are duplicated safe/unsafe content inflating tokens and action guidance that stays high-level without executable commands or templates.

Suggestions

Remove the duplicated Safe-vs-Unsafe Automation block from the Quick Reference (or from Step 2) to cut tokens without losing information.

Add concrete, executable detail to Step 3 (Apply Updates) — e.g. an actual command or a copy-paste template for the Quick Reference insertion that anchors the worked example.

Condense the verbose worked example into a compact table or shorten the per-step narration; the result summary already conveys the impact.

DimensionReasoningScore

Conciseness

Mostly efficient with bullet/section structure, but the Safe-vs-Unsafe lists are duplicated between Step 2 and the Quick Reference, and the worked example block is lengthy padding that could be trimmed.

3 / 5

Actionability

Names concrete targets (skill-validator, review-multi structure check, git commit/copy backup) but provides no executable commands, templates, or file-edit specifics, leaving the actual apply-step under-specified.

3 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with an explicit Validate step and a Rollback feedback loop for batch operations, but lacks formalized checklists that would push it to fully explicit validation.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized with Overview, When to Use, per-step sections, an example, and a Quick Reference table, with only minor organization gaps from the duplicated content.

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.

A well-constructed description that explicitly states both capability and trigger conditions, anchored to a specific niche via named sibling skills. The action list is concrete but slightly abstract, and a few natural synonyms would round out trigger coverage.

DimensionReasoningScore

Specificity

Names several concrete actions ("improvement identification, priority assessment, safe application, validation, and rollback capability") but the actions are somewhat high-level rather than fully concrete, leaving minor coverage gaps.

4 / 5

Completeness

Clearly answers what (the 5-step improvement workflow: identification, assessment, application, validation, rollback) and when (explicit "Use when..." clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

"Use when applying systematic improvements, automating enhancement cycles, bulk updating multiple skills, or implementing ecosystem-wide improvements" gives good natural-phrase coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Ties the skill to specific siblings (system-reviewer, best-practices-learner) and ecosystem-improvement automation, creating a mostly-distinct niche with only minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.