hs-release

Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.

Quality

100%

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

100%Weight 40%Scale 1-3

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, executable runbook with concrete commands, validation checkpoints, and genuinely useful pitfalls scoped to this irreversible release process. It avoids pedagogy and verbosity while remaining complete enough to execute.

Dimension	Reasoning	Score
Conciseness	Lean throughout with no concept explanations Claude already knows; every line conveys workflow-specific gotchas (the pipe-exit-status pitfall, docs- vs docs/ branch naming) that earn their tokens.	3 / 3
Actionability	Provides copy-paste-ready commands with concrete arguments — ./scripts/release.sh <version>, uv run --directory hindsight-dev generate-changelog, gh pr create — rather than abstract direction or pseudocode.	3 / 3
Workflow Clarity	Steps are explicitly sequenced (Step 0/1/2/Cleanup) with validation checkpoints for this outward-facing release (gh run list, git ls-remote --tags, npx prettier --check) and recovery guidance, matching the highest anchor despite the destructive nature of the task.	3 / 3
Progressive Disclosure	No bundle files exist, and the single self-contained SKILL.md is organized into clear, navigable sections with no need for external references; per the rubric's simple-skills note this satisfies the top anchor.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, concrete, and uses third-person imperative voice while clearly stating both capability and trigger conditions. It is among the strongest examples in the rubric's reference set.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR" — matching the anchor for listing several specific concrete actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what (cut release, open changelog+blog PR) and when ("Use when asked to..."), satisfying the highest anchor; not a 2 because the trigger clause is explicit rather than implied.	3 / 3
Trigger Term Quality	"Use when asked to cut/start a release, bump the version, or publish a new Hindsight version" covers the natural phrasings a user would say when requesting this skill.	3 / 3
Distinctiveness Conflict Risk	Scoped to a "core Hindsight release" with product-specific versioning (vX.Y.Z) and explicit triggers, giving it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

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

	Total	14 / 16 Passed

Repository: vectorize-io/hindsight
Path: .claude/skills/hs-release/SKILL.md
Commit: ed120a2

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