vote-open
Start the voting process for a Helium Release Proposal. Creates the vote summary gist, opens a PR against helium/helium-vote, updates the HRP status to Frozen, and posts a vote reminder to Reddit. 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.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a narrow, specific workflow with concrete actions and comprehensive trigger terms. It follows best practices by using third person voice, listing specific steps, and providing an explicit 'Use when...' clause with multiple natural language variations. The domain-specific terminology ensures it won't be confused with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates the vote summary gist, opens a PR against helium/helium-vote, updates the HRP status to Frozen, and posts a vote reminder to Reddit. These are highly specific, actionable steps. | 3 / 3 |
Completeness | Clearly answers both 'what' (starts the voting process with four specific steps) and 'when' (explicit 'Use when...' clause with multiple trigger phrases and a situational trigger). Both are thoroughly addressed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'open voting', 'start the vote', 'create the vote', 'put it to vote', 'kick off voting', plus the contextual trigger 'submit an HRP for community vote'. These are natural, varied phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with domain-specific terms like 'Helium Release Proposal', 'HRP', 'helium/helium-vote', and 'vote summary gist'. This is a very clear niche that is unlikely to conflict with any other skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, highly actionable skill for a complex multi-step governance workflow. Its greatest strengths are the concrete commands, exact templates, and clear sequencing with user confirmation checkpoints. The main weakness is the repeated boilerplate across templates that inflates token usage, and the lack of external file references for the templates which would improve progressive disclosure.
Suggestions
Extract the vote summary templates into separate template files (e.g., templates/vote-summary.md and templates/vote-summary-no-change.md) and reference them from the skill, reducing repetition of the governance boilerplate
Consolidate the three template renderings (features template, no-change template, concrete example) — the concrete example alone with a note about the no-change variant would suffice, saving ~40 lines
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long but most content is necessary — the templates, examples, and step-by-step commands are domain-specific knowledge Claude wouldn't have. However, the boilerplate governance sections are repeated three times (two templates + one example), which is wasteful. The explanatory notes are generally justified but could be tightened in places (e.g., the note about frozen status and revert could be shorter). | 2 / 3 |
Actionability | Highly actionable with concrete bash commands, exact templates with placeholders, a worked example (April 2026), specific commit messages, and clear instructions for each step. The Reddit comment template is copy-paste ready. Scripts are referenced with full paths and exact flags. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with explicit checkpoints: user confirmation before proceeding (step 1), showing the summary for approval before creating the gist (step 2), and a deferred step 7 that handles the asynchronous multisig signing. Error recovery is addressed (script failure in step 7, missing reddit-post-id fallback, revert path if vote PR is rejected). The validation-before-proceeding pattern is well-implemented. | 3 / 3 |
Progressive Disclosure | The skill is a single monolithic file with no references to supporting documentation. The three full markdown templates (two templates + one concrete example) could be extracted to separate template files. The inline templates make the skill quite long. However, the structure with numbered steps and clear headers provides reasonable navigation within the single file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- helium/helium-release-proposals
- Commit
d750301
- Reviewed
Table of Contents
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.