Newsletter
ericrisco/rsc-harness
A skill your agent uses when running an email newsletter as a recurring publication — subject + preview pair, issues that turn opens into clicks, the welcome sequence, cadence and engagement…
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.
$ npx skills add GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills building-communication-engine --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/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/building-communication-engine .claude/skills/building-communication-engine && 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 "building-communication-engine" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/building-communication-engine into .claude/skills/building-communication-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-communication-engine", 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/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/building-communication-engineType 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 GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills building-communication-engine --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/building-communication-engine .agents/skills/building-communication-engine && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "building-communication-engine" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/building-communication-engine into .agents/skills/building-communication-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-communication-engine", 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 GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills building-communication-engine --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/building-communication-engine .cursor/skills/building-communication-engine && 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 "building-communication-engine" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/building-communication-engine into .cursor/skills/building-communication-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-communication-engine", 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/GTM-Strategist/gtm-strategist-skills.git --path .claude/skills/building-communication-engine--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 GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills building-communication-engine --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/building-communication-engine .gemini/skills/building-communication-engine && 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 "building-communication-engine" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/building-communication-engine into .gemini/skills/building-communication-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-communication-engine", 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 GTM-Strategist/gtm-strategist-skills building-communication-engineInstalls 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 GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/building-communication-engine .github/skills/building-communication-engine && 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 "building-communication-engine" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/building-communication-engine into .github/skills/building-communication-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-communication-engine", 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 GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills building-communication-engine --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/building-communication-engine .opencode/skills/building-communication-engine && 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 "building-communication-engine" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/building-communication-engine into .opencode/skills/building-communication-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-communication-engine", 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.
building-communication-engineA 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.
Building Communication Engine is an agent skill from GTM-Strategist/gtm-strategist-skills. Use this skill when the user wants to choose marketing channels, plan their launch newsletter, set a GTM budget, collect social proof, or build their communication strategy. Phase 8 of 12: interactive guided workflow for choosing GTM motions, narrowing channels, projecting funnels, drafting social posts, launching newsletters, collecting social proof, marketplace strategy, GTM budget, and launch plan presentation.
Its SKILL.md is about 2.8k 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 Go-to-market strategy, Newsletters and Marketing psychology. The repository describes itself as: Your AI go-to-market co-pilot. The licence is MIT.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit a5ead26. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
gtmstrategist.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Building Communication Engine loads about 2.8k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,390 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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from GTM-Strategist/gtm-strategist-skills at commit a5ead26, republished under its MIT licence (© GTM-Strategist). 1,390 words, ~2,773 tokens.
.claude/skills/building-communication-engine/SKILL.md (or your agent's skills folder).This is Phase 8 of the GTM Strategist methodology. You have your product defined, pricing set, positioning crafted, and launch assets prepared. Now you build the engine that gets your message to market.
This phase answers: How will we reach our market, through which channels, with what budget, and who owns what?
Read my-gtm-context.md first. Key sections: Target Market (2), ICP (3), Team & Resources (8), Goals (9), Voice (10).
Check outputs/ for prior phase work. This phase builds on:
outputs/01-*.md — OPE canvas, value prop, 90-day plan (Phase 1)outputs/03-*.md — Validated ICP/ECP personas (Phase 3)outputs/05-*.md — Pricing strategy and business model (Phase 5)outputs/06-*.md — Positioning, UVP/USP, messaging (Phase 6)outputs/07-*.md — Website, demo, media kit, pitch deck (Phase 7)If key prior outputs are missing, tell the user which phase to complete first and why.
Output file: outputs/08-gtm-motions.md
Duration: 1-3 hours
Map the five core GTM motions and choose which fit your stage and resources.
The Five GTM Motions: Inbound (content/SEO pulls prospects to you), Outbound (direct outreach), Product-Led/PLG (free trial/freemium), Community-Led (build audience first), Partner-Led (leverage others' audiences).
For each motion, score 1-5 on: ICP Fit, Resource Match, Time to Results, Scalability, Stage Fit.
Stage-based defaults:
Within each motion, pick specific actions. Do not try everything — pick 3-5 total actions across motions. Deliver: selected motions (ranked with scores), selected GTM actions (with owner, timeline, success metric), motions deprioritized (and why), key assumptions to validate.
Output file: outputs/08-channel-selection.md
Duration: 1-3 hours
Pick 2-3 channels maximum. Better to dominate one channel than be mediocre on five.
For each candidate channel, evaluate: ICP Presence (are they actually there?), Content-Market Fit, Competition Density, Cost to Play, Measurability, Compounding potential.
Quick channel guide:
Deliver: 2-3 selected channels (with evidence, cadence, owner, 90-day goal, monthly cost), channels deprioritized, month-by-month sequencing plan.
Output file: outputs/08-funnel-projection.md
Duration: 1-3 hours
Model your funnel from top to bottom. Work backward from revenue goal.
Backward funnel math: Start with revenue goal → divide by average deal size → customers needed → divide by close rate → opportunities needed → continue up through SQLs, MQLs, leads, visitors. Use industry benchmarks as starting assumptions (B2B SaaS: 2-5% visitor-to-lead, 20-30% opp-to-customer; B2C: 1-3% visitor-to-lead, 2-5% trial-to-customer).
Break down the funnel per selected channel. Model three scenarios (conservative at half benchmark, base at benchmark, optimistic at +30%).
Deliver: revenue target, backward funnel model, per-channel breakdown, sensitivity analysis (3 scenarios), key levers to optimize, assumptions and risks.
Output file: outputs/08-social-media-drafts.md
Duration: 1-3 hours
Pre-launch content for your personal profile so you don't look like a ghost when prospects check. The goal is NOT to sell — establish credibility and signal something is coming.
Five post categories: Expertise Signal ("I've spent X months studying..."), Behind the Scenes ("Building [product] taught me..."), Problem Spotlight ("Every [ICP] I talk to has the same complaint..."), Insight/Hot Take ("[Common belief] is wrong..."), Social Proof Tease ("Just finished our 10th interview...").
Write from personal experience. Use specific numbers and stories. Hook in first line. End with engagement prompt (question, not CTA). Match platform native style. Reference voice from my-gtm-context.md Section 10.
Deliver: 5+ full post drafts (each with category, platform, timing relative to launch), plus a publishing calendar.
Output file: outputs/08-newsletter-plan.md
Duration: 1-3 hours
Start a newsletter or closed updates channel for stakeholders, early adopters, and supporters.
Options: Email newsletter (Beehiiv, ConvertKit, Substack), Closed blog/updates page, Private community updates (Discord/Slack), LinkedIn newsletter.
Content mix per issue: Progress update (2-3 paragraphs), Insight or learning (3-5 paragraphs), One specific ask or CTA (1-2 sentences).
First 4 issues: #1 The Why (origin story + problem validation), #2 The How (approach + what's different), #3 The Proof (early signals, interview snippets), #4 The Launch (details + exclusive early access).
Deliver: strategy (format, tool, frequency, target list size), audience building plan (how to get first 100 subscribers), content calendar for 4 issues, full draft of Issue #1, metrics to track (open rate >40%, click >5%, reply >2%).
Output file: outputs/08-social-proof-collection.md
Duration: 1-3 days
Social proof is the single strongest conversion lever. Collect at least 5 statements before launch.
Strength hierarchy: Named customer + metric (strongest) → Named customer + quote → Logo wall → Anonymous quote → Aggregate stat → Advisor endorsement → Self-reported metric (weakest).
Who to ask: Interview participants who showed positive sentiment (Phase 2-3), alpha/beta testers, design partners, advisors, industry peers who saw your demo.
How to ask: Short message referencing the specific positive thing they said. Offer three options: named quote, anonymous quote, or they write their own version.
Enhancement: Turn vague quotes into specific ones (always get approval). "It's really good" → "This is the first tool that actually fits how our team works."
Deliver: 5+ statements (each with exact quote, attribution, context, permission status, best use case), social proof gaps, outreach plan for more.
Output file: outputs/08-marketplace-strategy.md
Duration: 1-3 hours
Decide which launch platforms (if any) to use and plan timing.
Key platforms: Product Hunt (tech early adopters, one-shot), AppSumo (deal seekers, post-launch), Indie Hackers (bootstrappers, build in public), G2/Capterra (B2B buyers, needs 10+ reviews), Hacker News (developers, unpredictable), Reddit (varies by subreddit, anti-promotional).
Launch on marketplace if: ICP is active there (validated), 50+ supporters, clear demo-able "aha moment", can handle traffic spike. Skip if: Enterprise ICP, needs hands-on onboarding, no support network, product not ready for scrutiny.
Deliver: decision (which platforms or skip), for each selected platform: why, timeline, goal, prep checklist, support network plan.
Output file: outputs/08-gtm-budget.md
Duration: 1-3 hours
Build a realistic GTM budget mapping spend to channels and expected returns.
Budget categories: Tools & Subscriptions ($100-500/mo), Content Creation ($0-2K/mo), Paid Advertising ($0-5K/mo start small), Events & Community ($0-1K/mo), Partnerships (performance-based), PR & Outreach ($0-2K one-time), Time Cost (founder hours at opportunity cost — usually the biggest line).
Per-channel ROI: For each channel, estimate: monthly spend, time investment (hours x opportunity cost), expected leads/month, expected customers/month, CAC, LTV:CAC ratio (target >3:1), payback period.
Deliver: Q1 budget summary (cash + time), detailed month-by-month budget table, per-channel ROI projections, budget rules (max % on unproven channels, review cadence), what's NOT budgeted and why.
Output file: outputs/08-launch-plan-presentation.md
Duration: 1-3 hours
Compile everything from Tasks 1-8 plus prior phase outputs into a single launch plan for team buy-in.
Structure: The Opportunity (problem, why now, target customer — from Phases 1-3), Our Approach (motions, channels, funnel — Tasks 1-3), Launch Assets & Readiness (from Phase 7 + Tasks 4-7), Budget & Resources (Task 8), Timeline & Owners (week-by-week for 4-8 weeks with RACI matrix), Success Metrics (30/60/90-day targets).
Include a launch readiness checklist covering all prior deliverables. Include risks with likelihood, impact, and mitigation. Include specific decisions needed (who decides, by when).
Deliver: complete launch plan document with executive summary, all sections, RACI matrix, timeline, readiness checklist, risks, and decisions needed.
Phase 8 transforms your positioning and assets into an operational engine. You should now have:
Next phase: Phase 9 (Executing Launch) — pulling the trigger on everything planned here.
GTM Strategist methodology by Maja Voje. https://gtmstrategist.com
© GTM-Strategist, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/building-communication-engine of GTM-Strategist/gtm-strategist-skills.
Open the folder on GitHubat commit a5ead26
Building Communication Engine 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 |
|---|---|---|---|---|---|---|
| Building Communication Engine this skillGTM-Strategist/gtm-strategist-skills | 264 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Newsletterericrisco/rsc-harness | 180 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Launch Distributionamplitude/builder-skills | 159 | — | ~2.8k | Automated safety check: Pass | None | |
| Buzz Launchjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.5k | Automated safety check: Notes | MIT | |
| Linkedin Company Pagessocial-media-skills/skills | 134 | — | ~2k | Automated safety check: Pass | MIT | |
| Changelog Social RecapFlorianBruniaux/claude-code-ultimate-guide | 6.1k | — | ~1.8k | Automated safety check: Notes | CC-BY-SA-4.0 |
ericrisco/rsc-harness
A skill your agent uses when running an email newsletter as a recurring publication — subject + preview pair, issues that turn opens into clicks, the welcome sequence, cadence and engagement…
amplitude/builder-skills
Plan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms.
jeremylongshore/tons-of-skills-marketplace
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment.
social-media-skills/skills
The LinkedIn company-page (LINKEDINPAGES) growth strategy skill -- a separate platform from personal LINKEDIN.
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
charlie947/social-media-skills
Build a personalised voice profile inside a Codex or Claude project from a short interview plus 3 to 5 sample pieces of writing.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to position their product in the market, craft messaging, define their UVP/USP, or build a visual identity.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to validate their customer assumptions, test their ICP, design experiments, or create customer personas from evidence.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to research competitors, plan customer interviews, conduct market research, or understand their competitive landscape.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user is preparing to launch, wants to set up a war room, build a launch support network, write launch emails, or plan launch day activities.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user needs to build launch assets like a website, pitch deck, press release, product demo, or media kit.
Categories
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. Building Communication Engine is an agent skill from GTM-Strategist/gtm-strategist-skills. Use this skill when the user wants to choose marketing channels, plan their launch newsletter, set a GTM budget, collect social proof, or build their communication strategy.
Building Communication Engine fits situations like: the user wants to choose marketing channels; plan their launch newsletter; set a GTM budget; collect social proof.
Run `npx skills add GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a claude-code`. Or copy the skill folder (.claude/skills/building-communication-engine in GTM-Strategist/gtm-strategist-skills) into .claude/skills/building-communication-engine in your project. Claude Code loads it when a task matches its description.
Run `npx skills add GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a codex`. Or copy the skill folder (.claude/skills/building-communication-engine in GTM-Strategist/gtm-strategist-skills) into .agents/skills/building-communication-engine in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GTM-Strategist/gtm-strategist-skills --skill building-communication-engine -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/building-communication-engine, .gemini/skills/building-communication-engine, .github/skills/building-communication-engine and .opencode/skills/building-communication-engine in your project.
SKILL.md names no scripts, command-line tools or credentials: Building Communication Engine is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: gtmstrategist.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Building Communication Engine is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Building Communication Engine: Newsletter (ericrisco/rsc-harness, 180 stars), Launch Distribution (amplitude/builder-skills, 159 stars), Buzz Launch (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Linkedin Company Pages (social-media-skills/skills, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
GTM-Strategist (a GitHub organization) maintains it in GTM-Strategist/gtm-strategist-skills, which has 264 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 7, 2026.
Source: GTM-Strategist/gtm-strategist-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.