newsletter
Use when the user wants to write a product update email, feature announcement newsletter, or digest email for users or subscribers
AlemTuzlak · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AlemTuzlak/skills --skill newsletter技能说明
name: newsletter description: Use when the user wants to write a product update email, feature announcement newsletter, or digest email for users or subscribers
Newsletter Writer
Write product update emails and feature announcement newsletters. Handles subject lines, preview text, email structure, and audience-appropriate content.
Input Resolution
Resolve the argument (if provided) in this order:
- Path to an existing marketing brief (
.mdcontaining "Executive Summary" or "Key Messages") -> marketing brief - Path to an existing blog post (
.mdwith blog post structure) -> blog post - Path to an existing changelog (
.mdwith Added/Fixed/Changed sections or CHANGELOG.md) -> changelog - Matches GitHub URL or
#\d+pattern -> PR - Contains
...or..-> git ref range - Resolves to existing file/directory -> codebase feature
- Otherwise -> freeform text
If no argument is provided, ask: "What should the newsletter cover? You can provide a marketing brief, blog post, changelog, PR URL/number, git ref range, file/directory path, or just describe the update."
If multiple interpretations match, confirm with the user.
Process Flow
digraph newsletter {
rankdir=TB;
"Resolve input" [shape=box];
"Phase 1: Discovery" [shape=box];
"Phase 2: Configure" [shape=box];
"Phase 3: Write" [shape=box];
"Phase 4: Review" [shape=box];
"Approved?" [shape=diamond];
"Phase 5: Output" [shape=box];
"Resolve input" -> "Phase 1: Discovery";
"Phase 1: Discovery" -> "Phase 2: Configure";
"Phase 2: Configure" -> "Phase 3: Write";
"Phase 3: Write" -> "Phase 4: Review";
"Phase 4: Review" -> "Approved?";
"Approved?" -> "Phase 3: Write" [label="revisions"];
"Approved?" -> "Phase 5: Output" [label="yes"];
}
Do NOT skip phases. Ask questions at a natural pace. If the user answers multiple questions at once, accept bundled answers and skip ahead.
If the user says "just pick defaults", "you choose", or similar, pick reasonable defaults based on context, state what you chose, and ask for a single confirmation before proceeding.
Never assume without confirming.
Phase 1: Discovery
Step 1 - Analyze the input
| Input type | What to read |
|---|---|
| Marketing brief | Extract problem statement, value prop, audience, key messages. Skip to Step 3. Still do Step 2 if brief lacks product context. |
| Blog post | Extract headline, key points, audience, CTA. Skip to Step 3. Still do Step 2 if lacking product context. |
| Changelog | Extract all entries. Use as the basis for a digest email. Skip to Step 3. |
| PR | Diff, PR description, review comments, commit messages (gh pr view, gh pr diff). For large PRs (20+ files), focus on user-facing changes. |
| Git refs | git diff and git log between refs. For large ranges, prioritize commit messages and user-facing changes. |
| Codebase feature | Read the specified files/directories. |
| Freeform text | Parse the user's description. If it lacks specifics, ask the user to provide more detail or point to a specific file/PR. Fall back to open-ended questions only if they can't. |
User-facing changes include: new features, UI changes, API changes, performance improvements, bug fixes, and documentation updates. Internal changes include: refactors, test additions, CI changes, and dependency bumps. When uncertain, list what you found and ask the user which are relevant.
Error handling:
ghnot available -> inform user, suggestgh auth login, offer alternative input- Invalid PR/ref -> ask user to verify
- File not found -> ask for correct path
Step 2 - Read broader product context
Read if they exist: README, docs/, package.json (or equivalent).
If nothing found, ask: "I couldn't find product context in the repo. Can you briefly describe the product and who it's for?"
Step 3 - Present understanding and determine format
Present a structured summary:
"Here's what I'll base the newsletter on:"
- Update A - short description
- Update B - short description
"Anything to add, remove, or correct?"
Then determine the email format based on the number of updates:
- Single major update -> single feature email (focused, deep)
- Multiple updates -> digest email (prioritized list, most important expanded)
Confirm the format with the user.
If no user-facing changes are found in the input, tell the user and stop: "No user-facing changes found in this input. Nothing to write a newsletter about."
Do NOT proceed until the user confirms scope and format.
Phase 2: Configuration
Ask these questions:
Q1 - Audience: "Who is this email going to?" (all users, power users, new users, specific plan tier, developers, non-technical users, other)
Q2 - Output format: "What format do you want the email in?"
- Copy only - subject line, preview text, body text, CTA text (drop into your email tool)
- Markdown - formatted markdown that most email tools can import
Q3 - Tone: Read existing repo content (README, docs, blog posts) to detect the product's voice. Then confirm:
"Based on your existing content, the tone seems [e.g. conversational and developer-friendly]. Should I match that or go a different direction?"
If no existing content to analyze, ask directly what tone the user wants.
Q4 - CTA: Infer the most appropriate call to action from context:
- New feature -> "Try it now", "See what's new"
- Improvement -> "Check it out", "See the difference"
- Open source -> "Update now", "See the release"
"I'd suggest the CTA be: [inferred CTA]. Want to go with that or something different?"
Phase 3: Write
Subject lines
Generate 3-5 subject line options with different approaches:
- Benefit-driven ("Your reports now export to PDF")
- Curiosity ("We rebuilt how search works")
- Specific feature name ("Introducing dark mode")
- Question ("Still waiting for exports to finish?")
- Urgency