Agent skill

Release Discord Post

by nevalang in nevalang/neva

Create a Discord-ready Neva release announcement from a GitHub release payload.

MITAuto-check passedDevelopment

Install Release Discord Post

skills CLI
$ npx skills add nevalang/neva --skill release-discord-post -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nevalang/neva release-discord-post --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nevalang/neva.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/release-discord-post .claude/skills/release-discord-post && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-discord-post
GitHub stars
1.1k
Token cost
~500 tokens
SKILL.md length
270 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Create a Discord-ready Neva release announcement from a GitHub release payload.

  • Works in 9 steps: Read the release context from the… → Read .codex/shared/release-marketing.md… → Produce a concise Discord post in… → …
  • Official Neva Discord release posts
  • SKILL.md covers Workflow and Output Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Release Discord Post is an agent skill from nevalang/neva. Create a Discord-ready Neva release announcement from a GitHub release payload. Use for official Neva Discord release posts.

Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Discord and GitHub. The repository describes itself as: Dataflow programming language where you write a program as a message-passing graph and everything runs in parallel by default. It has strong static types, compiles to machine… The licence is MIT.

When your agent uses it

  • Official Neva Discord release posts
  • Tasks that involve Changelog and release notes

Example prompts

  • “/release-discord-post”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Read the release context from the prompt: repository, target channel name,
  2. Read .codex/shared/release-marketing.md for positioning, CTA, and tone
  3. Produce a concise Discord post in English using this high-level structure
  4. Keep the intro and bullets grounded in the actual release notes. If the notes
  5. Optimize for Discord readability: plain text or light Markdown, short
  6. Keep the tone clear, sharp, mildly energetic, and community-facing. Avoid
  7. Use @everyone only when the caller explicitly asks for it.
  8. Keep the message under 1800 characters.
  9. Save output to the exact file path requested by the caller.

What it can do on your machine

Read from SKILL.md and the folder at commit 127afd9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Discord Post loads about 500 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 270 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~500

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nevalang/neva at commit 127afd9, republished under its MIT licence (© nevalang). 270 words, ~500 tokens.

Download SKILL.mdSave it as .claude/skills/release-discord-post/SKILL.md (or your agent's skills folder).
name
release-discord-post
description
Create a Discord-ready Neva release announcement from a GitHub release payload. Use for official Neva Discord release posts.

Release Discord Post

Create a Discord-ready release announcement in English for the target Neva Discord news-style channel provided by the caller.

Workflow

  1. Read the release context from the prompt: repository, target channel name, tag, release name, release URL, and release notes.
  2. Read .codex/shared/release-marketing.md for positioning, CTA, and tone guidance.
  3. Produce a concise Discord post in English using this high-level structure:
    • Line 1: release heading like Neva vX.Y.Z or Neva vX.Y.Z - Release Title
    • Optional short punchy framing line when the release has a clear theme
    • Short intro paragraph, 1-2 sentences max
    • Highlights or What shipped label
    • 4-8 short bullet lines with the most relevant release changes
    • Full notes: label or short CTA line
    • Final line: release URL by itself
  4. Keep the intro and bullets grounded in the actual release notes. If the notes are sparse, stay conservative and do not invent features or guarantees.
  5. Optimize for Discord readability: plain text or light Markdown, short paragraphs, scannable bullets, no Telegram-style HTML.
  6. Keep the tone clear, sharp, mildly energetic, and community-facing. Avoid corporate phrasing and overselling.
  7. Use @everyone only when the caller explicitly asks for it.
  8. Keep the message under 1800 characters.
  9. Save output to the exact file path requested by the caller.

Output Rules

  • Return only the final Discord message body in the file.
  • Do not add wrappers like "Here is your post", "Result:", or "Output:".
  • Do not add YAML frontmatter, surrounding quotes, or code fences.
  • Do not bury the release URL inside another sentence; keep it on its own final line.
  • Prefer short, high-signal bullets over exhaustive coverage of every patch note.

© nevalang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/release-discord-post of nevalang/neva.

Open the folder on GitHubat commit 127afd9

Compare with similar skills

Release Discord Post next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Discord Post compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Discord Post this skillnevalang/neva1.1k—~500Automated safety check: PassMIT
Releasepwrdrvr/openclaw-codex-app-server265—~2.2kAutomated safety check: PassMIT
Writing Release NotesGoneTone/genshin-impact-wish-gacha-analyzer152—~1.6kAutomated safety check: PassMIT
Subwave Discord Releaseperminder-klair/subwave1.4k—~2.3kAutomated safety check: PassMIT
Beta Prereleaservdbreemen/OTGW-firmware207—~2.7kAutomated safety check: PassGPL-3.0
Release MaintainerUndertone0809/rudder292—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Release

    pwrdrvr/openclaw-codex-app-server

    Plan and publish a GitHub Release in a tag-driven repository.

    265 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Writing Release Notes

    GoneTone/genshin-impact-wish-gacha-analyzer

    A skill your agent uses when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer).

    152 GitHub stars~1.6k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Subwave Discord Release

    perminder-klair/subwave

    Draft a Discord release announcement for SUB/WAVE from a release PR, tag, or version number.

    1.4k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Beta Prerelease

    rvdbreemen/OTGW-firmware

    Publish an OTGW-firmware beta prerelease — bump VERSIONPRERELEASE, push to otgw-1.x.x, tag, and let CI build + publish the GitHub prerelease

    207 GitHub stars~2.7k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Release Maintainer

    Undertone0809/rudder

    A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…

    292 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Release

    LanternOps/breeze

    A skill your agent uses when cutting, shipping, or announcing a Breeze RMM release — "cut a release", "ship vX.Y.Z", "release notes for X", "what do self-hosters need to know", "draft the release…

    132 GitHub stars~9.8k tokensUpdated today
    DevelopmentAuto-check: notes

More from nevalang/neva

All 8 skills in this repo
  • Neva To Mermaid

    nevalang/neva

    Convert Neva programs to valid Mermaid flowchart diagrams. An agent skill from nevalang/neva.

    1.1k GitHub stars~795 tokensUpdated 1 mo ago
    Auto-check passed
  • Release Neva

    nevalang/neva

    Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts.

    1.1k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Create a Telegram-ready Neva release announcement from a GitHub release payload.

    1.1k GitHub stars~439 tokensUpdated 1 mo ago
    Auto-check passed
  • Papercut

    nevalang/neva

    Capture or triage small Neva repository and engineering-harness frictions without derailing feature work.

    1.1k GitHub stars~400 tokensUpdated 1 mo ago
    Auto-check passed
  • Review

    nevalang/neva

    A skill your agent uses for focused review of a Neva pull request, branch, diff, or patch.

    1.1k GitHub stars~382 tokensUpdated 1 mo ago
    Auto-check passed
  • Go

    nevalang/neva

    A skill your agent uses for Go changes in Neva: authoring, refactoring, debugging, or review.

    1.1k GitHub stars~388 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Release Discord Post

What does Release Discord Post do?

Create a Discord-ready Neva release announcement from a GitHub release payload. Release Discord Post is an agent skill from nevalang/neva. Create a Discord-ready Neva release announcement from a GitHub release payload.

When should I use Release Discord Post?

Release Discord Post fits situations like: official Neva Discord release posts; tasks that involve Changelog and release notes.

How do I install Release Discord Post in Claude Code?

Run `npx skills add nevalang/neva --skill release-discord-post -a claude-code`. Or copy the skill folder (.codex/skills/release-discord-post in nevalang/neva) into .claude/skills/release-discord-post in your project. Claude Code loads it when a task matches its description.

How do I install Release Discord Post in Codex?

Run `npx skills add nevalang/neva --skill release-discord-post -a codex`. Or copy the skill folder (.codex/skills/release-discord-post in nevalang/neva) into .agents/skills/release-discord-post in your project. Codex loads it when a task matches its description.

Can I use Release Discord Post in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nevalang/neva --skill release-discord-post -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-discord-post, .gemini/skills/release-discord-post, .github/skills/release-discord-post and .opencode/skills/release-discord-post in your project.

What does Release Discord Post need to run?

SKILL.md names no scripts, command-line tools or credentials: Release Discord Post is instructions for the agent only.

Does Release Discord Post access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Release Discord Post safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Discord Post use?

Release Discord Post is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Discord Post use?

About 500 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Discord Post?

Skills that share tags, products or a category with Release Discord Post: Release (pwrdrvr/openclaw-codex-app-server, 265 stars), Writing Release Notes (GoneTone/genshin-impact-wish-gacha-analyzer, 152 stars), Subwave Discord Release (perminder-klair/subwave, 1.4k stars) and Beta Prerelease (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Discord Post?

nevalang (a GitHub organization) maintains it in nevalang/neva, which has 1,085 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 23, 2026.

Source: nevalang/neva on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.