newsletter-creation-curation
Industry-specific newsletter creation with cadence recommendations and automation workflows
What this skill does
## **๐ฏ Multi-Dimensional Navigator**
**Newsletters serve different purposes depending on your context. Find your path:**
### **STEP 1: What's Your Goal?**
Your primary goal determines everything about your newsletter strategy:
```
โ LEAD GENERATION - Generate inbound leads for sales team
โ THOUGHT LEADERSHIP - Build authority in your category
โ PERSONAL BRAND - Build your individual reputation
โ CATEGORY OWNERSHIP - Own the conversation in your space
```
### **STEP 2: What's Your Industry Vertical?**
Your industry determines:
- Content topics and angle
- Competitive positioning
- Tone and risk tolerance
- What's considered "valuable content"
```
โ Sales Tech - Tactical sales tips, conversation intelligence insights
โ HR Tech - People operations, employee engagement, compliance
โ Fintech - Financial regulations, payment trends, compliance updates
โ Operations Tech - Retail execution, supply chain, distribution
```
### **STEP 3: What's Your Company Stage?**
Your stage determines:
- Newsletter goals (lead gen vs thought leadership)
- Resources available (time, budget)
- Publishing frequency
- Content depth
```
โ Series A ($1M-10M ARR) - Lead gen focus, founder-led
โ Series B ($10M-50M ARR) - Thought leadership, team-led
โ Series C+ ($50M+ ARR) - Category ownership, dedicated team
```
### **STEP 4: Are You Founder or Employee?**
Your role determines:
- Editorial autonomy
- Approval workflows
- Personal vs company brand
- What you can/cannot say
```
โ Founder - Full autonomy, personal = company brand
โ VP/Director - Partial autonomy, manager approval
โ PMM/Content Lead - Team collaboration, brand guidelines
โ Employee (Non-Leadership) - Significant constraints
```
### **STEP 5: What's Your Primary Market?**
Your geography determines:
- Publishing times (IST vs EST)
- Content examples (Indian vs US companies)
- Distribution channels (WhatsApp vs LinkedIn)
```
โ India-first - IST times, local examples, price-conscious
โ US-first - EST/PST times, US examples, premium positioning
```
---
## **Quick Navigation by Common Scenarios**
**Most Common Use Cases:**
1. **"I'm a Sales Tech founder, want to generate leads via newsletter"**
โ Go to: **Section A1** (Sales Tech, Series A, Lead Gen Focus)
2. **"I'm VP Marketing at Series B HR Tech, want thought leadership newsletter"**
โ Go to: **Section B2** (HR Tech, Series B, Thought Leadership)
3. **"I'm at Series C fintech, want to own the category conversation"**
โ Go to: **Section C3** (Fintech, Series C+, Category Ownership)
4. **"I'm PMM at ops tech, my VP wants me to start a newsletter"**
โ Go to: **Section D2** (Operations Tech, Employee-Led, Approval Workflows)
---
# ๐ SECTION A: SALES TECH NEWSLETTERS
**When To Use This Section:**
- Your product: Sales engagement, conversation intelligence, sales enablement
- Your audience: Sales leaders, CROs, SDR managers, AEs
- Your angle: Tactical sales tips, revenue growth, deal execution
- Tone: Aggressive, data-driven, ROI-focused
---
## **A1: Sales Tech @ Series A (Founder-Led Lead Generation)**
### **Your Reality Check:**
```
COMPANY PROFILE:
- Size: $1M-10M ARR, 10-100 employees
- Stage: Series A, need inbound leads
- You: Founder (or early marketing hire)
- Newsletter goal: Generate 10-20 SQLs per month
- Time available: 3-5 hours/week
- Budget: $0-200/month
```
### **The Sales Tech Newsletter Formula:**
**Why Sales Leaders Read Newsletters:**
```
SALES LEADERS DON'T READ:
โ Generic sales tips ("7 ways to close more deals")
โ Long-form essays (no time)
โ Theory without tactics
โ Anything that doesn't help THIS QUARTER
SALES LEADERS READ:
โ
Data-driven insights ("Gong analyzed 1M calls, here's what top reps do")
โ
Tactical playbooks (copy-paste into next call)
โ
Competitive intelligence (what competitors are doing)
โ
Quick wins (implement in <30 minutes)
```
### **Series A Sales Tech Newsletter Strategy:**
**GOAL: 10-20 SQLs per month from newsletter**
**Week-by-Week Startup Plan:**
```
WEEK 1: POSITIONING & SETUP (4 hours)
Day 1-2: Choose Your Angle (2 hours)
SALES TECH NEWSLETTER ANGLES:
Option 1: "Conversation Intelligence Insights"
- Example: Analyze sales calls, share patterns
- Audience: Sales leaders at B2B SaaS (50-500 employees)
- Frequency: Weekly
- Differentiator: Data-driven (use your product's data)
Option 2: "SMB Sales Playbook"
- Example: Tactical plays for small sales teams
- Audience: Founders, sales managers at startups
- Frequency: Weekly
- Differentiator: Practical, not theoretical
Option 3: "AI Sales Coaching"
- Example: How AI changes sales coaching
- Audience: Sales enablement leaders
- Frequency: Bi-weekly
- Differentiator: Future-focused, contrarian takes
YOUR DECISION:
Pick ONE angle. Stick to it for 12 weeks minimum.
Example: "AI Sales Coaching for SMB Teams"
Day 3: Setup Publishing (2 hours)
SALES TECH PUBLISHING OPTIONS:
FREE OPTIONS:
โก LinkedIn Newsletter (RECOMMENDED for Sales Tech)
- Why: Your audience is already on LinkedIn
- Setup: 15 minutes
- Reach: Notifies your connections
- Downside: LinkedIn owns the list
โก Substack (RECOMMENDED if building owned list)
- Why: Own your subscribers, email delivery
- Setup: 30 minutes
- Cost: Free (5% fee on paid subscriptions)
- Downside: Cold start (need to drive traffic)
โก Medium (NOT RECOMMENDED)
- Why: Audience is too broad, not B2B sales-focused
- Skip this for Sales Tech
HYBRID APPROACH (BEST):
- Publish on Substack (own the list)
- Cross-post to LinkedIn (distribution)
- Repurpose on Twitter threads (amplification)
SETUP CHECKLIST:
โก Substack account created
โก Newsletter name: [Your Angle] Newsletter
Example: "The AI Sales Coach" or "SMB Sales Playbook"
โก About section: 2-3 sentences on who it's for
โก First post published: "Issue #0: What to expect"
```
**WEEK 2: WRITE & PUBLISH ISSUE #1 (4 hours)**
```
Monday: Research & Outline (1 hour)
SALES TECH CONTENT SOURCES:
PRIMARY (Use These):
โก Gong blog (conversation intelligence leader)
โก Sales Hacker (community content)
โก r/sales on Reddit (real sales rep pain points)
โก Your own sales calls (if you have product data)
โก Customer interviews (ask: "What's your biggest sales challenge?")
SECONDARY (Reference):
โก Pavilion community (CRO insights)
โก SaaStr blog (B2B SaaS sales)
โก LinkedIn posts from sales leaders (Jason Lemkin, Jacco van der Kooij)
WHAT TO LOOK FOR:
- Data-driven insights (numbers, stats, research)
- Contrarian takes (what everyone gets wrong)
- Tactical playbooks (step-by-step processes)
Tuesday-Wednesday: Write Issue #1 (2 hours)
SALES TECH NEWSLETTER STRUCTURE:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ SUBJECT LINE (Critical for Sales Tech) โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ โ BAD: "Issue #1: Sales Tips" โ
โ โ
GOOD: "Why 73% of SDRs fail [data]" โ
โ โ
GOOD: "The 2-minute discovery hack" โ
โ โ
GOOD: "Gong is wrong about cold calls"โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
FORMAT (600-900 words):
**OPENING HOOK (50-100 words)**
Start with: Data point, contrarian take, or bold claim
Example:
"Gong analyzed 1 million sales calls and found the average
discovery call is 38 minutes. But the top 10% of reps?
They keep it under 25 minutes. Here's why..."
**THE INSIGHT (200-300 words)**
Explain the data or framework
Use: Numbers, quotes, examples
Avoid: Fluff, generic advice
**THE TACTICAL PLAYBOOK (250-400 words)**
Step-by-step: How to apply this
Format:
1. Preparation: What to do before
2. Execution: How to do it
3. Follow-up: What happens after
**THE CALL TO ACTION (50-100 words)**
Next step for reader:
- Try this technique
- Reply with your experience
- Book a demo (if relevant - sparingly)
Thursday: Edit & Polish (30 minutes)
SALES TECH EDITING CHECKLIST:
โก Cut 30% of words (sales leaders are busy)
โก Check: Every paragraph has data or tactics
โก Remove: Theory, fluff, obvious advice
โก Add: Specific numbers, examples, names
โก Verify: All claims have sources
Friday: Publish (30 minutes)
TIMING (CRITIRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing โ use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.