vote-close
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
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 articulates specific actions, provides comprehensive trigger phrases, and occupies a very distinct niche. It covers both the primary use case (recording vote results) and edge cases (cancelling votes), making it easy for Claude to know exactly when to select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: updates HRP status, adds vote URL, updates README, posts Reddit comment, and handles vote cancellation/reversion. Very detailed about what it does. | 3 / 3 |
Completeness | Clearly answers both 'what' (records vote results, updates HRP status, adds vote URL, updates README, posts Reddit comment) and 'when' (explicit 'Use when...' clause with multiple trigger phrases and scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases: 'the vote passed', 'record the vote result', 'close the vote', 'the vote is done', 'update the HRP with the vote result', and mentions heliumvote.com URLs. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: Helium Release Proposal vote recording. The domain-specific terms (HRP, heliumvote.com, Frozen/Proposed/Approved statuses) make it extremely unlikely to conflict with other skills. | 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 workflow skill with excellent actionability — concrete commands, exact field names, format templates, and explicit thresholds. The three-way branching (passed/failed/cancelled) is clearly delineated with appropriate validation. Minor weaknesses include some verbosity in the Reddit templates and introductory text, and the lack of bundle files to offload reference content.
Suggestions
Trim the introductory paragraph — the skill name and step 1 already make the purpose clear without restating it.
Consider extracting the Reddit comment templates into a separate reference file to reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity — e.g., the intro paragraph restating the description, and the Reddit comment templates are lengthy. The status guard messages and step explanations could be tighter, though most content earns its place given the complexity of the workflow. | 2 / 3 |
Actionability | Provides concrete bash commands, exact frontmatter field changes, specific README line formats, commit message templates, and copy-paste Reddit comment text. The threshold (67%) is explicit, and fallback behavior is clearly defined. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced with explicit branching (passed/failed/cancelled), status guards at entry, a confirmation checkpoint before recording the outcome, and distinct instructions for each path including commit and reporting. The feedback loop of querying chain → presenting results → user confirmation is well-defined. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sub-steps, but it's a fairly long monolithic document. The Reddit comment templates and README format examples could potentially be referenced from separate files. However, no bundle files exist to offload to, and the inline content is reasonably organized with numbered steps and labeled branches. | 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.