newsletter-writer
Write a full creator newsletter issue — subject line, preview text, hook, body with a clear takeaway, and a CTA — in the writer's voice, for Substack, beehiiv, ConvertKit, or email. Use when asked to write a newsletter, an email issue, a Substack post, or to turn notes/a topic into a sendable newsletter. Produces a ready-to-send issue with subject-line options and a skimmable structure. Distinct from B2B drip/nurture sequences.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/newsletter-writer && cp -r /tmp/newsletter-writer/plugins/pm-creator/skills/newsletter-writer ~/.claude/skills/newsletter-writerSKILL.md
# Newsletter Writer Skill
A newsletter is a relationship, not a broadcast. The best issues open a loop in the subject line, reward the open in the first sentence, deliver one clear idea, and make the next step obvious. This skill writes that issue — in your voice, ready to send.
## Working from a brief
Given a topic, notes, or a piece to adapt, **write the full issue anyway**. Infer the audience and the single idea; mark invented specifics *(assumed — replace)*. Don't hedge with "in this issue we'll explore…" — get to the value.
## Required Inputs
Ask for (if not already provided):
- **Topic / notes / source** for the issue
- **Audience** and **voice** (or pull from a [[creator-brand-kit]])
- **Goal / CTA** (reply, click, subscribe-upgrade, share) and rough **length**
- **Platform** (Substack / beehiiv / ConvertKit / plain email) for formatting norms
## Output Format
### Subject lines
**5 options**, mixing curiosity, specificity, and benefit — each ≤ ~50 characters. Star the recommended one.
### Preview text
One line (~80 chars) that complements (doesn't repeat) the subject.
### The issue
- **Hook** — first 1–2 sentences that reward the open and set up the idea.
- **Body** — one core idea, in short scannable paragraphs/sub-headers, with a concrete example or story. No throat-clearing.
- **The takeaway** — the one thing to remember, stated plainly (a callout line works well).
- **CTA** — a single clear next step matching the goal.
- **PS** — optional, often the most-read line; use it for a secondary nudge or personal note.
### Skim test
A 3-bullet "what a 5-second skimmer takes away" — if those bullets don't carry the value, restructure.
## Quality Checks
- [ ] Subject lines are specific and varied; the preview complements, not repeats
- [ ] The first sentence rewards the open (no "hope you're well, in today's issue…")
- [ ] One core idea, skimmable, with a concrete example
- [ ] A single clear CTA tied to the goal
- [ ] Reads in the creator's voice, not generic newsletter-ese
## Anti-Patterns
- A subject line that's a label ("Newsletter #42")
- Burying the value under a long personal preamble
- Three competing CTAs, or none
- A wall of text with no sub-heads or callout — unskimmableConduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.