mohitagw15856/newsletter-writer
plugins/pm-creator/skills/newsletter-writer/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills newsletter-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 22, 2026, 6:58 AM249.0s1 file scanned
SKILL.md
- name:
- newsletter-writer
- description:
- 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.
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 — unskimmable
Related Skills
mohitagw15856/win-loss-analysis
business
VerifiedTrustedCommunity
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/which-skill
development
VerifiedTrustedCommunity
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/vuln-triage
testing
VerifiedTrustedCommunity
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/voice-of-customer-program
development
VerifiedTrustedCommunity
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.
1,117SKILL.mdUpdated Jul 2, 2026