Megaphone

The launch-orchestration plugin for indie & vibe coders.
Plans your launch, drafts every channel, publishes to your accounts — fully local, no SaaS in the middle.

---

You built the thing. Megaphone helps the world find it.

It scans your repo, drafts community-aware posts (Reddit per-subreddit, Show HN, Indie Hackers, Peerlist, Hashnode + the usual feed platforms), runs outreach to venues and amplifiers, publishes the drafts to live platforms, schedules launch sequences, audits your landing page, and tracks traction — all from inside Claude Code.

Your OAuth tokens stay on your machine. No backend. No subscription.

Install

In Claude Code, run:

/plugin marketplace add fernandoleyra/megaphone
/plugin install megaphone

Then enable it: run /plugin, find megaphone in the list, and toggle it on. Apply with /reload-plugins (or restart Claude Code). You'll get 9 skills (auto-triggered from natural language) and 6 slash commands (for explicit invocation).

If skills or commands don't show up, run /plugin again and confirm megaphone is enabled, then /reload-plugins.

First run

The fastest way to see Megaphone work: a 3-command session that takes you from "fresh repo" to "drafted launch post on disk."

You: I just built a thing. Help me ship it.
Claude: [megaphone-init] → scans repo, asks for 1–3 voice samples, writes .megaphone/profile.json

You: draft a Bluesky launch post
Claude: [megaphone-post] → reads recent commits + voice samples, writes .megaphone/posts/<date>/bluesky.md

You: publish it
Claude: [megaphone-publish] → posts to your Bluesky (after you confirm), writes a receipt to .megaphone/published/

You'll know Megaphone is working when .megaphone/profile.json reads back your voice samples and the first post draft sounds like you, not like generic AI output. That's the activation moment.

A fuller session — assets, outreach, audit, schedule — looks like this:

You: generate the assets
Claude: [megaphone-assets] → tagline + hook + README hero + dev.to intro + banner-image prompt

You: where should I submit and who should I DM?
Claude: [megaphone-outreach] → 15 venues scored, 10 amplifiers found, personalized packets and DMs drafted

You: pre-launch audit
Claude: [megaphone-audit] → README/journey walkthrough + activation moment + ranked blockers

You: schedule the launch sequence
Claude: [megaphone-schedule] → one queue row per platform, fired locally on launch day

Slash commands

Command	What it does
/megaphone:init	Scan repo, write .megaphone/profile.json
/megaphone:post	Draft a community-aware post for a venue
/megaphone:publish	Publish a draft to a live platform
/megaphone:schedule	Schedule a post, cadence, or launch sequence
/megaphone:audit	Landing page + user journey audit
/megaphone:digest	Weekly traction digest

The other three skills (megaphone-assets, megaphone-demo, megaphone-outreach) are conversational by nature — invoke them by describing what you want.

What you get — 9 skills

These auto-trigger when Claude detects a matching intent in your message. The phrases below are examples — exact wording isn't required.

Skill	Example phrases	What it does
megaphone-init	"set up megaphone", "init megaphone for this repo"	Scans your repo and writes .megaphone/profile.json capturing what your project is, who it's for, and how you sound.
megaphone-assets	"generate marketing assets", "rewrite my README", "I need a banner"	One-liner, hook, README hero, dev.to intro, landing copy. Crafts banner-image prompts (NanoBanana / DALL·E).
megaphone-demo	"make a demo gif", "record a demo", "make a CLI mockup"	Two paths: real recordings of deployed web apps via Playwright, OR scripted Remotion mockups for CLI/IDE projects (hands a structured scene spec to a Remotion-rendering skill).
megaphone-post	"draft a Show HN", "draft a Reddit r/SideProject post", "post on Indie Hackers"	Community-aware drafting. Reads each venue's culture before writing — Reddit per-sub, HN, IH, Peerlist, Hashnode + Bluesky, X, LinkedIn, Threads, Mastodon, dev.to.
megaphone-outreach	"plan my launch", "find awesome-lists", "draft a DM to "	Four phases: score venues → find amplifiers → draft personalized DMs + submission packets → build the 30/14/6/0-day launch plan.
megaphone-publish	"publish my drafts", "post to bluesky", "ship the launch posts"	Drafts go live on the actual platform — Bluesky, LinkedIn, dev.to, Reddit, Mastodon, X, Hashnode. Local OAuth, tokens never leave your machine.
megaphone-schedule	"schedule this for tuesday 10am", "set up the launch sequence"	One-offs, recurring cadences from a folder, coordinated launch-day sequences. Asks your preferred cadence (1-day blitz / 7-day sprint / 30-day plan / custom).
megaphone-audit	"audit my landing page", "audit my user journey", "pre-launch audit"	Landing page (100-pt rubric) + journey audit (70-pt + three-persona walkthrough). Names the activation moment and ranks blockers.
megaphone-digest	"weekly digest", "how's my project doing"	Stars delta, posts published, top performers, next best action.

Why it's different

	Megaphone	Upload-Post	Postiz	Buffer / Hootsuite
Where your tokens live	Your machine	Their backend	Their DB	Their dashboard
Subscription	None	$0 / 10 uploads/mo	Freemium	$6–$120+/mo
Repo-aware drafting	✅	❌	❌	❌
Community-platform drafting (Reddit per-sub, HN, IH)	First-class	❌	Limited	❌
Cross-platform launch sequences	✅	❌	❌	❌
Amplifier discovery + personalized DMs	✅	❌	❌	❌
Landing + journey audits	✅	❌	❌	❌

The trade-off: we don't do TikTok / Instagram / YouTube. Megaphone is built for launching software — which is what indie devs actually need.

Design principles

• Human-in-the-loop by default. Every post is drafted to a file you can edit before publishing. Outreach DMs are never auto-sent.
• Repo-aware. Skills read your README, manifests, recent commits, deployed URL, voice samples. The more you commit, the better the posts.
• Persistent. Per-project state in .megaphone/, user-wide credentials in ~/.megaphone/credentials/ (chmod 0600). Survives across sessions. Credentials are managed via the short megaphone-auth command (auto-installed to ~/.local/bin by /megaphone:init) — megaphone-auth status, megaphone-auth connect <platform>, megaphone-auth disconnect <platform>.
• Stdlib-only Python. No pip install for the core. Demo GIFs need Playwright + ffmpeg (one-time) — or, for CLI projects, hand off to a Remotion-rendering skill.
• Honest about platform rules. HN, awesome-lists, Reddit promo rules, X auto-replies — Megaphone says plainly what's automatable and what isn't.

Roadmap

Concrete next-version targets. Open issues to influence priority.

• 0.8 — Demo path for CLI projects. Hand off a structured scene spec to a Remotion-rendering skill so plugin/CLI projects get an embeddable mockup demo without Playwright.
• 0.8 — Custom launch cadences. megaphone-schedule and megaphone-outreach accept 1-day blitz / 7-day sprint / 30-day plan / custom timelines instead of the hardcoded 30/14/6/0.
• 0.9 — Threads connector. Add Threads (Meta) to the per-platform connector layer.
• 0.9 — Launch-week analytics in /megaphone:digest. Hour-level traction view for the first 72h after launch.
• 1.0 — megaphone-publish retries. Smarter exponential backoff + dead-letter queue for posts that exhaust their retry budget.

Want to nudge an item up? Open an issue with a use case.

Changelog

See CHANGELOG.md for the per-version history.

Requirements

• Claude Code (latest)
• Python 3.10+ (stdlib only — no pip install for the core)
• Optional: Playwright + ffmpeg (only if you use megaphone-demo for web-app GIFs)

⭐ Star this repo

If Megaphone helps you launch something, please star the repo. Stars are the single biggest signal that keeps this project alive and free for everyone. It costs you one click — and it helps another indie dev find it.

→ Star Megaphone on GitHub

Acknowledgments

Megaphone stands on the shoulders of:

• Anthropic Claude Code — the platform that made plugins like this possible.
• Anthropic official skills — reference patterns for the skills format.
• obra/superpowers — for showing what a great Claude Code plugin looks like end-to-end.

If you build something on top of Megaphone, ping me — I'd love to see it.

License

MIT © 2026 Fernando Leyra. Free to use, fork, modify, and redistribute.