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 — unskimmableDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.