Agent skill
thought-leadership
Creates value-packed, niche-specific, thought leadership newsletters (800-1,500 words) with irresistible subject lines, skimmable headers, and actionable content. Uses proven frameworks for headlines, introductions, and sectioning. Use when user mentions "write newsletter", "thought leadership content", "weekly newsletter", or wants to create educational, value-driven newsletter content.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/thought-leadership-alexmcfarland-ai-co-writer-plugins
SKILL.md
Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work
- BUSINESS.md — their business, products, positioning, brand voice, content strategy
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all context silently. Do not reference or summarize files unless asked.
Newsletter: Thought Leadership
Purpose: Write value-packed, niche-specific, thought leadership weekly newsletters (800-1,500 words) that educate, engage, and position the writer as an authority.
When to Activate
Use this skill when:
- User asks to write a newsletter or weekly email
- User mentions "thought leadership" or "educational newsletter"
- User wants to create value-packed content for their audience
- User provides a topic/idea and wants a full newsletter written
- User says "write my weekly email" or similar
Core Philosophy
This is NOT basic email writing. This is:
- Thought leadership — establishing authority and expertise
- Value-packed — tangible, tactical, actionable content
- Skim-optimized — headers alone deliver 80% of value
- Niche-specific — targeted to specific audience needs
Length: 800-1,500 words
The 4 Fundamental Variables
Variable 1: Subject Line (Irresistible Headline)
Variable 2: Introduction (Hook + Promise)
Variable 3: Headers (3-10 sections, skimmable)
Variable 4: Section Content (Tactical, actionable insights)
Workflow
Step 1: Load Context Profiles
Before starting, load all context profiles provided in the task.
Step 2: Craft Subject Line Options
Generate 5 subject line variations using the Irresistible Headline Framework:
The 6-Piece Framework:
- HOW MANY (Number) — Usually 2-19
- THE WHAT (Topic) — The subject matter
- THE HOW (Proven Approach) — Tips, Steps, Mistakes, Lessons, Benefits, Reasons, etc.
- THE WHO (Audience) — Specific target reader
- THE WHY (Outcome) — Tangible result they want
- TWIST THE KNIFE (More Outcomes) — 1-3 additional outcomes
Example: "7 Copywriting Tips For Beginners To Sell Your First $100 Digital Product, Start Making Money Online, And Eventually Quit Your Job"
Subject Line Requirements:
- Length: 30-50 characters or 4-8 words
- Case: sentence-case (first word capitalized, rest lowercase)
- Exception: If starts with number, don't capitalize next word
- Good: "3 ways to land your first ghostwriting client"
- Bad: "3 Ways To Land Your First Ghostwriting Client"
Tangible vs. Intangible Outcomes:
- ❌ Intangible: "So you can be happier"
- ✅ Tangible: "So you can wake up every morning feeling full of energy"
Step 3: Write the Introduction (5 Blocks)
Block 1: Greeting
Format: "Hey there!" or similar friendly opening
Block 2: Opening Hook (1 sentence)
Choose ONE approach:
- Ask a thought-provoking question
- Strong, declarative sentence
- Reference a meaningful moment in time
- Present a vulnerable statement
- Offer a controversial opinion
- Share a unique insight
Block 3: The Promise (3-7 sentences OR bullets)
Educate on:
- Problem: The niche-specific problem(s) readers face, why they exist, negative outcomes
- OR Outcome: The desirable outcome(s) readers want, why valuable, consequences of not achieving
Block 4: The Solution (1-2 sentences)
State what you're going to help them with today.
Block 5: Transition (1 sentence)
Bridge to the main content.
Examples: "Let's walk through each one." / "Let's dive in!" / "So, with that in mind, let's solve that problem."
Step 4: Create Headers (3-10 Sections)
The 10 Magical Ways to Expand Anything:
- Tips
- Stats
- Steps
- Lessons
- Benefits
- Reasons
- Mistakes
- Examples
- Questions
- Personal Stories
Header Guidelines:
- Format: Sentence Style — full complete sentence, first word capitalized, punctuation at end
- Goal: Deliver promise in headers alone (reader gets 80% value from just reading headers)
- Bolded: All headers should be bold (H3 format: ###)
- Promise alignment: Headers must clearly deliver on the promise from subject line/intro
Number of sections:
- More sections (7-10) = headers deliver most value, less detail in each section
- Fewer sections (3-5) = more room to elaborate tactically in each section
Step 5: Write Section Content
Section Structure:
- Opening: Single-sentence opener
- Middle: Prose + ONE bulleted list per section (use sparingly)
- Closing: Single-sentence closer
- Rhythm: Alternate between long and short sentences for pacing
Content Criteria:
- How-to focused: Make it actionable/instructional (tips, steps, reasons, examples)
- Why-focused: Make it explanation-focused (stats, lessons, benefits, mistakes)
- Specificity: Very specific, tangible, tactical, differentiated insights
- No fluff: Every sentence should add value
- Skimmable: Easy to scan and extract value quickly
Step 6: Format for Email Delivery
Email Formatting:
- Headers: Bold (### format or text)
- Paragraphs: Short (1-3 sentences max)
- Bullets: Use for lists of examples or options
- Links: Include where mentioned
- Italics: Use sparingly for emphasis
- White space: Line breaks between sections
Output Format
## Subject Line Options
1. [Option 1 in sentence-case]
2. [Option 2 in sentence-case]
3. [Option 3 in sentence-case]
4. [Option 4 in sentence-case]
5. [Option 5 in sentence-case]
**Recommended**: Option [X] - [Brief reasoning why]
---
## Newsletter: [Chosen Subject Line]
**Word count**: ~[X] words
---
Hey there!
[Opening hook - 1 sentence]
[Promise block - 3-7 sentences explaining the problem or outcome]
[Solution - 1-2 sentences stating what you'll deliver]
[Transition - 1 sentence]
### [Header 1: Full sentence delivering on promise.]
[Single sentence opener]
[2-3 sentences of explanation/context]
[Optional bulleted list if applicable]
[Single sentence closer or transition]
### [Header 2: Full sentence delivering on promise.]
[Continue pattern for all sections...]
---
**Stats**: [X] words | [X] sections | [X] key takeaways
Quality Checklist
Before delivering:
- 5 subject line options presented (sentence-case)
- Subject line uses irresistible headline framework
- Introduction follows 5-block structure
- 3-10 headers that deliver promise in sentence format
- Headers alone provide 80% of value
- Each section starts and ends with single sentence
- Content is tactical, actionable, specific (no fluff)
- Bulleted lists used sparingly (max one per section)
- Length is 800-1,500 words
- Skimmable and easy to read
- Formatted for email (bolded headers, line breaks)
Best Practices
Subject lines:
- Test multiple options
- Tangible outcomes beat vague promises
- Numbers work well (3, 5, 7, 10)
- Sentence-case feels more personal
Content:
- Value-first, always
- No fabricated stories unless user provides them
- Use user's unique insights and angle
- Make it actionable — readers should know what to do
- Examples and specifics trump generalizations
Voice:
- Conversational but authoritative
- Helpful teacher, not corporate marketer
- Direct and to the point
- Personality encouraged (based on context)
Remember: Thought leadership newsletters establish authority through value delivery. Every section should make the reader think "This is exactly what I needed" and position you as the expert who helped them.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?