Skip to content
cccskills
FreePublished on GitHub

release-telegram-post

Create a Telegram-ready Neva release announcement from a GitHub release payload. Use for official Neva Telegram release posts.

The English summary is being prepared. Showing the original description.

Works withTelegramGitHub
See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

go

Free

Use for Go changes in Neva: authoring, refactoring, debugging, or review.

The English summary is being prepared. Showing the original description.

nevalang/neva1.1KUpdated Aug 23, 2026

Use for Neva source or snippets: authoring, refactoring, debugging, or review.

The English summary is being prepared. Showing the original description.

nevalang/neva1.1KUpdated Aug 23, 2026

Convert Neva programs to valid Mermaid flowchart diagrams. Use when asked to visualize Neva code as Mermaid.

The English summary is being prepared. Showing the original description.

nevalang/neva1.1KUpdated Aug 23, 2026

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

The English summary is being prepared. Showing the original description.

nevalang/neva1.1KUpdated Aug 23, 2026

Create a Discord-ready Neva release announcement from a GitHub release payload. Use for official Neva Discord release posts.

The English summary is being prepared. Showing the original description.

nevalang/neva1.1KUpdated Aug 23, 2026

Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts. Use this for monthly release preparation in nevalang/neva.

The English summary is being prepared. Showing the original description.

nevalang/neva1.1KUpdated Aug 23, 2026

See all skills by nevalang

Report a problem with this skill