Content
N/AReviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Something went wrong
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.
78
2.00x
Quality
67%
Does it follow best practices?
Impact
98%
2.00xAverage score across 3 eval scenarios
Securityby
Advisory
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./clawdbot/auto-updater/SKILL.mdQuality
Description
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 explaining what the skill does with specific concrete actions and occupies a clear, distinct niche. However, it lacks an explicit 'Use when...' clause, which is important for Claude to know when to select this skill. The trigger terms could also be expanded to cover more natural user phrasings.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about setting up automatic updates, configuring cron-based skill updates, or managing OpenClaw update schedules.'
Include additional natural trigger terms like 'auto-update', 'scheduled updates', 'keep skills current', or 'update schedule' to improve matching with user requests.
| 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 operations. | 3 / 3 |
Completeness | The 'what' is well covered (update OpenClaw/skills daily via cron, check/apply updates, message user). However, there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill, which caps this at 2 per the rubric guidelines. | 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 cron-based updates for OpenClaw and skills with user notification. This is unlikely to conflict with other skills due to the specific combination of cron scheduling, OpenClaw updates, and daily cadence. | 3 / 3 |
Total | 10 / 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
292843f
- 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.