Name: validate-a-release
Rating: 66.4 (1 reviews)
Author: different-ai

validate-a-release

Validate the release, check the released binaries, is 0.18.x safe to roll out, prove a published desktop release. Boots the RELEASED mac-arm64 enterprise and cloud binaries through the packaged journeys, checks updater manifests and notarization, and publishes evidence.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/validate-a-release/SKILL.md

Quality

Content

88%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 dense, highly actionable runbook with excellent sequencing and validation checkpoints; its main weakness is inline version-specific detail that will rot and the absence of any reference split for a 115-line file.

Suggestions

Move rot-prone release-specific notes (0.18.45/0.18.46 IPC rejections, #4727, the 0.18.44 negative-control result) into a 'Known-bad releases' or 'Historical notes' section so the core workflow stays evergreen.

Consider extracting the journey command table or the scope statement into a reference file to give the SKILL.md body a clearer overview-first structure.

Parameterize the hardcoded repo path 'different-ai/openwork' and the MySQL command if they vary, so the runbook generalizes beyond one setup.

Dimension	Reasoning	Score
Conciseness	Lean and task-relevant with no concept padding, but inline time-sensitive specifics (0.18.45/0.18.46, #4726/#4727, '0.18.44 fails with Local context is missing') sit outside any deprecated/old-patterns section, which the rubric penalizes.	4 / 5
Actionability	Fully executable, copy-paste-ready bash throughout, with a journey table giving exact invocations covering the common release-validation cases.	5 / 5
Workflow Clarity	Clear five-step sequence with explicit validation gates ('stop and report', verdict/skipped checks, 're-extract if not') and a negative control, providing feedback loops for error recovery.	5 / 5
Progressive Disclosure	No bundle files exist; the skill is a single self-contained file with well-organized numbered sections, but it lacks an overview-pointing-to-references pattern and is somewhat long for one file.	4 / 5
	Total	18 / 20 Passed

Description

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

The description is specific and distinct, naming concrete release-validation actions with natural trigger phrases, but lacks an explicit 'Use when...' clause so the use-condition is only weakly implied.

Suggestions

Add an explicit trigger clause such as 'Use when validating whether a published OpenWork desktop release is safe to roll out' to lift completeness.

Trim the generic opening ('Validate the release, check the released binaries') that restates the concrete actions already in the second sentence.

Add a couple of synonyms users might say ('release gate', 'rollout sign-off') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Boots the RELEASED mac-arm64 enterprise and cloud binaries through the packaged journeys, checks updater manifests and notarization, and publishes evidence'), though the opening restates the goal generically.	4 / 5
Completeness	The 'what' is clear but there is no explicit 'Use when...' clause; the 'when' is only weakly implied via trigger phrases, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural phrases a user would say ('is 0.18.x safe to roll out', 'validate the release', 'prove a published desktop release') with good coverage, missing a few synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (mac-arm64 release validation for a named product) with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: different-ai/openwork
Path: .opencode/skills/validate-a-release/SKILL.md
Commit: 417244c

Reviewed: 2 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.