content-research-writer

name	content-research-writer
description	Research topics deeply and create compelling content including blog posts, Reddit campaigns, technical articles, and educational materials. Use for marketing and developer advocacy content.

Content Research Writer

Research topics thoroughly and produce high-quality written content for developer relations, marketing, and community building.

When to Use This Skill

Use this skill when you need to:

• Write blog posts or articles
• Create Reddit marketing posts
• Develop technical tutorials
• Write educational content
• Create social media thread content
• Research competitive landscape
• Produce thought leadership pieces

Research Process

1. Topic Analysis

• Identify core concepts and terminology
• Find related topics and tangents
• Understand target audience knowledge level
• Locate authoritative sources

2. Source Gathering

• Official documentation
• GitHub repositories and READMEs
• Developer blogs and tutorials
• Community discussions (Reddit, forums, Nostr)
• Academic papers (if applicable)
• Competitor content

3. Synthesis

• Extract key insights
• Identify unique angles
• Find gaps in existing content
• Develop original perspective

Content Types

Blog Post (Technical)

Structure:

1. Hook - Why this matters (1-2 paragraphs)
2. Problem Statement - What we're solving
3. Solution Overview - High-level approach
4. Implementation - Step-by-step with code
5. Results/Demo - Show it working
6. Conclusion - Key takeaways + next steps
7. Resources - Links, docs, repos

Length: 1,000-2,500 words Tone: Conversational but technical

Blog Post (Thought Leadership)

Structure:

1. Provocative opening - Challenge assumptions
2. Context - Current state of things
3. Thesis - Your perspective
4. Supporting arguments (3-4)
5. Counterarguments addressed
6. Call to action
7. Discussion prompt

Length: 800-1,500 words Tone: Confident, informed, accessible

Reddit Post (Marketing)

Format:

• Eye-catching title (not clickbait)
• Brief context (2-3 sentences)
• Value proposition (what's in it for reader)
• Key features/benefits (bullet points OK here)
• Call to action
• Engagement question

Tone: Authentic, not salesy, community-minded Note: Disclose affiliation when appropriate

Technical Tutorial

Structure:

1. What we're building (with screenshot/demo)
2. Prerequisites
3. Setup steps
4. Core implementation (chunked sections)
5. Testing/verification
6. Common issues + solutions
7. Next steps / extensions
8. Full code repository link

Length: 2,000-4,000 words Include: Code blocks, screenshots, diagrams

Twitter/Nostr Thread

Format:

• Hook tweet (standalone value)
• Context tweet
• 3-7 main points (1 idea per tweet)
• Summary/takeaway
• CTA (follow, try it, join community)

Each tweet: 280 chars max, can include media

Writing Guidelines

Voice & Tone

• Authentic - Write like a human, not a corporation
• Helpful - Focus on reader value
• Technical but accessible - Explain jargon
• Enthusiastic without hype - Show genuine excitement

SEO Considerations

• Use target keywords naturally
• Descriptive headers (H2, H3)
• Meta description (150-160 chars)
• Internal/external links
• Alt text for images

Developer Advocacy Specifics

• Lead with problems, not products
• Show, don't tell (demos > claims)
• Acknowledge limitations honestly
• Include working code examples
• Link to documentation

Content Calendar Integration

When planning content:

• Align with product launches
• Tie to conferences/events
• Consider seasonal trends
• Build on previous content
• Plan series for complex topics

Example Prompts This Skill Handles

• "Write a blog post about building on Nostr"
• "Create a Reddit post promoting Shakespeare"
• "Research the Lightning Network ecosystem and write an overview"
• "Draft a tutorial for using Blossom for media storage"
• "Write a Twitter thread explaining why Nostr matters"