CtrlK
BlogDocsLog inGet started
Tessl Logo

harness-release

Generic release automation for projects using Keep a Changelog + GitHub. Single confirmation gate then end-to-end automation: bump detection, CHANGELOG promotion, PR/main merge, tag, GitHub Release. Trigger: release, version bump, publish. Do NOT load for: implementation, review, planning, setup.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 thorough, well-sequenced release workflow with strong validation and good reference structure. Main weaknesses are repeated bare-invocation prose that could be tightened and several referenced scripts missing from the bundle.

Suggestions

Consolidate the repeated bare-invocation intent (currently restated at lines 38-39, 58-60, and 61) into a single canonical statement to reduce redundancy.

Bundle or verify the referenced scripts (release-preflight.sh, check-release-version-sync.py, release-verify-publish.sh, build-opencode.js) so the actionability guidance is fully executable as-is.

Move the full Confirmation Gate plan block and environment-variable tables into a reference file to keep SKILL.md closer to an overview and lift progressive_disclosure.

DimensionReasoningScore

Conciseness

Mostly purposeful dense content, but the bare-invocation intent and 'release complete' framing are restated multiple times (e.g., lines 38-39, 58-60, 61), which is more than minor trimming.

3 / 5

Actionability

Concrete, executable bash/git/gh commands throughout, but several referenced scripts (release-preflight.sh, check-release-version-sync.py, release-verify-publish.sh, build-opencode.js) are not present in the bundle, leaving minor execution gaps.

4 / 5

Workflow Clarity

Explicit 3-stage numbered sequence (Pre-Gate 1-8, Confirmation Gate, Post-Gate 9-19) with abundant validation checkpoints (fail-closed preflight, version-sync, reachability check, verify-publish) and a failure-recovery table with feedback loops.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references to 6 real references/*.md files (all verified present), but SKILL.md itself is a long ~360-line document that inlines considerable detail beyond a pure overview.

4 / 5

Total

16

/

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 strong, concrete, third-person description that clearly states what the skill does, when to trigger it, and what to avoid it for. Minor room only in trigger-term synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete end-to-end actions ('bump detection, CHANGELOG promotion, PR/main merge, tag, GitHub Release'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (release automation chain) and 'when' ('Trigger: release, version bump, publish') with concrete trigger phrases and an exclusion list.

5 / 5

Trigger Term Quality

'Trigger: release, version bump, publish' provides good natural-term coverage plus explicit anti-triggers, but lacks the synonyms/extensions needed for the top anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Keep a Changelog + GitHub release automation) and explicit 'Do NOT load for: implementation, review, planning, setup' minimize overlap with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing, 7 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository
Chachamaru127/claude-code-harness
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.