skillshare-release

End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASE_NOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version. For changelog-only tasks, use /changelog instead.

Quality

94%

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

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.

The content is a well-sequenced, actionable release runbook with strong validation checkpoints and a clear confirmation gate. Its main weakness is redundancy between the inline phase guidance and the trailing Rules section, plus release-notes wording detail that could live in a reference file.

Suggestions

Remove the "## Rules" entries that restate inline phase guidance (e.g. "Fix, don't skip", "Release notes stay local by default", "Ask before push"); keep only rules that add new information not already covered in a phase.

Move the detailed release-notes wording rules and good/bad examples (Phase 3) into a references/RELEASE_NOTES_GUIDE.md and link to it, reducing SKILL.md length and improving progressive disclosure.

Consolidate the two places that specify the commit message format (Phase 5 and Rules) into a single canonical statement to avoid drift.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence, but the "## Rules" section repeats guidance already stated inline in Phases 1 and 3 (e.g. "Fix, don't skip" and "Release notes stay local by default"), which could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (make check, /changelog $VERSION, git add/commit/tag/push with exact paths and commit-message format), and the release-notes structure gives explicit actionable templates.	5 / 5
Workflow Clarity	A clear seven-phase sequence with explicit checkpoints: test validation with a fix-and-re-run feedback loop (Phase 1), "Review the output before proceeding" (Phase 2), and a user-confirmation gate before push (Phase 7) — appropriate validation for the destructive git operations.	5 / 5
Progressive Disclosure	Well-organized into clearly headed phases with no nested references, and the skill is appropriately self-contained; however it runs over 50 lines with no external bundle to offload the detailed wording rules, which keeps it just short of the ideal split.	4 / 5
	Total	18 / 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.

The description is third-person, concise, and clearly states both capability and trigger conditions with natural user phrasing. It also disambiguates a closely related skill, which strengthens distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Runs tests, generates changelog (via /changelog), optionally writes local RELEASE_NOTES, updates version numbers, commits, and drafts announcements" — covering the release workflow comprehensively.	5 / 5
Completeness	Explicitly answers both what (the end-to-end release steps) and when (the quoted trigger phrases and "any request to publish a new version") with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural trigger phrases users would actually say are given verbatim — "release", "prepare release", "cut a release", "release v0.19" — plus a disambiguating "For changelog-only tasks, use /changelog instead."	5 / 5
Distinctiveness Conflict Risk	Scoped to a named niche (skillshare release) with distinct triggers and an explicit hand-off to /changelog for changelog-only work, minimizing overlap with other 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: runkids/skillshare
Path: .skillshare/skills/skillshare-release/SKILL.md
Commit: e535e8f

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.