clawdbot-release-check
Check for new clawdbot releases and notify once per new version.
Install with Tessl CLI
npx tessl i github:jdrhyne/agent-skills --skill clawdbot-release-checkOverall
score
78%
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
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 identifies a clear, narrow niche (clawdbot release checking) which provides good distinctiveness, but suffers from missing explicit trigger guidance and limited natural keywords. The lack of a 'Use when...' clause significantly weakens its utility for skill selection among many options.
Suggestions
Add a 'Use when...' clause specifying triggers like 'Use when the user asks about clawdbot updates, new versions, or wants to check if clawdbot is up to date'
Include additional natural trigger terms users might say: 'update', 'upgrade', 'latest version', 'version check', 'outdated'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (clawdbot releases) and two actions (check, notify), but lacks detail on what checking or notifying entails or what additional capabilities exist. | 2 / 3 |
Completeness | Describes what it does (check and notify) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'clawdbot releases' and 'new version' which are relevant, but misses common variations users might say like 'update', 'upgrade', 'latest version', or 'version check'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to 'clawdbot' which is a distinct product name, making it unlikely to conflict with other skills. The niche is clear and narrow. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates strong technical writing. It's concise, provides executable commands throughout, and organizes information logically from quick setup to detailed configuration. The example output section effectively shows what to expect without over-explaining.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section serves a purpose - installation, setup, usage, and configuration are all presented without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable commands throughout - installation, setup with various flags, manual usage options, and even the update command. All examples are copy-paste ready with clear flag explanations. | 3 / 3 |
Workflow Clarity | For this simple single-purpose skill, the workflow is crystal clear: setup with cron, restart gateway, then it runs automatically. Manual usage options are well-documented with clear flags for different scenarios (--force, --reset, --status). | 3 / 3 |
Progressive Disclosure | Well-organized sections progress logically from quick setup to manual usage to internals (files, configuration). Content is appropriately sized for a single file - no need for external references given the scope. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 11 / 16 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.