Record the result of a Helium Release Proposal community vote. Updates the HRP status to Approved (or back to Proposed if the vote failed), adds the vote URL, updates the README with the result, and posts a Reddit comment. Use when the user says "the vote passed", "record the vote result", "close the vote", "the vote is done", "update the HRP with the vote result", or mentions a heliumvote.com URL for an HRP. Also handles cancelling a vote that never started (reverting Frozen back to Proposed).
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
You record the outcome of a Helium Release Proposal community vote and update all the tracking surfaces — the release file, the README, and the Reddit thread.
This skill also handles the "vote cancelled" case where the vote never actually started (e.g. the helium-vote PR was rejected or the multisig didn't sign).
status: Frozen — this is the one with an active or recently completed voteStatus guard: This skill only operates on Frozen HRPs. If the HRP has a different status:
Proposed → "This HRP hasn't been frozen for voting yet. Run /hrp:vote-open first."Approved → "This HRP's vote result has already been recorded."Released → "This HRP has already been released."Run the lookup script to get the vote URL and results directly from the on-chain proposal:
"${CLAUDE_PLUGIN_ROOT}/scripts/lookup-vote-url.sh" --month "{YYYY-MM}" --resultsThis returns JSON with url, publicKey, forPercent, againstPercent, and totalVeHNT.
If the script returns an error (proposal not found or RPC failure), fall back to asking the user for the vote URL and percentage manually.
If the frontmatter already has a vote-url, use that instead of querying the chain.
Use the on-chain results to determine the outcome automatically:
Present the results to the user for confirmation: "The on-chain vote shows {forPercent}% approval ({totalVeHNT} veHNT). Record this as [passed/failed]?"
If the user says the vote was cancelled (never went live), skip to step 4c.
The vote URL and percentage come from the lookup script. The date defaults to today unless the user specifies otherwise.
Update frontmatter:
status: Approvedvote-url: {heliumvote.com URL}Update README — insert a new line into the vote history list. The list lives between the intro paragraph and the "How to Contribute" section. Insert at the top of the list (newest first), matching the existing format exactly:
- HRP {YYYY-MM} passed with [{X}% of the vote]({vote-url}) on {Month Dth Year}Nudge the user to post a Reddit comment (if reddit-post-id exists). Provide:
https://www.reddit.com/comments/{id}/ (strip t3_ prefix from the post ID)**HRP {Month Year} passed!**
The community approved this release with {X}% of the vote. Deployment is expected within the next few days.
Thanks to everyone who participated in the vote!
[Vote results]({vote-url})Same data sources as 4a (URL, percentage from lookup script).
Update frontmatter:
status: Proposed (reverts to allow further changes)vote-url: {heliumvote.com URL} (kept for historical record)vote-summary-url and vote-pr fieldsUpdate README — same insertion point as 4a:
- HRP {YYYY-MM} failed with [{X}% of the vote]({vote-url}) on {Month Dth Year}Nudge the user to post a Reddit comment (same pattern as 4a):
**HRP {Month Year} did not pass**
The community vote concluded with {X}% approval. The proposal has been reverted to Proposed status for further discussion and revision.
[Vote results]({vote-url})No vote URL, percentage, or date needed.
Update frontmatter:
status: Proposed (reverts to allow further changes)vote-summary-url and vote-pr fieldsDo not update the README — nothing to record if no vote happened.
No Reddit comment — unless the user specifically asks for one.
Commit directly to main (the release file should already be on main by this point). Include both the release file and README (if changed) in a single commit:
Record HRP {Month Year} vote result: approved with {X}%Record HRP {Month Year} vote result: failed with {X}%Revert HRP {Month Year} to Proposed (vote cancelled)Tell the user:
/hrp:release to record the deployment date."/hrp:vote-open again when ready."d750301
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.