release

Step through versioning, tagging, and verification

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/release/SKILL.md

Quality

Content

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

The content is a tight, executable, well-sequenced release runbook with concrete commands throughout and appropriate verification steps, weakened only by a few time-sensitive hardcoded values and a tangential context line.

Suggestions

Replace the hardcoded `0.1.21` with a placeholder (e.g. `pnpm bump:set -- <version>`) to avoid time-sensitive staleness.

Add an explicit pre-tag checkpoint confirming the bump commit is merged into `main` before running `git tag`, and an explicit "if verification fails" branch pointing to the Rerun step.

Trim or justify the OpenCode-primitives sentence in Prepare, as it is not directly tied to the release steps.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-driven, but time-sensitive specifics (the hardcoded version example `0.1.21`, the repo `Devin-AXIS/iPolloWork`) and a tangential OpenCode-primitives sentence could be tightened, so it is mostly efficient rather than fully lean.	3 / 5
Actionability	Every section provides copy-paste-ready, executable commands (`pnpm bump:*`, `git tag`/`git push`, `gh workflow run`, `gh run list`, `gh release view`) with specific file paths, covering the common release cases.	5 / 5
Workflow Clarity	A clear Prepare → Bump → Merge → Tag → Rerun → Verify sequence with an end-of-flow verification checkpoint and a Rerun recovery path exists, but it lacks explicit pre-tag validation that the bump merged cleanly and an explicit "if verify fails" feedback loop beyond rerunning.	4 / 5
Progressive Disclosure	At well under 50 lines with a single purpose and no need for external references, the cleanly sectioned headers (Prepare, Bump, Merge, Tag, Rerun, Verify) satisfy the simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

53%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 concise and third-person with a clear "what", but it lacks any "when to use" trigger guidance and omits common release-related keywords like "release" or "publish", limiting its discovery and completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when cutting a release: bumping versions, tagging, and verifying the published release.'

Include natural trigger terms users actually say, such as 'release', 'publish', 'version bump', and 'cut a release'.

Tighten the "what" by naming concrete operations (e.g. 'bump versions, tag the commit, trigger the release workflow, and verify the published release') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names three concrete release actions ("versioning, tagging, and verification") but they remain high-level and generic rather than enumerating specific operations like bump commands or tag pushing.	3 / 5
Completeness	It states a clear "what" ("Step through versioning, tagging, and verification") but provides no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	"versioning, tagging, and verification" are relevant keywords but it omits common natural terms users say such as "release", "publish", "version bump", or "cut a release".	3 / 5
Distinctiveness Conflict Risk	The phrase clearly signals a release-workflow niche that is mostly distinct from other skills, with only minor overlap risk against general git skills, though "verification" alone is somewhat generic.	4 / 5
	Total	13 / 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: Devin-AXIS/iPolloWork
Path: .opencode/skills/release/SKILL.md
Commit: 52934c1

Reviewed: about 14 hours 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.