auto-updater

Automatically update OpenClaw and selected skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.

2.00x

Quality

61%

Does it follow best practices?

Impact

98%

2.00x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./clawdbot/auto-updater/SKILL.md

Quality

Content

65%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 concise and actionable with solid section structure and executable commands, but it omits validation checkpoints for a batch update workflow (capping workflow clarity) and fails to link the existing reference bundle files (weakening progressive disclosure).

Suggestions

Add explicit validation/feedback checkpoints to the update workflow (e.g. capture before/after versions, confirm updates applied, retry once on failure, report errors) so batch operations are verifiable.

Link the existing reference files from the body with clear one-level-deep pointers (e.g. 'See references/agent-guide.md for the full setup procedure' and 'See references/summary-examples.md for report formatting'), rather than leaving them orphaned.

De-duplicate the repeated 'clawhub update --all' instructions between 'How Updates Work' and 'Manual Commands' to tighten conciseness toward anchor 5.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; minor redundancy (e.g. 'clawhub update --all' appears in both How Updates Work and Manual Commands) keeps it just below anchor 5.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout ('openclaw cron add ...', 'npm update -g openclaw@latest', 'clawhub update --all --no-input --force'); minor gaps such as health-check context keep it at 4 rather than 5.	4 / 5
Workflow Clarity	The setup sequence is present, but this daily batch update workflow has no validation/verification checkpoints (no version-change confirmation, no retry-on-failure), so per the rubric cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Section structure is good, but the provided bundle files (references/agent-guide.md, references/summary-examples.md) are never referenced or signaled from the body, so content that should be navigated to is orphaned rather than clearly linked one level deep.	3 / 5
	Total	14 / 20 Passed

Description

58%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 specific and action-oriented with a clear 'what', but it lacks an explicit 'Use when...' trigger clause, which caps completeness and weakens trigger-term quality. Distinctiveness is reasonably strong thanks to the OpenClaw/skills/cron framing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to keep OpenClaw and installed skills up to date automatically or asks about daily/scheduled updates.'

Include natural user-facing synonyms in the description ('keep up to date', 'auto-update', 'scheduled updates', 'upgrade skills') to broaden trigger coverage.

Tighten the action list into a more comprehensive enumeration (e.g. name the update sources explicitly) to push specificity toward anchor 5.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ('Runs via cron', 'checks for updates', 'applies them', 'messages the user with a summary of what changed'); falls short of anchor 5 because the action coverage is broad rather than comprehensively enumerated.	4 / 5
Completeness	Clearly states what the skill does, but there is no 'Use when...' or equivalent explicit trigger clause; per the rubric this caps completeness at 3 even though the 'what' is clear.	3 / 5
Trigger Term Quality	Contains relevant keywords ('update', 'OpenClaw', 'skills', 'daily', 'cron') but misses common natural variations a user would say and has no explicit trigger phrasing, so it sits at 'some relevant keywords but missing variations'.	3 / 5
Distinctiveness Conflict Risk	The OpenClaw + skills + cron framing carves out a mostly distinct niche with only minor overlap risk against generic update utilities; not a clean 5 because 'update' is broadly generic.	4 / 5
	Total	14 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: jdrhyne/agent-skills
Path: clawdbot/auto-updater/SKILL.md
Commit: 439cd3a

Reviewed: 13 days 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.