Name: vote-open
Rating: 72 (1 reviews)
Author: helium

vote-open

Start the voting process for a Helium Release Proposal. Creates the vote summary gist, opens a PR against helium/helium-vote, and updates the HRP status to Frozen. Use when the user says "open voting", "start the vote", "create the vote", "put it to vote", "kick off voting", or it's time to submit an HRP for community vote.

Quality

88%

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

77%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 highly actionable with a clearly sequenced, checkpointed workflow, but it loses token efficiency to a duplicated concrete example and does not leverage progressive disclosure. Tightening the example and possibly externalizing the templates would raise the two lowest dimensions.

Suggestions

Trim or remove the concrete April 2026 example (lines 89-113), which duplicates the with-features template almost line-for-line; a single filled-in feature line plus a note on the filename format would preserve clarity while saving ~20 lines.

Move time-sensitive example values (the 2026-04 date, the 20260401-core-devs.md filename, the specific feature name) out of the main flow or into a clearly marked example block, since hardcoded dates and version strings will go stale.

Consider extracting the two vote-summary templates into a references/ file (e.g. references/vote-summary-templates.md) linked from step 2, giving SKILL.md a leaner overview with a one-level-deep reference structure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and domain-specific, but the concrete April 2026 example duplicates the with-features template almost line-for-line, and it hardcodes time-sensitive values (2026-04, 20260401-core-devs.md) outside any deprecated/old-patterns section. It is not a 3 because of that redundant ~23-line duplicate; not a 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Provides fully executable commands with exact script paths and all flags (gh-hiptron.sh gist create, vote-pr.sh --month/--gist-url/--hrp-file, lookup-vote-url.sh --month), exact commit messages, exact frontmatter fields, and copy-paste-ready templates. It is not a 2 because the guidance is complete and executable rather than pseudocode with missing details.	3 / 3
Workflow Clarity	A clear numbered 7-step sequence with explicit validation checkpoints (step 1 confirmation prompt; step 2 'Show the generated summary to the user for confirmation before creating the gist'), error recovery in step 7, and rollback guidance in the step 5 note. It is not a 2 because checkpoints are explicit, not implicit; the destructive/batch cap does not apply since this is a reversible status update.	3 / 3
Progressive Disclosure	A single ~175-line monolithic file with no reference files (references/, scripts/, assets/ are absent); it is well-sectioned (not a wall of text, so not a 1) but over 50 lines with no overview-to-reference split, and the redundant inline concrete example adds bulk. It is not a 3 because nothing is split into one-level-deep references.	2 / 3
	Total	10 / 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.

An excellent description: it states three concrete actions, supplies five natural user trigger phrases, and clearly covers both what and when within a distinct governance niche. No weaknesses to address.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — 'Creates the vote summary gist, opens a PR against helium/helium-vote, and updates the HRP status to Frozen' — matching the multiple-specific-actions anchor. It is not a 2 because the actions are comprehensive rather than partial, and the voice is third person so no specificity penalty applies.	3 / 3
Completeness	Explicitly answers what (the three actions) and when (an explicit 'Use when the user says...' clause with triggers). It is not a 2 because the 'when' is stated explicitly rather than merely implied.	3 / 3
Trigger Term Quality	Provides five natural phrasings a user would say ('open voting', 'start the vote', 'create the vote', 'put it to vote', 'kick off voting') plus 'submit an HRP for community vote'. This exceeds the anchor-2 bar of 'some relevant keywords but missing common variations'.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow Helium-governance niche ('Helium Release Proposal', 'helium/helium-vote', 'HRP status to Frozen') with distinct triggers unlikely to overlap other skills. It is not a 2 because the niche and triggers are highly specific rather than broadly overlapping.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: helium/helium-release-proposals
Path: .claude/plugins/hrp/skills/vote-open/SKILL.md
Commit: d42a6cc

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