newsletter-creation-curation · diff
git:20260225.733acad to git:20260308.5724749
184 added, 156 removed. Audit A to A.
---
name: newsletter-creation-curation
description: Industry-adaptive B2B newsletter creation with stage, role, and geography-aware workflows
+ metadata: {"clawdbot":{"emoji":"📧","homepage":"https://github.com/shashwatgtm","always":true}}
---
# Newsletter Creation & Curation Skill
Use this skill to create B2B newsletters that match business context, not generic content templates.
Deep strategic guidance is in `PLAYBOOK.md`.
Use this file as the executable operating manual.
- ---
-
- ## Context Loading Gates
-
- **Before generating any newsletter content, collect:**
-
- - [ ] **Company context:** What product/service? Who is the ICP?
- - [ ] **Newsletter goal:** Lead gen / thought leadership / personal brand / category ownership
- - [ ] **Industry vertical:** Sales Tech / HR Tech / Fintech / Operations Tech
- - [ ] **Company stage:** Series A / Series B / Series C+
- - [ ] **Role:** Founder / VP-Director / PMM-Content / Enterprise employee
- - [ ] **Geography:** US-first / India-first
- - [ ] **Prior issues:** Any existing issues to maintain consistency and voice?
- - [ ] **Approval constraints:** Does this need legal/brand/manager review?
-
- **Structured intake — answer all 5 dimensions before proceeding:**
-
- ```
- Goal: [lead_gen | thought_leadership | personal_brand | category_ownership]
- Industry: [sales_tech | hr_tech | fintech | ops_tech]
- Stage: [series_a | series_b | series_c_plus]
- Role: [founder | vp_director | pmm_content | enterprise_employee]
- Geography: [us_first | india_first]
- ```
-
- ---
-
- ## Phase 1: Context Analysis
-
- Before drafting, reason through:
-
- 1. **Template match:** Which industry template best fits? (Sales Tech = data-heavy; HR Tech = research-led; Fintech = compliance-aware; Ops Tech = practical)
- 2. **Cadence match:** Series A = weekly/bi-weekly for simplicity; Series B = weekly with process; Series C+ = media-grade weekly with pillars
- 3. **Role constraints:** Founder = direct POV allowed; Employee = approval checkpoint required before final draft
- 4. **Geography adjustments:** India-first = IST timing + local examples; US-first = EST/PST + US benchmarks
- 5. **Goal-content alignment:** Lead gen needs a clear conversion CTA; thought leadership needs original insight, not general content
-
- Output one-line strategy statement:
- > `For [ICP], we publish [cadence] to achieve [goal] with [format].`
-
- ---
-
- ## Phase 2: Issue Blueprint
-
- Before writing full draft, produce an issue blueprint:
-
- ```markdown
- ## Issue Blueprint
+ ## Mode
- **Strategy:** For [ICP], [cadence] to achieve [goal].
- **Industry tone:** [tactical/research-led/compliance-aware/practical]
- **Approval required:** [yes/no — who]
+ Detect from context or ask: *"Outline only, full edition, or full edition + calendar?"*
- **Sections:**
- 1. Subject lines (3 options) — [~words each]
- 2. Hook — [target ~75 words]
- 3. Core insight — [target ~200 words]
- 4. Actionable playbook — [target ~150 words, 3-5 steps]
- 5. CTA — [1 sentence, singular action]
- ```
+ | Mode | What you get | Best for |
+ |------|-------------|----------|
+ | `quick` | Edition outline + 3 lead story angles, no writing | Planning, editorial direction |
+ | `standard` | Full newsletter edition, all sections written | Publishing this week |
+ | `deep` | Full edition + 4-week content calendar + audience segmentation recommendations | Launching or systematizing a newsletter |
- Get confirmation or proceed to draft.
+ **Default: `standard`** — use `quick` if they're still deciding what to write. Use `deep` if they're building a newsletter from scratch or scaling.
---
- ## Phase 3: Full Issue Draft
+ ## Quick Decision Tree (5 Dimensions)
- Generate complete publish-ready draft. Required structure — every issue:
+ Answer these in order before writing anything.
- ### Subject Line Options (3 required)
- Produce 3 distinct angles:
- - A: Curiosity/open loop ("The metric most [ICP] ignore")
- - B: Specific + benefit ("How [Company type] achieves [X] in [timeframe]")
- - C: Contrarian/bold ("Stop [common behavior]. Do this instead.")
+ ### 1) Goal
+ - `Lead Generation`: newsletter should drive pipeline and SQLs.
+ - `Thought Leadership`: newsletter should build trust and category authority.
+ - `Personal Brand`: newsletter should establish individual POV and visibility.
+ - `Category Ownership`: newsletter should define market narrative at scale.
- ### Hook
- - First 2 sentences must earn the read
- - Lead with the problem + stakes
- - Target: busy reader can extract the point in 60 seconds
+ ### 2) Industry
+ - `Sales Tech`: tactical, data-heavy, ROI-forward.
+ - `HR Tech`: research-led, professional, trust-first.
+ - `Fintech`: compliance-aware, conservative claims.
+ - `Operations Tech`: domain-specific, practical playbooks.
- ### Core Insight
- - One primary takeaway per issue — not three
- - Support with: data, framework, or named pattern
- - Include specific numbers or named examples wherever possible
+ ### 3) Company Stage
+ - `Series A`: founder-led, lean, weekly or bi-weekly.
+ - `Series B`: team-led, stronger editorial process, analytics discipline.
+ - `Series C+`: media-grade quality, original research, category narrative.
- ### Actionable Playbook
- - 3-5 steps or checklist items
- - Each step must be implementable, not just conceptual
- - Series A = simpler steps; Series C+ = more sophisticated process
+ ### 4) Role
+ - `Founder`: highest autonomy, fastest execution.
+ - `VP/Director`: medium autonomy, stakeholder review expected.
+ - `PMM/Content`: structured approvals, brand constraints.
+ - `Enterprise employee`: PR/legal gatekeeping likely required.
- ### CTA
- - ONE measurable action only
- - Options: reply with [X], click [link], share [asset], book [demo]
- - Never use vague CTAs ("Learn more")
+ ### 5) Geography
+ - `India-first`: IST timing, local examples/channels.
+ - `US-first`: EST/PST timing, US benchmarks/channels.
- ---
+ ## Template Selector
- ## Phase 4: Refinement Checklist
+ Pick exactly one base template first:
+ - Sales Tech: `templates/sales-tech-template.md`
+ - HR Tech: `templates/hr-tech-template.md`
+ - Fintech: `templates/fintech-template.md`
+ - Operations Tech: `templates/ops-tech-template.md`
- Run before delivering:
+ Then adapt cadence and tone using Stage + Role + Geography.
- - [ ] `Clarity`: Can a busy reader extract value in 60 seconds?
- - [ ] `Specificity`: Does each section include concrete guidance or evidence?
- - [ ] `Relevance`: Does tone match industry and role constraints?
- - [ ] `Compliance`: For fintech/employee-led, is a legal/manager review step included?
- - [ ] `Consistency`: Does voice align with prior issues (if any were provided)?
- - [ ] `CTA`: Is there exactly ONE measurable CTA — not two, not zero?
+ ## Execution Workflow (Do This Every Time)
- ---
+ ### Step 1: Assess Context
+ Collect and confirm:
+ - Product category and ICP.
+ - Primary goal for the next 90 days.
+ - Stage, role, approval constraints.
+ - Geography and timezone.
+ - Available production bandwidth (hours/week, team, budget).
- ## Phase 5: Self-Critique Pass (REQUIRED)
+ Output:
+ - One-line strategy statement: `For [ICP], we publish [cadence] to achieve [goal] with [format].`
- After completing the draft, evaluate:
+ ### Step 2: Select and Adapt Template
+ Actions:
+ - Load one industry template from `templates/`.
+ - Set cadence:
+ - Series A: weekly/bi-weekly (execution simplicity).
+ - Series B: weekly or bi-weekly (team process).
+ - Series C+: weekly with recurring pillars (media-quality).
+ - Apply role constraints:
+ - Founder: direct POV is allowed.
+ - Employee: insert approval checkpoint before final draft.
+ - Apply geography settings:
+ - India-first: schedule in IST and local references.
+ - US-first: schedule in EST/PST and US references.
- - [ ] Does the subject line A option create genuine curiosity without being clickbait?
- - [ ] Does the hook deliver a problem + stakes in the first 2 sentences?
- - [ ] Is the core insight something subscribers couldn't get from a generic AI prompt?
- - [ ] Does the playbook have steps that are specific to this audience, not generic "tips"?
- - [ ] Is the CTA actually measurable — i.e., can they track whether it worked?
- - [ ] For fintech/employee contexts: is there an explicit approval checkpoint?
+ Output:
+ - Final issue blueprint with section headings + target word count per section.
- Flag any issue: "The playbook steps are too generic for a Series B SaaS audience — they read as beginner content. Revised to assume existing process maturity."
+ ### Step 3: Generate Content
+ Use the blueprint to draft issue content.
- ---
+ Required structure:
+ - Subject line options (3)
+ - Hook (problem + stakes)
+ - Core insight (data, framework, or pattern)
+ - Actionable playbook (steps/checklist)
+ - CTA (reply, share, demo, resource)
- ## Iteration Protocol
+ Generation rules:
+ - Prefer specific numbers, examples, and named scenarios.
+ - Remove generic filler.
+ - Keep one primary takeaway per issue.
+ - Keep CTA singular and measurable.
- After delivering the draft:
- 1. Ask: "Does the hook earn the read? Does the playbook feel actionable for your audience?"
- 2. If hook is weak → rewrite using a different angle (data-led, story-led, or contrarian)
- 3. If playbook is too generic → ask for a specific example from their own experience to ground it
- 4. For next issue: "Want me to save these content themes so the next issue builds on this one?"
+ Output:
+ - Draft issue in publish-ready markdown.
- ---
+ ### Step 4: Refine and Ship
+ Run this checklist:
+ - `Clarity`: can a busy reader extract value in 60 seconds?
+ - `Specificity`: does each section include concrete guidance or evidence?
+ - `Relevance`: does tone match industry and role constraints?
+ - `Compliance`: for fintech/employee-led, ensure legal/manager review step exists.
+ - `Consistency`: voice aligns with prior issues.
- ## Output Structure
+ Finalize:
+ - Choose one subject line.
+ - Add final send time.
+ - Add amplification plan (LinkedIn + one secondary channel).
- ```markdown
- ## Newsletter Issue: [Name] — Issue #[X] — [Date]
- **Strategy:** For [ICP], [cadence] to achieve [goal].
+ Output:
+ - Final issue + distribution notes + KPI targets.
- ---
+ ## Role-Based Approval Workflow
- ### Subject Line Options
- A) [Curiosity/open loop]
- B) [Specific + benefit]
- C) [Contrarian/bold]
- **Recommended:** [A/B/C] — [reason]
+ Use this enforcement logic before publishing:
+ - Founder-led:
+ - No formal approval required.
+ - Optional peer review for quality.
+ - VP/Director-led:
+ - Manager or leadership review required.
+ - High-impact claims should be validated.
+ - PMM/Content-led:
+ - Brand + stakeholder review required.
+ - Keep documented source notes for claims.
+ - Enterprise employee:
+ - PR/legal review required before distribution.
- ---
+ If unsure, default to stricter review.
- ### Hook
- [2-3 sentences — problem + stakes]
+ ## KPI Defaults by Goal
- ---
+ - Lead Generation:
+ - Open rate, CTR, demo requests, SQL mentions in CRM.
+ - Thought Leadership:
+ - Open rate trend, replies, shares, speaking invites, inbound references.
+ - Personal Brand:
+ - Subscriber growth, profile visits, inbound opportunities.
+ - Category Ownership:
+ - Share of voice, citations, partnerships, executive visibility.
- ### Core Insight
- [200-300 words — data, framework, or named pattern]
+ ## Playbook Map (Deep Dives)
- ---
+ Use these sections in `PLAYBOOK.md` when deeper strategy is needed:
+ - Sales Tech strategy: `SECTION A`
+ - HR Tech strategy: `SECTION B`
+ - Fintech strategy: `SECTION C`
+ - Operations Tech strategy: `SECTION D`
+ - Role approvals and geography tactics: `CROSS-CUTTING: UNIVERSAL FRAMEWORKS`
+ - Mistakes, prompts, tool matrix, quick-reference matrix: bottom sections of `PLAYBOOK.md`
- ### Actionable Playbook
- 1. [Step]
- 2. [Step]
- 3. [Step]
+ ## Why This vs Generic ChatGPT Prompting?
- ---
+ This skill adds structured context control that generic prompting usually misses:
+ - Matches content to `industry + stage + role + geography` before drafting.
+ - Forces approval logic for employee-led and fintech scenarios.
+ - Uses proven templates tied to B2B newsletter outcomes.
+ - Produces repeatable workflows, not one-off writing outputs.
+ - Keeps strategic depth in `PLAYBOOK.md` for escalation without bloating execution steps.
- ### CTA
- [Single measurable action]
+ ## Fictional Case Study (Realistic)
- ---
+ ### Context
+ - Company: `SignalPilot` (Sales Tech)
+ - Stage: Series A, $4M ARR
+ - Role: Founder-led
+ - Market: US-first
+ - Goal: 12 SQLs/month from newsletter in 6 months
+ - Bandwidth: 4 hours/week, no designer
- ### Distribution Plan
- - **Send time:** [Day, Time, Timezone]
- - **LinkedIn amplification:** [Post angle / hook]
- - **Secondary channel:** [Platform + angle]
+ ### What They Did
+ - Selected `templates/sales-tech-template.md`.
+ - Published weekly on Tuesday 9 AM EST.
+ - Issue mix:
+ - 50% data-backed sales observations
+ - 30% tactical playbooks
+ - 20% contrarian POV
+ - Reused each issue for one LinkedIn post + one short thread.
- ### KPI Targets
- - Open rate goal: [%]
- - CTR goal: [%]
- - Primary metric: [SQLs / subscribers / replies]
+ ### Outcome (6 Months)
+ - 1,350 subscribers.
+ - Average 42% open rate, 8.1% CTR.
+ - 14 monthly SQLs tagged as newsletter-influenced.
+ - Sales team started using issues as pre-demo credibility assets.
- ### Approval Required
- [Yes — [who] | No]
+ ## Usage Examples
- ### Self-Critique Notes
- [Issues flagged + revisions made]
+ ### Example A: Founder, Sales Tech, Series A
+ Prompt:
+ ```text
+ Use newsletter-creation-curation.
+ Context: Sales tech founder, Series A, US market, lead generation goal.
+ Create next week's issue using the sales-tech template, with 3 subject lines,
+ 700-900 words, and a Tuesday 9 AM EST send plan.
```
- ---
-
- ## Playbook Map (Deep Dives in `PLAYBOOK.md`)
+ ### Example B: VP Marketing, HR Tech, Series B
+ Prompt:
+ ```text
+ Use newsletter-creation-curation.
+ Context: HR tech VP Marketing, Series B, US-first, thought-leadership goal.
+ Create a bi-weekly issue outline and full draft with approval checkpoints and
+ source-backed claims only.
+ ```
- - Sales Tech strategy: `SECTION A`
- - HR Tech strategy: `SECTION B`
- - Fintech strategy: `SECTION C`
- - Operations Tech strategy: `SECTION D`
- - Role approvals and geography tactics: `CROSS-CUTTING: UNIVERSAL FRAMEWORKS`
+ ### Example C: PMM, Fintech, Series B, India
+ Prompt:
+ ```text
+ Use newsletter-creation-curation.
+ Context: Fintech PMM, Series B, India-first, trust-building goal.
+ Build issue draft with compliance-safe language, IST send timing, and
+ manager/legal review checklist.
+ ```
- ---
+ ## Fast Start (Agent Checklist)
- *Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*
+ 1. Ask 5 decision-tree questions.
+ 2. Select one industry template from `templates/`.
+ 3. Produce issue blueprint (sections + word counts).
+ 4. Draft issue using the workflow.
+ 5. Apply role/compliance review.
+ 6. Finalize send-time, amplification, and KPI targets.
+ 7. If deeper strategy is needed, consult `PLAYBOOK.md`.