CtrlK
BlogDocsLog inGet started
Tessl Logo

auto-claude-updater

Auto-update system for Auto-Claude skills and documentation. Use when checking for updates, synchronizing with upstream, updating skills automatically, or managing version compatibility.

56

Quality

65%

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 ./.claude/skills/auto-claude-updater/SKILL.md

The canonical home for this skill is auto-claude-updater in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

42%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 content is information-rich and mostly actionable, but suffers from verbosity (duplicating the bundled script inline), broken/truncated sed commands, and missing validation in destructive batch workflows. Tighter use of the existing bundle files would substantially improve it.

Suggestions

Replace the inlined sync-auto-claude-skills.sh script body with a one-line reference to scripts/sync-auto-claude-skills.sh, and reference references/CHANGELOG-LATEST.md instead of inline curl changelog fetching.

Fix the truncated 'sed -i "s/auto-claude-version: 2.7.2...' commands so each is a complete, executable substitution with closing quotes and a replacement value.

Add validation checkpoints to the Update Workflow — verify 'git pull' succeeds before 'npm run install:all', and validate skill SKILL.md frontmatter after the bulk sed version bump.

DimensionReasoningScore

Conciseness

The ~325-line body inlines the full sync script that already exists as a bundle file and repeats the same curl-to-releases/latest pattern across several sections, making it noticeably padded rather than tight.

2 / 5

Actionability

Mostly concrete, executable commands, but several 'sed -i "s/auto-claude-version: 2.7.2' blocks are truncated with missing closing quotes and replacements, so they would fail if run as written.

3 / 5

Workflow Clarity

The 4-step Update Workflow is clearly sequenced, but the destructive/batch operations (git pull over the repo, bulk sed -i across all skills) lack validation checkpoints, which caps this score at 3 per the rubric.

3 / 5

Progressive Disclosure

Bundle files exist (scripts/sync-auto-claude-skills.sh, references/CHANGELOG-LATEST.md) but the script is duplicated inline rather than referenced, and the changelog bundle is unused in favor of inline curl, leaving structure underused.

3 / 5

Total

11

/

20

Passed

Description

88%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 strong description that clearly states the skill's purpose and provides explicit 'Use when' trigger guidance with several concrete actions. Minor room for improvement on trigger-term breadth and distinctiveness from sibling auto-claude skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'checking for updates', 'synchronizing with upstream', 'updating skills automatically', 'managing version compatibility' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ('Auto-update system for Auto-Claude skills and documentation') and when ('Use when checking for updates, synchronizing with upstream...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases like 'checking for updates' and 'synchronizing with upstream', but lacks synonyms or the breadth of variants needed for a 5.

4 / 5

Distinctiveness Conflict Risk

The Auto-Claude-updater niche is mostly distinct with clear triggers, but there is minor overlap risk with closely related sibling skills like auto-claude-setup.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

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.