Name: release
Rating: 72 (1 reviews)
Author: Cloudzero

release

Cut a release of this repository (the CloudZero plugin marketplace itself — not a customer-facing plugin). Promotes every touched plugin's own `Unreleased` changelog section to a dated entry, synthesizes those changes into a new SemVer section at the top of the root `CHANGELOG.md`, bumps `.claude-plugin/marketplace.json`'s version, runs the full CI validation suite locally, tags the release, publishes a GitHub Release, and opens the companion docs PR against `Cloudzero/cloudzero-documentation`'s `v2.0` branch so customer-facing docs land in step with the code. This is a maintainer-only, repo-local skill (lives in `.claude/skills/`, not inside a `plugins/*/skills/` directory) — it is never installed by marketplace consumers. Use when told "cut a release", "release the marketplace", "ship a new version", "promote the changelog", or after merging PR(s) that need a version bump and a docs update — mirroring how v1.2.0 (the Model Right Sizer launch) shipped.

Quality

90%

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

Quality

Content

81%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 highly actionable, well-sequenced release runbook with strong validation gates and concrete commands throughout. Its main weakness is verbosity — numerous parenthetical rationales and historical justifications inflate the body beyond what the procedural steps require.

Suggestions

Tighten the justificatory asides (e.g. the direct-push-to-main precedent, the squash-commit SHA rationale, the cost-analyst 1.2.0 aside) into a single short 'Precedents / gotchas' note rather than weaving them inline.

Consider moving the 'Why this is scoped to this repo only' rationale into a brief one-liner or a separate reference file so the main body stays focused on the release steps.

Extract the per-step historical anchors (v1.0.0, v1.2.0 launch thread) into a compact 'Prior releases' reference so the procedure reads as a stable checklist rather than a narrative.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of generic concept padding, but heavy with justificatory asides and historical anecdotes (the direct-push precedent, the SHA-mismatch bug rationale, the 'Why this is scoped to this repo only' section) that could be trimmed without losing the actionable guidance.	3 / 5
Actionability	Fully executable throughout — exact commands (`git describe --tags --abbrev=0`, `git fetch origin main && git tag vX.Y.Z origin/main`, `gh release create vX.Y.Z --title ... --notes ...`), concrete file paths, and copy-ready commit messages cover the common cases.	5 / 5
Workflow Clarity	A clear 10-step sequence with explicit validation checkpoints (step 6 'All must pass before continuing', step 7 review-and-merge gate) and feedback loops for the outward-facing tag/publish steps, including the 'tag from main after merge, never the release branch' guardrail.	5 / 5
Progressive Disclosure	Well-organized into clear sections with a one-level-deep 'Related' block linking real repo files (CLAUDE.md, CONTRIBUTING.md, CHANGELOG.md); no bundle files exist, so the body inlines detail that is appropriately sectioned but not split across files.	4 / 5
	Total	17 / 20 Passed

Description

100%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 precise, third-person description that names a comprehensive set of concrete actions and pairs them with natural, synonymous trigger phrases and an explicit Use-when clause. It is long, but the length is specificity rather than fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete release actions — promote Unreleased changelog, synthesize a SemVer section, bump marketplace.json version, run CI validation, tag, publish a GitHub Release, open the docs PR — giving comprehensive coverage of the workflow.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated release actions) and 'when' (a 'Use when told...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Natural maintainer phrasing with synonyms ('cut a release', 'release the marketplace', 'ship a new version', 'promote the changelog') plus a situational trigger ('after merging PR(s) that need a version bump').	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche — releasing this specific marketplace, explicitly 'not a customer-facing plugin' and 'never installed by marketplace consumers' — minimizing overlap with plugin-level skills.	5 / 5
	Total	20 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: Cloudzero/cloudzero-claude-marketplace
Path: .claude/skills/release/SKILL.md
Commit: 62c27f3

Reviewed: 1 day 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.