releasing-plugin-versions

Use when releasing a new plugin version, bumping versions, creating git tags, or publishing GitHub releases for this marketplace

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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

The body is concise, highly actionable, and well-organized for a simple release-procedure skill. The main gap is the absence of validation/verification checkpoints before irreversible steps like pushing tags and publishing releases.

Suggestions

Add a pre-tag verification step that confirms all 4 version locations were updated (e.g., re-list the locations as a checklist to tick before running git tag) to catch partial updates before the irreversible push.

Add a tag-format validation checkpoint (run 'git tag --sort=-v:refname | head -5' and confirm the new tag matches the existing vMAJOR.MINOR.PATCH pattern) before 'git push && git push origin v1.3.0'.

Include a short error-recovery note for the push/release steps (e.g., how to delete and recreate a misformed tag before it is published) to close the destructive-operation feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven with no padding and no explanation of concepts Claude already knows; every section earns its place. It is not 2 because there is no unnecessary exposition to tighten.	3 / 3
Actionability	Provides copy-paste-ready, executable bash commands for the full release flow (git commit/tag/push, gh release create) with a concrete template and exact tag format. It is not 2 because the code is real and complete rather than pseudocode.	3 / 3
Workflow Clarity	The sequence is clearly numbered (stage -> commit -> tag -> push -> release), but destructive/published operations (pushing tags, creating releases) and the 4-location version update lack explicit validation checkpoints or error-recovery feedback loops, which the rubric caps at 2 for batch/destructive workflows.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a single-purpose, well-sectioned document; per the simple-skills note, well-organized sections with no need for external references can score 3.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, trigger-led, and specific, clearly answering both what the skill does and when to use it. It is among the stronger examples with no notable fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'releasing a new plugin version, bumping versions, creating git tags, or publishing GitHub releases' — matching the multiple-specific-actions anchor rather than the partial domain-only anchor at 2.	3 / 3
Completeness	An explicit 'Use when ...' clause answers when, and the enumerated actions answer what, satisfying the both-what-and-what-when anchor; it is not capped at 2 because the trigger guidance is explicit rather than merely implied.	3 / 3
Trigger Term Quality	Terms like 'releasing', 'bumping versions', 'git tags', and 'GitHub releases' are natural phrasings a user would say when needing this skill, giving good coverage; it is not 2 because the keywords are common variations rather than a single generic term.	3 / 3
Distinctiveness Conflict Risk	Scoping to 'plugin version' and 'this marketplace' carves a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 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: ivan-magda/claude-superpowers
Commit: af7cba7

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