| name | content-research-writer |
| description | Creates high-quality content (blog posts, tweets, newsletters, documentation) that matches the user's writing style and voice. Performs web research to find citations and supporting evidence. Use when user requests blog posts, marketing content, newsletters, tweets, or any written content that should sound authentic and be well-researched. |
Content Research Writer
This skill helps create compelling, well-researched content in the user's authentic voice. It avoids "AI slop" by analyzing writing samples, conducting research, and providing proper citations.
When to Use This Skill
Use this skill when the user requests:
- Blog posts or articles
- Marketing content
- Newsletters or email campaigns
- Social media posts (Twitter/X, LinkedIn)
- Technical documentation with research
- Product announcements
- Case studies or whitepapers
Workflow
1. Understand the Request
Clarify:
- Topic: What is the content about?
- Purpose: Why is this being written? (educate, market, inform, persuade)
- Audience: Who will read this?
- Tone: Professional, casual, technical, conversational?
- Length: Word count or section structure?
2. Analyze Voice (If Available)
If the user provides reference writing samples:
- Read existing content carefully
- Identify:
- Sentence structure patterns (short punchy vs long flowing)
- Vocabulary level and word choices
- Use of contractions, idioms, metaphors
- Paragraph rhythm and pacing
- How technical concepts are explained
- Emotional tone and energy level
- First person vs third person usage
3. Research Phase
Conduct thorough research:
- Use web search to find recent, relevant sources
- Look for:
- Statistics and data points
- Expert quotes and perspectives
- Recent news or developments
- Case studies or examples
- Contrarian viewpoints
- Prioritize authoritative sources:
- Academic papers
- Industry reports
- Official documentation
- Reputable news outlets
- Domain experts
4. Content Structure
Organize the content logically:
For Blog Posts:
- Hook (compelling opening)
- Problem/context
- Main points (3-5 key ideas)
- Supporting evidence with citations
- Conclusion/call-to-action
For Newsletters:
- Personal opening
- Main story or insight
- Supporting examples
- Practical takeaway
- Conversational close
For Technical Content:
- Clear problem statement
- Context and background
- Solution approach
- Implementation details
- Results and implications
5. Writing Guidelines
Voice Authenticity:
- Match the user's established patterns
- Use their vocabulary and phrasing
- Mirror their sentence structure
- Maintain their level of formality
- Replicate their storytelling style
Research Integration:
- Cite sources naturally in the flow
- Use block quotes sparingly (only for impactful statements)
- Paraphrase research findings in the user's voice
- Include [citation] markers or footnotes
- Link to sources when relevant
Avoid AI Slop:
- ❌ Generic platitudes ("In today's digital landscape...")
- ❌ Overused transitions ("Moreover," "Furthermore," "Additionally")
- ❌ Buzzword soup without substance
- ❌ Robotic, formal language when user is casual
- ❌ Formulaic introductions and conclusions
Do:
- ✅ Start with a specific, concrete hook
- ✅ Use concrete examples and stories
- ✅ Include surprising insights or data
- ✅ Make strong, opinionated claims (when appropriate)
- ✅ End with memorable takeaways
6. Citation Format
Inline Citations:
According to a 2024 Stanford study, AI-assisted coding increased productivity by 126% [1].
Footnote Style:
The foreclosure market in Brevard County grew 23% year-over-year.¹
---
¹ Florida Realtors Association, Q4 2024 Report
Link Style:
Research from [Anthropic's Claude usage report](https://example.com) shows...
Special Use Cases
Marketing Content
For content designed to acquire customers:
- Focus on specific pain points
- Include social proof and results
- Use storytelling over feature lists
- End with clear next steps
- Research competitor messaging
Technical Documentation
For developer or technical content:
- Include code examples
- Explain "why" not just "how"
- Use proper technical terminology
- Research current best practices
- Cite official documentation
Thought Leadership
For establishing expertise:
- Take strong, defensible positions
- Use original insights
- Challenge conventional wisdom thoughtfully
- Support claims with research
- Use compelling narratives
Quality Checklist
Before delivering content, verify:
Examples
Example 1: Marketing Blog Post
User Request: "Write a blog post about why property management is important for real estate investors. Use my newsletter style."
Research:
- Find vacancy rate statistics
- Look up property management cost data
- Find case studies of investor success/failure
- Research time commitment data
Output Structure:
- Hook with specific scenario
- Personal insight/story
- 3-4 key benefits with data
- Real example or case study
- Practical next steps
Example 2: Technical Tutorial
User Request: "Write about implementing Stripe webhooks correctly. Match my technical writing style."
Research:
- Official Stripe documentation
- Common webhook implementation mistakes
- Security best practices
- Testing approaches
Output Structure:
- Problem: why webhooks fail
- Core concepts explanation
- Step-by-step implementation
- Testing and verification
- Production considerations
Example 3: Newsletter
User Request: "Write a newsletter about Claude skills using my voice."
Research:
- Latest Claude skills documentation
- Community examples
- Usage statistics if available
- Developer testimonials
Output Structure:
- Personal discovery story
- Concrete examples of value
- Specific how-to
- What to try next
- Conversational sign-off
Tips for Best Results
- Provide reference samples: Share 2-3 examples of your writing
- Specify tone explicitly: "Technical but accessible" vs "casual and punchy"
- Indicate research needs: "Include stats" or "find case studies"
- Set word count: Helps structure appropriately
- Request citations: Be explicit if you want sources cited
