CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

2.74x
Quality

70%

Does it follow best practices?

Impact

96%

2.74x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is auto-updater in jdrhyne/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

72%Scale 1-3

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 (the update summary example and resources section) and missing validation checkpoints in the update workflow - there's no explicit step to verify updates succeeded before considering the job complete.

Suggestions

Add a validation step after updates (e.g., 'Verify update succeeded: clawdbot --version && clawdhub list') to the workflow

Trim the update summary format example to just show the structure, not a full realistic example

Remove or condense the Resources section - Claude can find documentation links if needed

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary sections like the detailed configuration options table and the 'Resources' section with external links. The update summary format example, while helpful, is verbose.

2 / 3

Actionability

Provides fully executable commands throughout - the cron setup command is copy-paste ready, update commands are specific, and troubleshooting includes concrete CLI commands. No pseudocode or vague instructions.

3 / 3

Workflow Clarity

The setup workflow is clear, but the 'How Updates Work' section lacks explicit validation steps. There's no feedback loop for verifying updates succeeded before proceeding, and the troubleshooting is reactive rather than preventive.

2 / 3

Progressive Disclosure

Well-organized with clear sections progressing from quick start to detailed configuration to troubleshooting. External references are one level deep and clearly signaled. Content is appropriately structured for a skill of this complexity.

3 / 3

Total

10

/

12

Passed

Description

67%Scale 1-3

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-related 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 'auto-update', 'upgrade', 'scheduled maintenance', 'keep up to date', or 'latest version'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'update Clawdbot and all installed skills', 'runs via cron', 'checks for updates', 'applies them', '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 through 'once daily' and 'automatically' rather than explicitly stated trigger conditions.

2 / 3

Trigger Term Quality

Contains some relevant terms like 'update', 'Clawdbot', 'skills', 'cron', but missing common variations users might say like 'auto-update', 'upgrade', 'refresh', 'scheduled updates', or 'maintenance'.

2 / 3

Distinctiveness Conflict Risk

Very specific niche: automated Clawdbot/skill updates via cron with daily scheduling. The combination of 'Clawdbot', 'skills', 'cron', and 'daily' creates a distinct identity unlikely to conflict with other skills.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
bap-jorkim/agent-skills-fork-feb-25
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.