clawdbot-release-check

Check for new OpenClaw releases and notify once per new version.

1.45x

Quality

61%

Does it follow best practices?

Impact

90%

1.45x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./clawdbot/clawdbot-release-check/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a reasonably concise and well-structured skill that provides concrete CLI commands for checking OpenClaw releases. However, it lacks validation/verification steps in its workflow, the referenced scripts are not included in the bundle, and the `{baseDir}` placeholder is used without clear resolution instructions. The skill would benefit from a verification step after setup and from including or explaining the referenced scripts.

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').

Clarify how `{baseDir}` is resolved — is it auto-populated by the system, or does the user need to set it?

Include the referenced scripts (`setup.sh`, `check.sh`) in the bundle or explain where they come from after `clawhub install`.

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	Commands are concrete and copy-paste ready, but they rely on placeholder variables like `{baseDir}` and `YOUR_TELEGRAM_ID` without explaining how to resolve `{baseDir}`. The scripts themselves are not provided in the bundle, so it's unclear what they actually do or what output to expect.	2 / 3
Workflow Clarity	The setup workflow (install → setup cron → restart gateway) is present but lacks validation checkpoints. There's no guidance on what to do if setup fails, how to verify the cron job was created correctly, or how to confirm notifications are working. For a task involving scheduled operations, a verification step would be important.	2 / 3
Progressive Disclosure	The content is well-organized into clear sections (Quick Setup, Manual Usage, Files, Configuration), but no bundle files are provided despite referencing scripts like `setup.sh` and `check.sh`. The skill references `{baseDir}/scripts/` paths but there are no supporting files to back them up, making the references unverifiable.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 reasonably clear about its purpose—monitoring OpenClaw releases and notifying once per version—but lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms. Its strongest aspect is distinctiveness due to the specific product name 'OpenClaw', but the lack of trigger guidance and limited keyword coverage weaken its overall effectiveness for skill selection.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about OpenClaw updates, new versions, or release notifications.'

Include additional natural trigger terms such as 'update', 'new version', 'latest release', 'upgrade', or 'changelog' to improve keyword coverage.

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 GitHub API, comparing version numbers, sending a message).	2 / 3
Completeness	Answers 'what' (check for new OpenClaw releases and notify once per new version) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes 'OpenClaw' and 'releases' as relevant keywords, but misses natural variations users might say such as 'update', 'new version', 'upgrade', 'changelog', or 'OpenClaw update check'.	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 generic release-checking or notification skills.	3 / 3
	Total	9 / 12 Passed

Validation

72%

Warnings & errors only

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: 292843f

Reviewed: about 17 hours ago

Table of Contents

Discovery Implementation Validation

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.