Building Communication Engine
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to choose marketing channels, plan their launch newsletter, set a GTM budget, collect social proof, or build their communication strategy.
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment.
Install Buzz Launch
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-launch --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/buzz-launch .claude/skills/buzz-launch && rm -rf skills-srcUse ~/.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/
Install the "buzz-launch" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-launch into .claude/skills/buzz-launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buzz-launch", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-launchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-launch --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/buzz-launch .agents/skills/buzz-launch && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "buzz-launch" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-launch into .agents/skills/buzz-launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buzz-launch", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-launch --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/buzz-launch .cursor/skills/buzz-launch && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "buzz-launch" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-launch into .cursor/skills/buzz-launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buzz-launch", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/buzz-launch--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-launch --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/buzz-launch .gemini/skills/buzz-launch && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "buzz-launch" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-launch into .gemini/skills/buzz-launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buzz-launch", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-launchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/buzz-launch .github/skills/buzz-launch && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "buzz-launch" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-launch into .github/skills/buzz-launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buzz-launch", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-launch --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/buzz-launch .opencode/skills/buzz-launch && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "buzz-launch" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-launch into .opencode/skills/buzz-launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buzz-launch", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
buzz-launch- GitHub stars
- 2.8k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 363 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment.
- Works in 7 steps: Launch Scope → Launch Readiness Checklist → Product Hunt Launch Plan → …
- Asked to launch [feature/product]
- SKILL.md covers Steps and Delivery
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Buzz Launch is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
Its SKILL.md is about 1.5k 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 Writing & Content, covering Product launch strategy, Newsletters and Social media posts. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Asked to launch [feature/product]
- Help us do a Product Hunt launch
- Coordinate the announcement
Example prompts
- “launch [feature/product]”
- “plan a launch”
- “help us do a Product Hunt launch”
- “/buzz-launch”
Requirements
- Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashGlobGrepWebFetchWebSearchAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Buzz Launch loads about 1.5k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 363 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
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 jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 363 words, ~1,468 tokens.
Download SKILL.mdSave it as
.claude/skills/buzz-launch/SKILL.md (or your agent's skills folder).- name
- buzz-launch
- description
- Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
- allowed-tools
- Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
- version
- 0.1.0
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
Launch Planning
You are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.
Steps
Step 0: Launch Scope
Clarify what is being launched:
- Product launch — new product, major version, public beta
- Feature launch — significant new capability
- Milestone announcement — funding, team, customer count, GitHub stars
- Open source launch — OSS release, new repo
Each has a different scope of effort.
Ask: What's being launched, and what is the goal? (Signups / GitHub stars / press coverage / community growth / enterprise pipeline)
Step 1: Launch Readiness Checklist
Before setting a launch date:
Product:
[ ] Product works reliably under load
[ ] Onboarding can be completed without help
[ ] Error states are handled gracefully (not 500 pages)
[ ] Mobile experience acceptable (if relevant)
Content:
[ ] Landing page copy updated to reflect new product/feature
[ ] Demo video or GIF created (30-60 seconds)
[ ] Screenshots updated
[ ] Docs updated for new functionality
Distribution assets:
[ ] Product Hunt listing drafted
[ ] HN Show HN post drafted
[ ] Twitter/X thread drafted
[ ] LinkedIn post drafted
[ ] Email to existing list drafted
[ ] Community announcement drafted (Discord/Slack)
Coordination:
[ ] Launch date set and team aligned
[ ] Support coverage scheduled for launch day
[ ] Person assigned to monitor and respond on each channel
[ ] Response playbook for likely objections/questionsStep 2: Product Hunt Launch Plan
Product Hunt is a snapshot of a day. Votes come in waves. Structure:
Pre-launch (2-4 weeks before):
- Create hunter network: ask 20-50 people to upvote on launch day. Real relationships only.
- Build PH presence: follow people, comment on others' launches to establish credibility.
- Prepare assets: logo, screenshots (×4), tagline (max 60 chars), description (max 260 chars)
Launch day:
- Post at 12:01 AM PST (start of day)
- Founder posts a personal comment at launch explaining the story
- Share PH link to: existing customers, email list, community, social — all at once in first 2 hours
- Monitor comments and respond within 30 minutes during business hours
PH listing structure:
Name: [Product name]
Tagline: [What it does in 60 chars — no marketing speak]
Description:
Problem: [1 sentence]
Solution: [1-2 sentences]
Key features: [3 bullets]
Who it's for: [1 sentence]
Try it: [link]
First maker comment:
[Personal story — why did you build this? What problem were YOU experiencing?]
[What's unique about your approach]
[What feedback you're looking for]Show full SKILL.md (154 more words)Show less
Step 3: HN Show HN Plan
HN is about authenticity and technical depth. Different audience than PH.
Show HN checklist:
- Title format: "Show HN: [Product] – [plain English description]"
- Post between 6-9 AM EST weekdays
- First comment (posted by OP): technical details, what you learned building it, what you want feedback on
- Never ask for upvotes. Never.
- Respond to every comment in the first 2 hours. Especially critical ones.
Founder's first comment template:
[What technical challenge was interesting in building this]
[What surprised you about the problem]
[What stage you're at — alpha/beta/v1, open source or not]
[Specific thing you want feedback on]Step 4: Coordinated Launch Timeline
T-7 days: Notify existing community ("something big coming")
T-3 days: Brief top supporters / customers with early access
T-1 day: Prep all draft posts, schedule email
Launch day:
12:01 AM: Product Hunt live
6:00 AM: HN Show HN post
9:00 AM: Twitter/X thread from founder account
9:30 AM: Company social shares
10:00 AM: Email to existing list
11:00 AM: Community announcement
12:00 PM: LinkedIn post
Launch week:
Day 2: First press coverage follow-up (if outreach was done pre-launch)
Day 3: "What we learned from launch" reflection post/thread
Day 7: Share launch metrics publicly (if strong — transparency builds trust)Step 5: Post-Launch Follow-Through
The biggest launch mistake: no follow-through. Community joins and finds nothing happening.
Week 1: Respond to every comment, question, and issue from launch
Week 2: Share 2-3 user stories from people who tried it at launch
Week 3: Roadmap update based on launch feedback
Month 2: "What happened after our launch" postStep 6: Produce Launch Kit
Deliver all launch assets:
# Launch Kit — [Product Name]
**Launch date:** [date]
**Goal:** [primary metric]
## Pre-Launch
[Checklist from Step 1]
## Product Hunt Listing
[Full listing copy]
## HN Show HN Post
[Title + first comment]
## Social Posts (all platforms)
[Ready-to-send posts per platform]
## Email to List
[Subject + body]
## Community Announcement
[Discord/Slack message]
## Launch Day Timeline
[Timeline from Step 4]
## Post-Launch Plan
[Week 1-4 actions]
## Success Metrics
- Primary: [metric — signups / stars / coverage]
- Secondary: [metric]
- How to measure: [specific tool or method]Delivery
Produce the complete launch kit with all assets written out and ready to use. Every piece should be copy-paste ready on launch day — no open questions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. If output exceeds 40 lines, delegate to /atlas-report.
© jeremylongshore, 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 plugins/ai-agency/tonone/skills/buzz-launch of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit 80f86df
Compare with similar skills
Buzz Launch 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Buzz Launch this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.5k | Automated safety check: Notes | MIT | |
| Building Communication EngineGTM-Strategist/gtm-strategist-skills | 263 | — | ~2.8k | Automated safety check: Pass | MIT | |
| X Researchtrailofbits/skills-curated | 513 | — | ~1.9k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Producthunt Launch KitVarnan-Tech/opendirectory | 674 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Schedule Socialindranilbanerjee/digital-marketing-pro | 859 | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Launch Distributionamplitude/builder-skills | 160 | — | ~2.8k | Automated safety check: Pass | None |
Similar skills
- Official
X Research
trailofbits/skills-curated
Searches X/Twitter for real-time perspectives, dev discussions, product feedback, breaking news, and expert opinions using the X API v2.
Producthunt Launch Kit
Varnan-Tech/opendirectory
A skill your agent uses when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets.
Schedule Social
indranilbanerjee/digital-marketing-pro
Schedule social posts to Twitter/X, Instagram, LinkedIn, TikTok, YouTube, and Pinterest through connected platform MCPs — generating per-platform copy variations, hashtag mixes, media-spec…
Launch Distribution
amplitude/builder-skills
Plan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms.
Dropspace
LeoYeAI/openclaw-master-skills
Create and publish social media launches via the Dropspace API.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Buzz Launch
What does Buzz Launch do?
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Buzz Launch is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment.
When should I use Buzz Launch?
Buzz Launch fits situations like: asked to launch [feature/product]; help us do a Product Hunt launch; coordinate the announcement.
How do I install Buzz Launch in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/buzz-launch in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/buzz-launch in your project. Claude Code loads it when a task matches its description.
How do I install Buzz Launch in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/buzz-launch in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/buzz-launch in your project. Codex loads it when a task matches its description.
Can I use Buzz Launch 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 jeremylongshore/tons-of-skills-marketplace --skill buzz-launch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/buzz-launch, .gemini/skills/buzz-launch, .github/skills/buzz-launch and .opencode/skills/buzz-launch in your project.
What does Buzz Launch need to run?
SKILL.md names no scripts, command-line tools or credentials: Buzz Launch is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.
Does Buzz Launch 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 Buzz Launch safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Buzz Launch use?
Buzz Launch is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Buzz Launch use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Buzz Launch?
Skills that share tags, products or a category with Buzz Launch: Building Communication Engine (GTM-Strategist/gtm-strategist-skills, 263 stars), X Research (trailofbits/skills-curated, 513 stars), Producthunt Launch Kit (Varnan-Tech/opendirectory, 674 stars) and Schedule Social (indranilbanerjee/digital-marketing-pro, 859 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Buzz Launch?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.