Writes opinion pieces and thought leadership articles that position the author as an industry authority. Use when you need to publish a strong perspective on an industry topic.
Use this skill when you need to:
DO NOT use this skill for how-to content, listicles, or neutral informational articles. This is for opinion-driven, authority-building pieces.
THOUGHT LEADERSHIP WITHOUT A CLEAR OPINION IS JUST CONTENT — THE AUTHOR MUST TAKE A POSITION AND DEFEND IT WITH EVIDENCE AND EXPERIENCE.
| Input | What to Ask | Default |
|---|
| Topic / position | "What is your opinion or argument?" | No default — must be provided |
| Why now | "Why is this relevant right now?" | Industry trend or recent event |
| Author's credibility | "What experience qualifies you to have this opinion?" | No default — must be provided |
| Target audience | "Who should read this and be influenced by it?" | Industry peers and potential clients |
| Publication | "Where will this be published? Blog, LinkedIn, industry publication?" | Blog |
| Word count | "Target length?" | 1,200-1,800 words |
GATE: Confirm brief before outlining.
**H1:** [Declarative title that states the position]
**Hook** (~150 words) — Story, observation, or bold claim that sets up the argument
**H2: The Current State** (~300 words) — What most people believe or do today
**H2: Why That's Wrong / Incomplete** (~400 words) — The author's contrarian perspective with evidence
**H2: What I've Seen / Done Instead** (~400 words) — Personal experience and results
**H2: What This Means for You** (~300 words) — Practical implications for the reader
**Conclusion** (~150 words) — Restate the position and call to action
GATE: Approve outline before writing.
| Rule | Detail |
|---|---|
| State the opinion early | The reader should know your position within the first 3 paragraphs |
| First person required | Thought leadership demands personal voice — "I believe," "In my experience" |
| Evidence for every claim | Data, case studies, or personal results back every argument |
| Acknowledge the other side | Address counterarguments directly — it strengthens your position |
| No hedging | "I think this might possibly be..." kills authority. State opinions confidently. |
| Concrete examples | Abstract opinions are forgettable. Specific stories and numbers are memorable. |
| End with implications | Tell the reader what to DO with this perspective |
Rate the piece before delivering:
Target Level 2-3 for maximum thought leadership impact.
[HOOK: Specific moment, observation, or bold claim]
[THE CONVENTIONAL WISDOM: What most people believe about this topic]
[THE PROBLEM: Why that belief is wrong, incomplete, or outdated]
- [Evidence point 1]
- [Evidence point 2]
- [Personal experience or data]
[THE ALTERNATIVE: What the author does/believes instead]
- [How it works]
- [Results achieved]
- [Why it's better]
[COUNTERARGUMENT: The strongest objection and your response to it]
[IMPLICATIONS: What this means for the reader and what they should do]
[CLOSE: Restate the position in one powerful sentence]
## Quality Checklist
- [ ] Author's position is clear within the first 3 paragraphs
- [ ] At least one contrarian or non-obvious insight
- [ ] Every claim is backed by evidence (data, experience, or case study)
- [ ] Counterarguments are acknowledged and addressed
- [ ] Written in first person with personal voice
- [ ] No hedging language ("might," "could possibly," "it seems")
- [ ] Ends with practical implications for the reader
- [ ] Opinion strength is Level 2 or 3
- [ ] Article would generate discussion if posted on LinkedIn
- [ ] Author's credibility is established early
Position: Obsessive A/B testing wastes more money than it saves for small businesses
Credibility: Ran 200+ A/B tests over 3 years at a 7-figure e-commerce company
Evidence: 80% of tests were inconclusive, opportunity cost of test setup exceeded gains
Outline:
Hook: "I spent $40K on A/B testing last year. Net revenue impact: -$12K."
Current state: The industry worships A/B testing as the path to optimization
Why it's wrong: At small traffic levels, most tests never reach significance
What I do instead: Make decisive changes based on qualitative data and customer conversations
Implications: Stop testing everything. Start listening to customers.