CtrlK
BlogDocsLog inGet started
Tessl Logo

release

Mark a Helium Release Proposal as deployed. Updates the HRP status to Released and records the deployment date. Use when the user says "the release is deployed", "mark it as released", "it's live", "we shipped the release", "deployment is done", or wants to close out an approved HRP after the network deployment. Also handles no-change months where no vote was needed — use when the user says "no changes this month", "skip this release", or "nothing to deploy".

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A compact, well-sequenced instruction-only skill with explicit status guards and a confirmation gate, and no unnecessary explanation. Its main weakness is that the file-discovery step is under-specified, leaving Claude without the HRP file location or naming pattern.

Suggestions

In Step 1, state where HRP files are stored and their naming pattern (e.g., path and filename format) so the 'find the HRP' instruction is executable rather than abstract.

Add a brief verification step after the commit (e.g., confirm the frontmatter now reads 'status: Released' and the README entry landed) to close the loop on the destructive-to-main commit.

Clarify the default for 'released-date' on the no-change path when no 'planned release-date' exists, since the instruction currently offers two fallbacks without a tiebreaker.

DimensionReasoningScore

Conciseness

Lean body that assumes competence — it does not explain what an HRP, Helium, or Solana is; status-guard messages and confirmation templates each earn their place. Not level 2 because there is no padding or redundant explanation.

3 / 3

Actionability

Concrete where it counts (exact frontmatter fields 'status: Released', 'released-date: {YYYY-MM-DD}', 'released-txid', commit-message templates, README insertion block), but Step 1 says 'find the HRP' without stating where these files live or their naming convention — incomplete guidance. Not level 3 because a key instruction is not copy-paste executable.

2 / 3

Workflow Clarity

Clear sequence (Steps 1, 2a, 2b, 3) with an explicit status-guard validation checkpoint that routes wrong states and a confirmation gate before the mutating commit. Not level 2 because validation checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

A single, simple, well-organized file with no nested references; per the simple-skills note, well-organized sections suffice for progressive disclosure at 3 when no external references are needed.

3 / 3

Total

11

/

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.

A strong, third-person description that names concrete actions and supplies an unusually rich set of natural trigger phrases for both the normal release and no-change-month paths. It clearly answers what and when with minimal padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Updates the HRP status to Released and records the deployment date' plus handling 'no-change months' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (mark deployed, update status, record date, handle no-change months) and when via repeated 'Use when...' clauses with concrete triggers.

3 / 3

Trigger Term Quality

Extensive natural trigger phrases a user would actually say: 'the release is deployed', 'mark it as released', 'it's live', 'we shipped the release', 'no changes this month', 'skip this release', 'nothing to deploy'.

3 / 3

Distinctiveness Conflict Risk

Narrow HRP-release niche with distinct, domain-specific triggers; unlikely to fire for unrelated skills. Uses correct third person voice ('Mark', 'Updates', 'handles').

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
helium/helium-release-proposals
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.