CtrlK
BlogDocsLog inGet started
Tessl Logo

post

Invoke this skill to post or comment on Reddit (r/HeliumNetwork) about Helium Release Proposals. This is the Reddit posting skill — it creates new announcement threads and adds update comments to existing ones. ALWAYS invoke for: "post it", "announce it", "let people know", "send a reminder", "notify the community" when the context involves an HRP, release, vote, or feature. ALWAYS invoke when the user says "the vote is live", "voting is open", "vote went live", "multisig signed" — these mean it's time to post the vote-live reminder on Reddit. These phrases default to Reddit unless the user explicitly says Twitter, email, or blog. ALWAYS invoke when the user mentions Reddit, subreddit, r/HeliumNetwork, or "the thread" alongside any HRP or release content. ALWAYS invoke when someone wants to communicate a release, vote reminder, or feature update to the Helium community without naming a specific platform — Reddit is the default community channel. DO NOT invoke for: drafting blog posts, sending emails, posting on Twitter/X, reviewing PRs, creating release files, or just looking up a reddit-post-id.

Invalid
This skill can't be scored yet
Validation errors are blocking scoring. Review and fix them to unlock Quality, Impact and Security scores. See what needs fixing →
SKILL.md
Quality
Evals
Security

HRP Reddit Post Skill

You help post Helium Release Proposals to r/HeliumNetwork. Each HRP gets one Reddit post (the initial announcement). All subsequent updates (new features added, vote reminders, etc.) are posted as comments on that original post to keep discussion in one thread.

The Reddit post ID is tracked in the release file's YAML frontmatter (reddit-post-id field), so it's visible in the repo and any contributor can post follow-ups.

Script location

${CLAUDE_PLUGIN_ROOT}/scripts/reddit-post.py

Steps

1. Identify the target HRP

  • If the user specifies a month, find that specific HRP file
  • Otherwise, find the most recent active HRP — look for the file with the latest vote-date whose status is not Released
  • Read the full HRP file contents
  • Note the release filename (e.g. releases/20260401-core-devs.md)

If the HRP has no real features (empty Roadmap Features, or only placeholder text like "no protocol updates"), tell the user there's nothing to announce yet and stop. Don't post an empty announcement.

2. Determine new post vs update

Check the release file's frontmatter for a reddit-post-id field:

  • No reddit-post-id → this is a new HRP that hasn't been announced yet. Create a new Reddit post.
  • Has reddit-post-id → a post already exists. Post a comment on the existing thread.

You can also verify programmatically:

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/reddit-post.py" lookup --file releases/YYYYMMDD-core-devs.md

3. Format the content

Tone: casual and community-friendly. This is a subreddit, not a boardroom. Write like a team member talking to the community — conversational, plain language, no jargon or corporate-speak.

New announcement (no reddit-post-id)

Title format: HRP {Month Year} is up — here's what's in it

Body structure:

Hey everyone, the {Month Year} Helium Release Proposal is out and ready for your review.

**What's in this release:**

{For each feature, write a plain-language 2-3 sentence explanation. Pull from the Motivation section but rephrase it like you're explaining to a community member, not a developer.}

**Key dates:**
- Vote opens: ~{vote-date formatted naturally}
- Target release: {release-date formatted naturally}

Check out the [full proposal](https://github.com/helium/helium-release-proposals/blob/main/releases/{filename})

Questions or feedback? Drop them in the comments — we want to hear from you before the vote goes live.

Concrete example — here's what the April 2026 HRP post would look like:

Title: HRP April 2026 is up — here's what's in it

Body:

Hey everyone, the April 2026 Helium Release Proposal is out and ready for your review.

**What's in this release:**

**1. Staked HNT Position Transfers** — Right now, if you've staked HNT and need to move your position to a different wallet (say, because your wallet got compromised or you want to move to a cold wallet), you're stuck waiting for the full unlock period. This release adds the ability to transfer staked positions directly between wallets without unstaking. Your lock duration, staked amount, and rewards all stay exactly the same — only the owning wallet changes.

**Key dates:**
- Vote opens: ~March 20th
- Target release: April 1st

Check out the [full proposal](https://github.com/helium/helium-release-proposals/blob/main/releases/20260401-core-devs.md)

Questions or feedback? Drop them in the comments — we want to hear from you before the vote goes live.

Update comment (has reddit-post-id)

Ask the user what changed if it's not obvious from context. Format as a comment on the existing thread:

For a new feature added:

**Update: {Feature Name} added**

{Plain-language 2-3 sentence explanation of the feature and why it matters.}

[Updated proposal](https://github.com/helium/helium-release-proposals/blob/main/releases/{filename})

For a vote-live announcement (only post once the on-chain proposal is active and voting is live):

**Heads up: voting is live for HRP {Month Year}**

Quick recap of what's in this release:

{numbered list in plain language}

Voting is open for 7 days. You can vote in the [Helium Wallet](https://wallet.helium.com) app or at [heliumvote.com](https://www.heliumvote.com).

After posting a vote-live update, set vote-live-date: {YYYY-MM-DD} (today's date) in the HRP frontmatter and commit to main with message: Record vote-live-date for HRP {Month Year}. This date is used to calculate when the 7-day voting window closes.

For a vote-ending-soon reminder (post ~2 days before the vote closes, i.e. around day 5 of the 7-day window). Calculate the end date from vote-live-date + 7 days:

**Reminder: voting for HRP {Month Year} closes on {end date}**

If you haven't voted yet, now's the time. Here's what's in this release:

{numbered list in plain language}

Vote in the [Helium Wallet](https://wallet.helium.com) app or at [heliumvote.com](https://www.heliumvote.com).

If no vote-live-date is set, ask the user when voting started to calculate the end date.

4. Confirm with user

Always show the full formatted title (if new) and body to the user and get explicit confirmation before posting. The user may want to adjust wording, add context, or change tone.

5. Post or comment

For a new announcement:

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/reddit-post.py" post \
  --file "releases/YYYYMMDD-core-devs.md" \
  --title "the title" \
  --body "the body"

This writes the reddit-post-id into the release file's frontmatter. After posting, commit the frontmatter change so the post ID is tracked in the repo.

For an update (comment on existing post):

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/reddit-post.py" update \
  --file "releases/YYYYMMDD-core-devs.md" \
  --body "the comment body"

The script reads the reddit-post-id from frontmatter and posts a comment on that thread.

6. Report result and commit

After posting:

  • Report the URL back to the user
  • If this was a new post, the release file was modified (frontmatter now has reddit-post-id). Commit this change directly to main with message: Add reddit-post-id for HRP {Month Year}

Credential setup

If credentials are missing, the script will error with details. Tell the user:

  1. Log in to Reddit as HeliumConsoleTeam
  2. Go to https://www.reddit.com/prefs/apps/ → create a script type app
  3. Create ~/.config/hrp/reddit.env:
    REDDIT_CLIENT_ID=your_client_id
    REDDIT_CLIENT_SECRET=your_client_secret
    REDDIT_USERNAME=HeliumConsoleTeam
    REDDIT_PASSWORD=your_password
Repository
helium/helium-release-proposals
Last updated
Created

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.