Skip to content
Skills Library
Marketing & content · Planning

announce

/announce

Use when a product or feature is ready to go public — after shipping, when the user says "announce it", "go live", "tell people about it", or wants a release marketed end to end.

Licence
MIT
Last repository change
06.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a product or feature is ready to go public — after shipping, when the user says "announce it", "go live", "tell people about it", or wants a release marketed end to end.

Triggers from the description

announce itgo livetell people about it
Original author description

Use when a product or feature is ready to go public — after shipping, when the user says "announce it", "go live", "tell people about it", or wants a release marketed end to end.

How it works

  1. 1. Pre-flight (verify, don't assume)
  2. 2. Assets
  3. 3. Announcement drafts (draft only — approval gate before ANY send)
  4. 4. Publish (only after explicit approval, channel by channel)
  5. 5. Post-launch loop
  6. Failure modes
Original SKILL.md headings · 65 lines, 927 words
SKILL.md preview
---
name: announce
description: Use when a product or feature is ready to go public — after shipping, when the user says "announce it", "go live", "tell people about it", or wants a release marketed end to end.
---

# Launch: ship → announce → measure

Chains existing capabilities into one launch pass. Draft everything, send nothing without approval — external comms are a CLAUDE.md Hard Stop.

The announcement rules below are distilled from sharing research and current platform-algorithm behavior; the full notes (per-platform signal weights, HN/PH/Reddit norms, sources) are in `references/virality.md` — read it when drafting for a channel not covered here or when the user asks why a rule exists. For strategy above the per-post mechanics (ORB channel portfolio, five-phase rollout, relaunch cadence, measurement loop), read `references/strategy.md` — especially when planning a launch rather than executing one.

## 1. Pre-flight (verify, don't assume)

- Uncommitted work? Run `/ship` first.
- Prod deploy live: check latest deployment status/logs (offlocal `get_latest_deployment_logs` / Vercel tools).
- Domain resolves, HTTPS works, OG meta + title + favicon present: fetch the live page and look.
- UI-facing? Run `/de-vibe` if it hasn't had a pass.

## 2. Assets

- Changelog entry (one contiguous pasteable block).
- Screenshot or demo GIF: chrome-devtools `take_screenshot` or claude-in-chrome `gif_creator` against the live site. This is not optional garnish — visual proof of the thing working is the single most shared element of an indie launch post, and image posts get ~150% more reposts than text-only on X.
- Landing copy sanity: does the page pass the 10-second first-glance test?

## 3. Announcement drafts (draft only — approval gate before ANY send)

Write all of these, then stop and present for approval.

**What makes a draft spread (apply to every channel):**

- **Lead with a hook that opens a specific curiosity gap.** "I lost 40 hours to X before finding why" works; "here's a mistake to avoid" doesn't. Vague hooks get scrolled past; hooks the post doesn't deliver on burn trust and completion rate.
- **Emotional charge over safe-and-informational.** Research on 7,000 viral articles: high-arousal emotion (awe, anger, surprise) drives sharing; flat announcement copy fails regardless of accuracy. Find the surprising angle — the number, the contrarian take, the before/after — not "we're excited to announce."
- **Give the sharer social currency.** People share what makes them look in-the-know. Include one insider fact or usable takeaway that the reader can pass along as their own discovery.
- **Receipts beat claims.** A screenshot of the thing actually working (or the real dashboard number) out-spreads polished marketing copy. "Fast" is a claim; a 3-second GIF is proof.
- **No engagement bait** ("like if you agree", "comment YES") — every major platform now classifies and halves it.

**Per-channel drafts:**

- **X/Twitter**: hook first, attach the image/GIF natively. Put the link in the first reply, not the post body — external links in the body cut reach 50-90%. Thread for depth (adds ~60% impressions), single post for speed.
- **LinkedIn**: optimize for dwell time — a story with a real arc (problem → what broke → what shipped) that takes 15+ seconds to read gets a reach bonus. Post from the personal profile (~70% more reach than company pages). Link in comments, not the post.
- **Show HN** (dev-facing products): title "Show HN: <name> – <plain one-liner>", no superlatives, link to the product or repo, never a marketing page. Body: who you are → what it is in one sentence → the problem → how it works technically → ask for feedback. Engineer-to-engineer, not pitch deck.
- **Reddit** (only where the user has account history — 9:1 contribution ratio is tracked account-wide): frame as a story post (tech decision, pricing experiment, what went wrong) with the product as supporting detail. Standalone "check out my app" posts get auto-removed.
- **Discord/Telegram announcement.**
- **Email to list** (Resend) if one exists. If there's lead time, a 72-hour teaser → reminder → launch sequence converts 3-5x better than one cold send — offer it.

Copy rules (from CLAUDE.md, non-negotiable): no em dashes, no "delve/elevate/seamless" AI slop, write like a person, pasteable blocks with no mid-sentence newlines.

## 4. Publish (only after explicit approval, channel by channel)

- X/LinkedIn: claude-in-chrome through the logged-in browser session.
- Discord/Telegram: existing webhooks (curl).
- Email: Resend via offlocal (governed — DashClaw guard applies).

**The first hour decides distribution.** On X and LinkedIn, early replies weigh ~15-150x a like and visibility halves every ~6 hours; on HN, the comment thread IS the launch. So publishing is not the end of the step: tell the user to stay reachable for 1-2 hours, and monitor + draft substantive replies to early comments for their approval (sentence-length, technical, treat critics as allies). Never solicit upvotes or seed friendly comments — vote-ring detection on HN/PH kills the post.

## 5. Post-launch loop

- Offer a next-day check: PostHog funnel/pageviews + Stripe events + Sentry errors for the new surface. `/schedule` a one-time run if the user wants it automated.
- **A launch is a cadence, not a day.** One announcement is the weakest strategy; re-announcing the same product on milestones (new feature, revenue number, build-in-public moment) gives repeated shots at spread. Offer to draft a 2-4 week follow-up post plan from the roadmap/changelog.

## Failure modes

- Announcing before the deploy is verified live — pre-flight is not optional.
- Sending anything without the per-channel approval gate.
- Marketing copy that reads AI-generated — apply the copy rules to every draft, not just finals.
- Putting the link in the X/LinkedIn post body — it's the most reliable way to kill reach.
- Publishing and walking away — the unanswered first hour wastes the launch.
- "We're excited to announce" openers — zero curiosity gap, zero social currency, scrolled past.
Files in this package (3)
  • SKILL.md 6 KB
  • references/strategy.md 4 KB
  • references/virality.md 6 KB

Versions

RepositoryScoreLicence
This page · ucsandman/marketing-studio100MIT
egregore-labs/egregore95MIT
egregore-labs/egregore86MIT

Database snapshot: 13.11.2026 · package version fd4fa2b1accb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90product-announcement
    Product announcement and launch communications generator that creates coordinated multi-channel launch messaging from press releases to social posts to internal comms. Use when: product announcement, launch announcement, product launch comms, press release, launch…
  • 86announce-release
    Announce a software release, changelog or product update on social networks with Reelspan - X, LinkedIn, Bluesky, Threads, Mastodon, Discord, Slack, Dev.to and more - with a post written for each. Use when the user ships a version, publishes release notes or a blog post, and wants it announced.
  • 100launch-strategy
    When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,'...
  • 100ozor-changelog-to-video
    Convert changelogs, release notes, and version updates into Ozor.ai video prompts. Use this skill whenever the user has a CHANGELOG.md, release notes, GitHub release, version bump summary, or any list of product changes and wants to turn them into a video. Trigger on phrases…
  • 100tg-announce
    Compose and send a short Telegram deployment announcement, or send an operational note, through an existing bot. Use for "announce this deploy", "post release summary" or "send a heads-up"; keep runtime error alerts in tg-alerts.
  • 100pitch-launch
    Produce an actual launch plan with announcement copy, channel sequence, and day-1 checklist. Use when asked to "plan a launch", "GTM strategy", "how do we announce this", "launch plan for [feature]", "go-to-market", "write our Product Hunt post", or "how do we get people to notice this".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.