Agent skill

Release Telegram Post

by nevalang in nevalang/neva

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

MITAuto-check passedDevelopment

Install Release Telegram Post

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

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

GitHub CLI
$ gh skill install nevalang/neva release-telegram-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-telegram-post .claude/skills/release-telegram-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-telegram-post
GitHub stars
1.1k
Token cost
~439 tokens
SKILL.md length
234 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 8 steps: Read the release context from the… → Read .codex/shared/release-marketing.md… → Produce a concise Telegram post in… → …
  • Official Neva Telegram 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 Telegram Post is an agent skill from nevalang/neva. Create a Telegram-ready Neva release announcement from a GitHub release payload. Use for official Neva Telegram release posts.

Its SKILL.md is about 440 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 Telegram 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 Telegram release posts
  • Tasks that involve Changelog and release notes

Example prompts

  • “/release-telegram-post”

Workflow steps

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

  1. Read the release context from the prompt: repository, tag, release name,
  2. Read .codex/shared/release-marketing.md for positioning, CTA, and tone
  3. Produce a concise Telegram post in English using this high-level structure
  4. Keep each highlight line short, concrete, and scannable.
  5. Make the post ambitious and clear, not dry and not hypey.
  6. Use Telegram HTML formatting only (, , ,
  7. Keep the message easy to scan and under 1500 characters.
  8. 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 Telegram Post loads about 439 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 234 words of instructions outside code blocks.

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

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). 234 words, ~439 tokens.

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

Release Telegram Post

Create a Telegram-ready release announcement in English for the Neva community group.

Workflow

  1. Read the release context from the prompt: repository, 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 Telegram post in English using this high-level structure:
    • Line 1: Neva vX.Y - Release Title
    • Line 2: standalone release URL
    • Short intro paragraph, 1-2 sentences max; state whether there are language-level breaking changes when the notes make that clear
    • Highlights: label
    • 6-8 short numbered highlight lines using emoji numerals
    • Final CTA paragraph with repo star/share/Open Collective links
  4. Keep each highlight line short, concrete, and scannable.
  5. Make the post ambitious and clear, not dry and not hypey.
  6. Use Telegram HTML formatting only (<b>, <i>, <code>, <a href="...">).
  7. Keep the message easy to scan and under 1500 characters.
  8. Save output to the exact file path requested by the caller.

Output Rules

  • Return only the final Telegram message body in the file.
  • Do not add wrappers like "Here is your post", "Result:", or "Output:".
  • Do not add YAML frontmatter, surrounding quotes, code fences, or unsupported HTML tags.
  • Do not reduce the project description to a dry list of technical facts unless they support a stronger product point.
  • Do not bury the release URL inside the CTA paragraph; it should appear near the top as a standalone line.

© 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-telegram-post of nevalang/neva.

Open the folder on GitHubat commit 127afd9

Compare with similar skills

Release Telegram 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 Telegram Post compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Telegram Post this skillnevalang/neva1.1k—~439Automated safety check: PassMIT
Takopi Releasebanteg/takopi1k—~734Automated safety check: PassMIT
Keen Pbr Release Postmaksimkurb/keen-pbr139—~844Automated safety check: PassGPL-3.0
Releasepwrdrvr/openclaw-codex-app-server265—~2.2kAutomated safety check: PassMIT
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Mole CLI Release Flowtw93/Mole70k—~2.5kAutomated safety check: PassGPL-3.0

Similar skills

  • Takopi Release

    banteg/takopi

    Prepare and ship a Takopi release. An agent skill from banteg/takopi.

    1k GitHub stars~734 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Keen Pbr Release Post

    maksimkurb/keen-pbr

    Draft keen-pbr release posts for GitHub and Telegram from git history.

    139 GitHub stars~844 tokensUpdated today
    DevelopmentAuto-check passed
  • 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
  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed

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 Discord-ready Neva release announcement from a GitHub release payload.

    1.1k GitHub stars~500 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 Telegram Post

What does Release Telegram Post do?

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

When should I use Release Telegram Post?

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

How do I install Release Telegram Post in Claude Code?

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

How do I install Release Telegram Post in Codex?

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

Can I use Release Telegram 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-telegram-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-telegram-post, .gemini/skills/release-telegram-post, .github/skills/release-telegram-post and .opencode/skills/release-telegram-post in your project.

What does Release Telegram Post need to run?

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

Does Release Telegram 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 Telegram 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 Telegram Post use?

Release Telegram 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 Telegram Post use?

About 439 tokens (SKILL.md is roughly 1.8k 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 Telegram Post?

Skills that share tags, products or a category with Release Telegram Post: Takopi Release (banteg/takopi, 1k stars), Keen Pbr Release Post (maksimkurb/keen-pbr, 139 stars), Release (pwrdrvr/openclaw-codex-app-server, 265 stars) and Cutting A Release (TriliumNext/Trilium, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Telegram Post?

nevalang (a GitHub organization) maintains it in nevalang/neva, which has 1,083 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.