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.
77
66%
Does it follow best practices?
Impact
98%
2.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./clawdbot/auto-updater/SKILL.mdQuality
Discovery
67%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 does a good job of explaining what the skill does with specific concrete actions and occupies a clear niche. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users might say when they want to configure or manage automatic updates.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to set up automatic updates, configure scheduled skill updates, or manage OpenClaw auto-update settings.'
Include additional natural trigger terms like 'auto-update', 'scheduled updates', 'keep skills current', or 'update schedule' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'update OpenClaw and selected skills', 'runs via cron', 'checks for updates', 'applies them', 'messages the user with a summary of what changed'. These are clear, concrete actions. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (updates OpenClaw and skills daily via cron, messages user with summary), but lacks an explicit 'Use when...' clause. The when is only implied by the automated nature of the task. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'cron', 'updates', 'daily', and 'OpenClaw', but misses natural user phrases like 'auto-update', 'scheduled updates', 'keep skills up to date', or 'update schedule'. The terms are more descriptive than trigger-oriented. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — automatic daily updates of OpenClaw and skills via cron is highly specific and unlikely to conflict with other skills. The combination of 'cron', 'OpenClaw', and 'daily update' creates a clear, unique identity. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable commands for setting up auto-updates with good concrete examples. However, it could be more concise by trimming the introductory explanation and could improve workflow clarity by adding explicit validation checkpoints after critical steps like cron creation and update execution. The troubleshooting section is useful but could be better organized as a separate reference.
Suggestions
Add a validation step after cron setup (e.g., 'Verify with `openclaw cron list` that the entry appears correctly') and after updates run to confirm success before reporting.
Remove the 'What It Does' section since it restates the skill's purpose — jump straight to Setup.
Move Troubleshooting and Manual Commands to a separate REFERENCE.md file and link to it from the main skill to reduce token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary sections like 'What It Does' which restates what the skill description already covers. The manual commands section and some explanatory text could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout — the cron setup command with all flags, npm update commands, health checks, clawhub commands, and troubleshooting steps are all concrete and specific. | 3 / 3 |
Workflow Clarity | The setup and update steps are listed but there's no explicit validation after the cron job is created (e.g., verify it was added successfully), and the update workflow lacks a feedback loop — no step to verify the update succeeded before proceeding to health checks or reporting. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the troubleshooting and manual commands sections add bulk that could be in a separate reference file. The external resource links at the end are generic URLs without clear signaling of what they contain. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- jdrhyne/agent-skills
- Commit
6768672
- 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.