release

Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

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

A strongly actionable, well-sequenced release runbook with robust validation checkpoints and a useful common-mistakes table. The main weakness is verbosity in Step 4, which inlines internal implementation detail that the release procedure does not require.

Suggestions

Trim Step 4 to a one-line "no manual blockrun sync needed — npm publish handles it" and drop the TypeScript fetch snippet, moving that background to a reference file if it must be preserved.

Consider extracting the recurring-mistake rationale (Step 4 implications + the Common Mistakes table row) into a single dedicated 'Deprecated patterns' section to consolidate the repeated explanation.

Add a concrete command for Step 2 (e.g., `npm version <newversion> --no-git-tag-version`) to match the copy-paste readiness of the other steps.

Dimension	Reasoning	Score
Conciseness	Most steps are tight command one-liners, but Step 4 inlines ~30 lines of tangential background (a 12-line TypeScript snippet of blockrun's internal fetch logic plus implication bullets) that could be trimmed to a single "no manual sync needed" note.	3 / 5
Actionability	Nearly every step supplies copy-paste bash commands with consistent {VERSION} placeholders, plus a concrete CHANGELOG format and a 5-point final verification script.	5 / 5
Workflow Clarity	Twelve clearly sequenced steps with explicit validation gates ("All must pass. Fix failures before proceeding.") and a final checklist ("If any mismatch, fix before declaring the release done"), satisfying the feedback-loop requirement for this publish/tag operation.	5 / 5
Progressive Disclosure	No bundle files exist and the body is a self-contained, well-organized numbered procedure; the only gap is Step 4's inline blockrun-server reference material that is tangential to the release procedure itself.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that clearly states both the capability set and the invocation condition for a narrow, distinctive niche. The only gap is synonym coverage in the description itself (partially compensated by the separate triggers list).

Dimension	Reasoning	Score
Specificity	Lists seven concrete release actions ("version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release"), matching the comprehensive-coverage anchor; no explicit I/You pronoun so no voice penalty applies.	5 / 5
Completeness	Explicitly answers both what ("Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release") and when ("Use this skill for EVERY ClawRouter release"), so the missing-trigger cap does not apply.	5 / 5
Trigger Term Quality	Natural terms like "release", "publish", "git tag", and "GitHub release" are present, but synonyms such as "ship", "version bump", or "deploy" appear only in the triggers field rather than the description itself.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to "ClawRouter release" with project-specific triggers, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: BlockRunAI/ClawRouter
Path: skills/release/SKILL.md
Commit: bd13340

Reviewed: 5 days 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.