auto-updater
Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
Overall
score
75%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates specific capabilities with concrete actions and has a clear, distinctive niche. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users might employ when seeking update functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when setting up automatic updates, configuring scheduled maintenance, or when the user asks about keeping Clawdbot current.'
Include additional natural trigger terms like 'upgrade', 'auto-update', 'scheduled updates', 'keep up to date', or 'maintenance' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'update Clawdbot and all installed skills', 'runs via cron', 'checks for updates', 'applies them', and 'messages the user with a summary'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (automatic daily updates via cron with user notification), but lacks an explicit 'Use when...' clause. The 'when' is only implied by 'once daily' and 'automatically'. | 2 / 3 |
Trigger Term Quality | Contains some relevant terms like 'update', 'Clawdbot', 'skills', 'cron', but missing common variations users might say like 'upgrade', 'auto-update', 'scheduled updates', or 'daily maintenance'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - automatic Clawdbot/skill updates via cron with daily scheduling. The combination of 'Clawdbot', 'skills', 'cron', and 'daily' creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear executable commands and good organization. The main weaknesses are some verbosity that could be trimmed (configuration table, lengthy example output) and missing explicit validation steps in the update workflow to verify success before considering the job complete.
Suggestions
Add an explicit validation step after updates (e.g., 'Verify update succeeded: clawdbot --version && clawdhub list') integrated into the workflow
Trim the configuration options table - these are self-explanatory from the cron command flags
Condense the update summary format example to show just the structure without 8 example skill names
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., the table of configuration options with obvious defaults, explaining what each package manager command does). The update summary format example is helpful but lengthy. | 2 / 3 |
Actionability | Provides fully executable commands throughout - the cron setup command is copy-paste ready with all flags, update commands are concrete, and troubleshooting includes specific diagnostic commands. | 3 / 3 |
Workflow Clarity | The setup workflow is clear, but the skill lacks explicit validation checkpoints. After running updates, there's no verification step to confirm success beyond reading the summary message. The 'always run clawdbot doctor after updating' is mentioned but not integrated into a clear workflow sequence. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from quick start to detailed configuration to troubleshooting. External resources are linked at the end with one-level-deep references. Content is appropriately structured for a skill of this complexity. | 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 | |
- 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.