CtrlK
BlogDocsLog inGet started
Tessl Logo

claw-release

Release automation for Claw skills and website. Guides through version bumping, tagging, and release verification.

60

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/claw-release/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The content is highly actionable and the release workflow is clearly sequenced with validation and recovery paths, but it is a monolithic single file with a heavy inline verification block and a referenced script that is not bundled.

Suggestions

Move the ~70-line release-artifact verification script into a bundled scripts/ file and reference it, keeping SKILL.md as an overview.

Trim or relocate tangential catalog content (Existing Skills, Internal Skills) so the core release workflow stays the focal point.

Ensure ./scripts/release-skill.sh is included in the bundle or clarify how it is obtained, since the workflow depends on it.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands and no explanations of concepts Claude already knows, but tangential sections (Existing Skills, Internal Skills) and a ~70-line inline verification script could be tightened or split out.

2 / 3

Actionability

It provides fully executable bash commands throughout — pre-flight checks, the release invocation, push, and a complete copy-paste-ready verification script with real arguments — matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

A clear 5-step sequence with explicit pre-flight checks, script-side validation, a verify-release step, an undo path, and a checklist; because validation is present the destructive-operation cap does not apply.

3 / 3

Progressive Disclosure

Everything lives in one ~250-line file with a large inline verification script, and the referenced ./scripts/release-skill.sh is not present as a bundle file, so structure exists but content that could be separate remains inline.

2 / 3

Total

10

/

12

Passed

Description

67%Weight 40%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 is specific and distinct, naming concrete release actions in a clear niche, but it lacks an explicit 'when to use' trigger clause and covers only a subset of natural trigger terms a maintainer might say.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when releasing or versioning a Claw skill, cutting a release tag, or publishing a skill update'.

Broaden trigger terms to include natural maintainer phrasings like 'publish', 'ship', and 'cut a release'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'version bumping, tagging, and release verification' — scoped to a named domain ('Claw skills and website'), matching the anchor that rewards listing several specific actions.

3 / 3

Completeness

It clearly answers 'what' but provides no 'Use when...' clause or equivalent trigger guidance for when to invoke the skill, which the rubric caps at 2.

2 / 3

Trigger Term Quality

It includes relevant natural terms like 'release', 'version bumping', and 'tagging', but omits common variations a maintainer would say such as 'publish', 'ship', or 'cut a release', so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The niche is tightly scoped to 'release automation for Claw skills and website', a distinct internal-maintainer purpose unlikely to be triggered by other skills.

3 / 3

Total

10

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 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

13

/

16

Passed

Repository
prompt-security/clawsec
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.