clawdbot-release-check
Check for new OpenClaw releases and notify once per new version.
70
59%
Does it follow best practices?
Impact
90%
1.45xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./clawdbot/clawdbot-release-check/SKILL.mdQuality
Discovery
40%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 concise and targets a clear niche (OpenClaw release checking), which gives it strong distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from more specific action details and natural trigger terms users might employ when requesting this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about OpenClaw updates, new versions, or release notifications.'
Include natural trigger term variations such as 'update', 'new version', 'upgrade', 'changelog', or 'release check' to improve keyword coverage.
Expand the 'what' portion with more concrete actions, e.g., 'Polls the OpenClaw repository for new releases, compares against the last seen version, and sends a one-time notification per new version.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (OpenClaw releases) and two actions (check for releases, notify), but doesn't elaborate on what 'check' or 'notify' entails concretely (e.g., polling a URL, comparing versions, sending a message). | 2 / 3 |
Completeness | Describes what it does (check for new OpenClaw releases and notify) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, bringing it closer to 1. | 1 / 3 |
Trigger Term Quality | Includes 'OpenClaw' and 'releases' as relevant keywords, but misses natural variations users might say like 'update', 'new version', 'upgrade', 'changelog', or 'release notes'. | 2 / 3 |
Distinctiveness Conflict Risk | 'OpenClaw' is a very specific product name, making this skill clearly distinguishable from other skills and unlikely to conflict with anything else. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides clear, actionable commands for checking OpenClaw releases. Its main weakness is the lack of a verification/validation step after setup to confirm the cron job and notifications are working correctly. The progressive disclosure is adequate for the skill's size but could be slightly improved with verification guidance.
Suggestions
Add a verification step after setup, e.g., 'Run `{baseDir}/scripts/check.sh --status` to confirm the cron job is active and notifications are configured correctly.'
Consider adding a brief troubleshooting note or link for common issues (e.g., Telegram ID not working, gateway restart failures).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what GitHub releases are or how cron works. Every section serves a clear purpose and every token earns its place. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for setup, manual usage, and configuration. All flags are listed with clear purposes, and file paths for state/cache are explicitly specified. | 3 / 3 |
Workflow Clarity | The setup workflow includes a clear sequence (setup then restart gateway), but there's no validation step to confirm the cron job was installed correctly or that notifications are working. For a task involving scheduled operations, a verification step (e.g., 'run --status to confirm setup') would improve confidence. | 2 / 3 |
Progressive Disclosure | Content is well-organized into logical sections, but everything is inline in a single file. The manual usage flags could benefit from a linked reference for detailed descriptions, and there's no pointer to troubleshooting or advanced configuration docs if they exist. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 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.