CtrlK
BlogDocsLog inGet started
Tessl Logo

clawdbot-release-check

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

72

24.00x
Quality

62%

Does it follow best practices?

Impact

96%

24.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./clawdbot/clawdbot-release-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 well-crafted skill that efficiently documents a release-checking utility. It provides concrete, executable commands throughout, maintains excellent structure with progressive complexity, and respects token budget by assuming Claude understands basic concepts like cron and environment variables.

DimensionReasoningScore

Conciseness

Content is lean and efficient. No unnecessary explanations of what GitHub releases are or how cron works. Every section provides direct, actionable information without padding.

3 / 3

Actionability

Fully executable commands throughout with copy-paste ready examples. Installation, setup, manual usage, and update commands are all concrete with specific flags and paths.

3 / 3

Workflow Clarity

For this simple single-purpose skill, the workflow is clear: install, setup with cron, restart gateway. The 'How It Works' section provides a clear 4-step sequence. Manual usage options are well-organized with distinct purposes.

3 / 3

Progressive Disclosure

Well-structured with clear sections progressing from quick setup to manual usage to internals. State and cache file details are appropriately placed at the end for those who need them. No unnecessary nesting or external references needed for this scope.

3 / 3

Total

12

/

12

Passed

Description

24%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 identifies a specific product (clawdbot) making it distinctive, but fails to provide trigger guidance for when Claude should use it. It lacks natural keywords users would say and doesn't explain the 'when' component, making it difficult for Claude to know when to select this skill from a larger pool.

Suggestions

Add a 'Use when...' clause with trigger terms like 'clawdbot update', 'check for updates', 'new version available', 'upgrade clawdbot'

Include natural keywords users might say such as 'update', 'upgrade', 'latest version', 'release notes'

Expand on what 'check' and 'notify' mean - e.g., 'Checks GitHub for new clawdbot releases and displays a one-time notification when a newer version is available'

DimensionReasoningScore

Specificity

Names the domain (clawdbot releases) and two actions (check, notify), but lacks detail on what 'check' entails or how notification works. Not comprehensive.

2 / 3

Completeness

Describes what it does (check releases, 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

Contains technical term 'clawdbot' which users may not naturally say. Missing common variations like 'update', 'upgrade', 'new version', 'latest release'. No natural trigger keywords.

1 / 3

Distinctiveness Conflict Risk

Very specific to 'clawdbot releases' - this is a clear niche that would not conflict with other skills. The specific product name makes it highly distinctive.

3 / 3

Total

7

/

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.

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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