Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Design, write, and grow editorial newsletters with consistent voice and format. Creates newsletter strategy, templates, and growth playbook. Use when someone wants to start a newsletter, improve an existing one, grow subscribers, write a newsletter issue, plan newsletter content, or set up on Substack, Beehiiv, Ghost, or ConvertKit. Triggers on 'newsletter', 'editorial', 'weekly email', 'subscriber growth', 'newsletter template', 'email digest', 'Substack', 'Beehiiv', 'newsletter strategy', 'newsletter issue', 'recurring email', or 'email content'. Even if they just say 'I want to email my audience regularly' or 'start a weekly email', this is the skill. Covers curated, editorial, and hybrid formats with referral programs, platform guidance, and engagement metrics.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You design and write editorial newsletters that people actually look forward to receiving. Not corporate updates nobody reads — opinionated, valuable, personality-driven emails that build an audience over time.
brand/voice-profile.md — newsletters live or die by voice consistencybrand/audience.md — understand what they care about, how sophisticated they aremarketing/newsletter/ for existing strategy and past issues| Type | Description | Best For | Example |
|---|---|---|---|
| Curated | Best links + your commentary | Industry watchers, busy professionals | The Hustle, TLDR |
| Editorial | Original essays/insights | Thought leaders, opinionated founders | Stratechery, Lenny's Newsletter |
| Hybrid | Mix of original + curated | Most founders and creators | Morning Brew, Dense Discovery |
| Product update | What's new in your product | SaaS companies with active users | Linear, Notion changelogs |
| Educational | Teaches one skill per issue | Course creators, consultants | James Clear, Marketing Examples |
Before writing a single issue, establish:
---
name: "Newsletter Name"
tagline: "One-line value prop (what they get + how often)"
type: curated | editorial | hybrid | product | educational
frequency: weekly | biweekly | daily
send_day: Tuesday
send_time: "9:00 AM ET"
target_audience: "Who specifically reads this"
core_topic: "The single topic area"
voice: "How it sounds (reference voice-profile.md)"
success_metric: "Open rate > 40%, click rate > 5%"
---
Every newsletter needs a repeatable structure readers come to expect.
# [Newsletter Name] — Issue #[N]
## [Catchy issue title or theme]
### Intro (2-3 sentences)
[Personal hook — what happened this week, what's on your mind, why this issue matters]
---
### Section 1: [Main Value Block]
[The core content — original insight, deep dive, or primary curation]
### Section 2: [Secondary Value]
[Supporting content, related links, or complementary angle]
### Section 3: [Quick Hits / Links]
- **[Link title]** — One-line commentary on why it matters
- **[Link title]** — One-line commentary
- **[Link title]** — One-line commentary
---
### [Recurring Section Name]
[Something predictable readers look forward to: tool of the week, quote, stat, hot take]
---
### CTA
[One primary ask: share, reply, check out product, visit link]
---
[Sign-off in your voice]
[Name]
[Footer: unsubscribe, share link, social links]
Curated Newsletter:
Editorial Newsletter:
Hybrid Newsletter:
---
issue_number: 42
title: "Issue title"
subject: "Email subject line"
preview: "Preview text"
theme: "Core topic"
send_date: 2026-03-12
word_count: 850
status: draft
---
Newsletters live or die on voice. Generic AI voice is fatal — readers unsubscribe from "content," they stay for a person.
Words to ban: delve, comprehensive, robust, utilize, landscape, navigate, foster, empower, elevate, streamline, crucial, leverage Phrases to ban: "In today's fast-paced world," "It's worth noting that," "Let's dive in," "Without further ado," "In conclusion" Structural tells: Every section same length. No personal anecdotes. No opinions without hedging. Perfect grammar everywhere (real newsletters have personality quirks). No contractions. The test: Read it aloud. If it sounds like a press release or a textbook, rewrite it. It should sound like a smart friend talking over coffee.
| Frequency | Pros | Cons | Best For |
|---|---|---|---|
| Daily | Habit-forming, high engagement | Burnout risk, high content demand | News, curation-heavy |
| Weekly | Sustainable, high quality per issue | Slower growth | Most creators and businesses |
| Biweekly | Low pressure, high quality | Harder to build habit | In-depth analysis, B2B |
| Monthly | Maximum quality | Easy to forget about | Reports, roundups |
Default recommendation: Weekly. It's the sweet spot between staying top-of-mind and maintaining quality.
For each newsletter, generate these growth assets:
Write a dedicated newsletter signup page with:
Write the welcome email that triggers on signup:
Write referral program copy with tiered rewards:
Write a cross-promo pitch email for newsletters of similar size:
For each issue, generate 1-2 social posts that share a highlight and link to the archive/signup:
| Channel | Tactic | Expected Conversion |
|---|---|---|
| Website | Homepage signup bar, exit intent popup, blog post CTAs | 1-3% of visitors |
| Social | Pin newsletter link in bio, share issue highlights | 0.5-2% of followers |
| Cross-promo | Newsletter swaps with similar-size newsletters | 50-200 subs per swap |
| Lead magnet | Free resource into newsletter opt-in | 20-40% of landing page visitors |
| Referral | Give subscribers a referral link + incentive | 10-20% of new subs |
| Content | SEO articles with newsletter CTA | Compounding over time |
| Metric | Good | Great | Action If Low |
|---|---|---|---|
| Open rate | 30-40% | 40-50%+ | Better subjects, clean list, check deliverability |
| Click rate | 2-4% | 5-8%+ | Better CTAs, more relevant links, clearer value |
| Reply rate | 1-2% | 3-5%+ | Ask better questions, be more personal |
| Unsubscribe | <0.5% | <0.2% | Check frequency, relevance, expectations |
| Growth rate | 5-10%/mo | 10-20%/mo | Add acquisition channels, improve lead magnets |
Newsletter: "The Build Log" — Weekly hybrid newsletter for indie hackers
Subject Line Variants:
Preview Text: Plus 3 tools I switched to this month
Issue:
# The Build Log — Issue #12
## The feature that almost killed our conversion rate
Last week I shipped a "smart onboarding" flow. Took 3 days to build. Looked beautiful.
Conversion dropped 23%.
Turns out, users don't want smart. They want fast. The old flow was 2 steps. The new one was 5. Each step was better — but 5 steps is 5 chances to leave.
I reverted Thursday morning. Conversion recovered by Friday.
**The lesson:** Complexity is a tax. Every step you add needs to earn 10x what it costs in drop-off.
---
### 3 things worth your time
**[Why most MVPs are too big](link)** — This thread nails it. Your MVP should embarrass you, not impress your friends.
**[Indie Hackers revenue dashboard](link)** — New feature lets you see revenue benchmarks by category. I spent 30 minutes comparing and it was worth every second.
**[PostHog's session replay](link)** — Free tier is generous. Watching real users navigate your app is humbling and instructive.
---
### Tool I switched to
**Plausible Analytics** — Replaced Google Analytics. Lighter, privacy-friendly, and I actually look at the dashboard now because it's not overwhelming.
---
What's the last feature you shipped that backfired? Hit reply — I read everything.
— James
marketing/newsletter/
├── strategy.md # Newsletter definition and strategy
├── template.md # Repeatable issue template
├── growth-plan.md # Acquisition and referral strategy
└── issues/
├── 2026-03-12-issue-title.md # Individual issues
└── ...
Integration: Issues output in plain text format compatible with gws CLI for sending.
See references/archetype-templates.md for the detailed output presentation format (visual summary with subject line variants, send recommendations, files saved, and what's next sections).
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Add a new sound effect to @remotion/sfx
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, measures, and improves an Answer Engine Optimization program across ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and Copilot. Use for AEO, GEO, LLMO, AI search visibility, AI citations, brand mentions, answer-engine monitoring, llms.txt, AI crawler audits, or questions like 'what does AI say about us?' and 'why are competitors cited instead of us?'. Produces a durable evidence report and prioritized gameplan, not a one-shot content checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.
日本語の概要は準備中です。原文の説明を表示しています。
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
日本語の概要は準備中です。原文の説明を表示しています。