agentleFS
Sign inStart free
WireCatLabsWireCatLabs/cli-docs/skills/release-announcement/SKILL.md

release-announcement

Skill1 starsChanged 5 days agoApache-2.0View on GitHub

Announce a WireCat Desktop release on the wirecat.dev blog, in the Telegram group and on Discord. Use when a desktop version is about to be released or was just tagged, or when asked to write release notes, a release post or a community announcement.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. NanmiCoder/cc-haha★ 15ksame name
    2. NanmiCoder/claude-code-haha★ 15ksame name
    3. Necmttn/ax★ 116same name
    4. ziya-ai/ziya★ 42same name
    5. microsoft/amplifier-app-paperclip★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always say it is WireCat Desktop (the app), not a tool release.

    line 6
  2. Distinctive:

    Add what a user would notice.

    line 15
  3. Very specific:

    After merge, bin/tag-release on main.

    line 21
  4. Very specific:

    Check free -g first and run one browser at a time.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Always say it is WireCat Desktop (the app), not a tool release. Model: the 0.3 post in content/blog/wirecat-desktop-0-3/ and cli-docs PR #508.

What goes in

  1. Desktop changes since the last tag: git log --oneline --no-merges v<prev>..origin/main in wirecat-desktop, and the PRs behind them. Check every claim against the commit: something added and removed before the release did not ship.
  2. Anything that shipped earlier and was never announced: read the earlier posts in content/blog/, then the tool releases since the last post (gh release list -R <repo> for each repo in tools.json). Add what a user would notice.
  3. Lead with the one or two changes that say what the release is for. Smaller fixes go in a list at the end.

Order

  1. Desktop: a release: X.Y.Z PR (package.json, src-tauri/Cargo.toml, the wirecat-desktop entry in Cargo.lock). After merge, bin/tag-release on main. The tag publishes the GitHub release.
  2. Blog: draft the post while the release builds (draft: true). Merge with draft: false only after the GitHub release is published, then wait for the Deploy run and check that /en, /ru and /es post URLs return 200.
  3. Telegram and Discord last, so every link works.

Blog post

  • content/blog/wirecat-desktop-X-Y/index.md, index.ru.md, index.es.md. Title WireCat Desktop X.Y: <what it is for>.
  • Tags: release-notes plus one to three more (see the blog-tags skill).
  • Images like 0.3: a 1600×900 JPG cover per language (~100 KB) and 3 to 4 WebP screenshots per language (under 60 KB). Take them from the desktop browser build with made-up data: pnpm dev in wirecat-desktop, then ?showcase&section=<page> (the flags are listed in wirecat-desktop CLAUDE.md). Crop out the sidebar version label. Check free -g first and run one browser at a time.
  • Voice: first person, plain words, no ;, —, – or hype words. Name MAX only in the Russian post.
  • End with how to get it, the GitHub release notes link, and Discord and GitHub issues for feedback.

Telegram and Discord

Telegram in Russian to the WireCat Community group (@wirecatdev, chat id -1004382826499), Discord in English to the releases channel. Same shape:

  1. A headline with an emoji: 🚀 WireCat Desktop X.Y.
  2. One or two sentences on what the release is for and who it helps.
  3. 4 to 6 lines, each starting with an emoji, one change each, in the reader's words.
  4. How to get it: the app offers the update itself, and the download link for new users.
  5. The post link.
  6. Engagement: a question to answer in the comments (which feature to do next, what they use most), and an invite to the Discord, the Telegram chat and a star on GitHub.

Show both texts to the owner before posting. Telegram goes out from the owner's account with tg personal messages send -1004382826499 (text on stdin). Discord goes out with bin/post-discord <file> in cli-docs, which reads the webhook from the keyring (service discord account wirecat-releases-webhook).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free