Content Research Writer

Transform writing from a solitary activity into a collaborative process. This skill provides research assistance, structural guidance, citation management, and iterative feedback while preserving your unique voice and style.

Perfect for bloggers, technical writers, researchers, and content creators who want AI assistance without losing their authentic voice.

Core Features

Collaborative Writing Tools

Outlining & Structure:

Build coherent frameworks from ideas
Identify logical flow and research gaps
Mark sections needing deeper exploration

Research & Citations:

Locate credible sources
Extract key facts and quotations
Format citations (inline, numbered, footnotes)

Hook Enhancement:

Strengthen introduction impact
Test curiosity generation
Provide multiple compelling alternatives

Voice Preservation:

Learn your writing style from samples
Suggest options, not directives
Maintain consistent tone throughout

Five-Phase Workflow

Phase 1: Planning

Define:
- Topic and target audience
- Article length and goals
- Key messages

Output:
- Collaborative outline
- Research priorities identified

Phase 2: Research

Gather:
- Information on key topics
- Supporting evidence with citations
- Multiple perspectives

Output:
- Running reference list
- Refined outline based on findings

Phase 3: Drafting

Write:
- Introduction with improved hook
- Body sections incrementally
- Request feedback after each section

Output:
- Draft with inline citations
- Section-by-section notes

Phase 4: Refinement

Review:
- Comprehensive structure check
- Flow and transition analysis
- Citation verification

Output:
- Polished draft
- Final source list

Phase 5: Publishing

Finalize:
- Proofread mechanics
- Complete pre-publish checklist
- Prepare distribution

Output:
- Publication-ready content

Usage Examples

Start with outlining:

Help me outline a technical article about React Server Components
for intermediate developers. Goal: 2000 words, focus on practical
examples and common pitfalls.

Research phase:

Find current performance benchmarks for React Server Components
vs traditional CSR. Add citations from official React docs and
credible tech blogs.

Draft with feedback:

I finished the introduction. Strengthen the opening hook and check
if it clearly communicates the value proposition.

Final review:

Full draft complete. Check overall flow, consistency, and verify
all technical claims have proper citations.

Best Practices

For Research:

✅ Verify source credibility before citing
✅ Prioritize recent, authoritative data
✅ Include multiple perspectives
✅ Maintain transparent attribution

For Feedback:

✅ Be specific: "Does this feel too technical?"
✅ Highlight concerns: "This section needs more evidence"
✅ Ask comparisons: "What's an alternative explanation?"

For Voice Preservation:

✅ Share writing samples upfront
✅ Specify desired tone (formal, conversational, technical)
✅ Flag misalignments: "This reads too academic"

File Organization

Recommended structure:

~/writing/article-name/
├── outline.md          # Initial planning
├── research.md         # Sources and notes
├── draft-v1.md         # First draft
├── draft-v2.md         # Revised version
├── final.md            # Publication version
├── feedback.md         # Review notes
└── sources/            # Reference materials

Citation Formats

Inline Citations:

MARKDOWN

React Server Components reduce bundle size by 30% (Vercel Blog, 2024).

Numbered References:

MARKDOWN

Performance benchmarks show significant improvements [1].

References:
[1] "React Server Components", Vercel Engineering Blog, 2024

Footnote Style:

MARKDOWN

Early adoption shows promise¹.

¹ According to the official React RFC published March 2024

Content Types Supported

Technical Writing:

Blog posts and tutorials
Technical documentation
Architecture guides
API references

Thought Leadership:

Industry analysis
Case studies
Best practices
Trend reports

Educational Content:

Course materials
Tutorial series
How-to guides
Learning resources

Marketing Content:

Newsletters
Presentation content
White papers
Product documentation

Section-by-Section Feedback

Clarity Check:

Are technical concepts explained clearly?
Do transitions flow logically?
Is jargon appropriately introduced?

Evidence Quality:

Are claims backed by credible sources?
Do examples support main points?
Are citations properly formatted?

Style Consistency:

Does tone match target audience?
Is voice consistent throughout?
Are code examples following conventions?

Hook Enhancement Examples

Original: "This article is about React Server Components."

Enhanced: "React Server Components promise to revolutionize how we build web apps—but only if you avoid these three common pitfalls that derail most implementations."

Why it works:

Creates curiosity (what pitfalls?)
Promises value (avoid mistakes)
Shows specificity (three specific issues)

Common Use Cases

For Bloggers:

Research trending topics
Structure compelling narratives
Maintain consistent voice across posts
Build proper reference lists

For Technical Writers:

Organize complex concepts
Verify technical accuracy
Create clear code examples
Structure documentation hierarchies

For Researchers:

Manage extensive citations
Maintain academic rigor
Structure literature reviews
Synthesize multiple sources

For Content Marketers:

Develop thought leadership pieces
Support claims with data
Create engaging introductions
Maintain brand voice consistency

About This Skill

This skill was created by ComposioHQ as part of their collection of Claude Code productivity skills.

Philosophy: Writing is collaborative, not solitary. The best AI writing assistants enhance your voice rather than replacing it. They research, structure, and refine—but you remain the author.

Collaborative writing assistant providing research support, structural guidance, citation management, and iterative feedback while preserving your unique voice.