release

Step through versioning, tagging, and verification

Quality

75%

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

100%

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

The body is a tight, fully actionable release runbook: concrete commands, exact file targets, a clear sequenced workflow with validation and a rerun feedback loop, and clean section organization with no unnecessary references. It is an exemplar of a concise instruction skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned with no concept-explaining filler; every section adds commands or concrete file paths Claude would not already know, so each token earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands (pnpm bump:patch, git tag/push, gh workflow run, gh run list, gh release view) plus the exact list of files to bump.	3 / 3
Workflow Clarity	The Prepare→Bump→Merge→Tag→Rerun→Verify sequence is explicit, with a concrete Verify validation step and a Rerun feedback loop for error recovery.	3 / 3
Progressive Disclosure	Under 50 lines and self-contained with no need for external references, the well-organized section headers satisfy progressive disclosure for a skill of this size.	3 / 3
	Total	12 / 12 Passed

Description

50%

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 identifies a coherent release-flow niche with three named actions but lacks concrete objects and any explicit "Use when" trigger guidance. It is competent but generic enough to leave both specificity and completeness at the mid level.

Suggestions

Add concrete objects to each action, e.g. "Bump package versions, tag the release commit, and verify the published GitHub release."

Append an explicit trigger clause such as "Use when cutting a release, bumping versions, or tagging and publishing a new release."

Include natural trigger terms users would say ("release", "publish", "cut a release", "bump version") to improve distinctiveness and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names three actions ("versioning, tagging, and verification") but as bare gerunds without objects, making it less concrete than the score-3 anchor which pairs verbs with targets.	2 / 3
Completeness	It states what the skill does ("Step through versioning, tagging, and verification") but provides no "Use when..." clause or equivalent trigger guidance, capping completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	"versioning, tagging, and verification" are relevant terms a user might say, but common variations like "release", "publish", or "bump version" are missing.	2 / 3
Distinctiveness Conflict Risk	The release niche (versioning + tagging + verification) is fairly specific, but without explicit triggers it could still overlap with general git or version-bump skills.	2 / 3
	Total	8 / 12 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: bd5caef

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