CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

86%

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

The canonical home for this skill is harness-release in Chachamaru127/claude-code-harness

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-structured, highly actionable release-automation skill with a clear gated workflow and properly externalized reference material. The main weakness is conciseness: dated incident notes and internal cross-document IDs inflate the body without aiding execution.

Suggestions

Move dated incident references ('2026-08-22 release run', 'v5.3.0 run 29679591686', 'v5.6.0 3 リリース連続欠番') and internal pattern/decision IDs (P27, P35, D69, H7, Phase 56.2.3) into a short 'Design notes / history' reference file or strip them from the operational body.

Consolidate the bare-invocation contract, 自主停止の禁止, and Output Contract subsections — they overlap in forbidding the same stop-and-wait behaviors and could be trimmed to one concise contract.

The '設計思想' and '関連スキル' sections restate points already made in 'PR ready vs release ready' and the description; consider condensing or linking out to reduce token cost.

DimensionReasoningScore

Conciseness

Core operational content (preflight bash, version-sync checks, gate template, failure table) is efficient, but inline incident history ('2026-08-22 release run', 'v5.3.0 run 29679591686') and internal pattern IDs (P27, P35, D69, H7, Phase 56.2.3) are padding a fresh operator does not need.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready commands (preflight checks, 'claude plugin validate', 'python3 scripts/check-release-version-sync.py', gh/git/tag commands, verify-publish with documented exit codes), with minor gaps from placeholders and plugin-root scripts not in the skill bundle.

4 / 5

Workflow Clarity

The '単一ゲートフロー' section lays out a fully numbered Review Gate → Work Commit Gate → Pre-Gate (1-8) → Confirmation Gate → Post-Gate (9-19) sequence with explicit validation checkpoints and feedback loops (review→fix→re-review until APPROVE, post-gate failure/recovery table, verify-publish polling).

5 / 5

Progressive Disclosure

The body is an overview that pushes detailed logic to six one-level-deep references (version-files, bump-detection, release-notes, post-gate-detail, github-release, versioning), all linked via ${CLAUDE_SKILL_DIR}/references/ and all present in the bundle.

5 / 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 strong, third-person description that states concrete capabilities, explicit positive triggers, and negative-scope guidance to avoid misfires. Trigger-term coverage is good but could add a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete release actions — 'bump detection, CHANGELOG promotion, PR/main merge, tag, GitHub Release' — giving comprehensive coverage of the pipeline rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what ('end-to-end automation: bump detection... GitHub Release') and when ('Trigger: release, version bump, publish'), plus negative guidance 'Do NOT load for: implementation, review, planning, setup'.

5 / 5

Trigger Term Quality

Provides natural triggers 'release, version bump, publish' that users would actually say, but stops short of comprehensive synonym coverage (e.g. 'changelog', 'tag', 'github release').

4 / 5

Distinctiveness Conflict Risk

The 'Keep a Changelog + GitHub' niche and explicit negative triggers ('Do NOT load for: implementation, review, planning, setup') sharply separate it from sibling harness-review/plan 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.

Validation — 14 / 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

Path

opencode/skills/harness-release/SKILL.md

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.