tomevault-io 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:
- Hook - Why this matters (1-2 paragraphs)
- Problem Statement - What we're solving
- Solution Overview - High-level approach
- Implementation - Step-by-step with code
- Results/Demo - Show it working
- Conclusion - Key takeaways + next steps
- Resources - Links, docs, repos
Length: 1,000-2,500 words Tone: Conversational but technical
Blog Post (Thought Leadership)
Structure:
- Provocative opening - Challenge assumptions
- Context - Current state of things
- Thesis - Your perspective
- Supporting arguments (3-4)
- Counterarguments addressed
- Call to action
- 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:
- What we're building (with screenshot/demo)
- Prerequisites
- Setup steps
- Core implementation (chunked sections)
- Testing/verification
- Common issues + solutions
- Next steps / extensions
- 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"
Converted and distributed by TomeVault — claim your Tome and manage your conversions.