gem-release

Automates the complete process of releasing a new version of the openclacky Ruby gem. Supports both stable releases (auto-increment) and pre-release versions (user-specified, e.g., 1.0.0.beta.1). Handles version bumping, testing, building, RubyGems publishing, GitHub Releases, and OSS CDN mirroring.

Quality

83%

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

Quality

Content

92%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 well-structured, actionable skill body that delegates heavy logic to a script while giving the agent concrete commands, a clear sequenced workflow, and explicit error-recovery feedback loops.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence (no explanation of gems/RubyGems); minor verbosity in the summary-format template and pre-release caveat table could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands (e.g., `bash "SKILL_DIR/scripts/release.sh" <version> --prerelease`, `git describe --tags --abbrev=0`) with concrete flags covering common cases.	5 / 5
Workflow Clarity	A clearly sequenced 13-step workflow with validation checkpoints (tests, CI wait, dry-run) and explicit error-recovery feedback loops ('diagnose and fix before retrying', 'safe to retry').	5 / 5
Progressive Disclosure	SKILL.md is an overview that delegates the bulk of the release logic to the one-level-deep, clearly signaled `SKILL_DIR/scripts/release.sh` bundle, with well-organized sections and easy navigation.	5 / 5
	Total	19 / 20 Passed

Description

75%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 specific, well-scoped description that concretely enumerates the release actions, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and limits trigger guidance.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when releasing or publishing a new openclacky gem version').

Include common synonyms a user might say, such as 'publish', 'ship', or 'cut a release'.

Optionally name file extensions or artifacts (e.g., '.gem', 'gem push') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'version bumping, testing, building, RubyGems publishing, GitHub Releases, and OSS CDN mirroring' — with comprehensive coverage matching the score-5 anchor.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no 'when'/'Use when' clause; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural phrases a user would say ('releasing a new version', 'pre-release versions') plus domain terms, but misses common synonyms and lacks explicit 'Use when' trigger phrasing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — releasing the openclacky Ruby gem — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 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: clacky-ai/openclacky
Path: .clacky/skills/gem-release/SKILL.md
Commit: db23154

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.