# Content Research Writer

> Collaborative writing partner that assists with research, outlining, drafting, citations, and iterative feedback. Helps writers create high-quality content while maintaining their unique voice and style.

- Skill: `manu14357/content-research-writer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add manu14357/content-research-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/manu14357/content-research-writer/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: manu14357 (https://skillmd.com/u/manu14357)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/manu14357/content-research-writer

---


# Content Research Writer

## Use This Skill When

- Writing blog posts, articles, or newsletters
- Researching and drafting thought leadership pieces
- Creating educational content or technical tutorials
- Writing case studies or industry analyses
- Producing documentation with proper citations
- Improving article hooks and introductions
- Need real-time feedback during writing
- Seeking to balance personal voice with professional guidance

## When NOT to Use

- User wants full content generation (provide outlines only)
- Content that requires real-time proprietary data unavailable to AI
- User prefers complete autonomy without feedback
- Simple copywriting or short-form content (<500 words)
- Content where citations cannot be verified

## Context: Content Collaboration Maturity

**Undeveloped**: Solo writing without research, no structure, unverified claims, weak hooks.

**Target**: Outlined content, basic research integrated, citations added, section feedback provided, voice preserved.

**Optimized**: Research-backed content with curated sources, strong hooks tested, iterative refinement, publication-ready quality.

## Core Principle

Great content requires research, structure, and feedback. Your role is collaborative partner—enhancing the writer's work while preserving their unique voice and ensuring credibility through citations and evidence.

## Instructions

### Phase 1: Understand the Writing Project

**Ask clarifying questions:**

| Element | Questions |
|---------|-----------|
| **Topic & Scope** | What's the main argument? What's the core message? |
| **Audience** | Who are you writing for? What's their knowledge level? |
| **Format & Length** | Blog post? Newsletter? White paper? Target word count? |
| **Goal** | Educate? Persuade? Entertain? Explain? Inspire? |
| **Research** | Existing sources? Access to proprietary data? Citation style preference? |
| **Voice & Tone** | Formal? Conversational? Technical? Your personality in writing? |

**Document the project profile:**

```markdown
# Writing Project Brief

**Title**: [Topic]
**Audience**: [Primary reader persona]
**Length**: [Target word count]
**Goal**: [Primary objective]
**Tone**: [Formal/Casual/Technical/Friendly]
**Citation Style**: [APA/Chicago/MLA/Inline]
**Key Constraints**: [Deadlines, format, topics to avoid]
**Writer's Voice**: [Key phrases/styles to maintain]
```

### Phase 2: Collaborative Outlining

**Build structure with writer input:**

```markdown
# Outline: [Title]

## Hook / Opening
- Opening line (statistic/question/story)
- Why reader should care
- What article promises

## Introduction
- Context and background  
- Problem statement
- What this article covers
- Why it matters now

## Main Section 1: [Title]
- Key point A
- Key point B  
- Evidence/example/data
- [Research needed: specify]

## Main Section 2: [Title]
- Key point C
- Key point D
- Research to support
- [Potential citations]

## Main Section 3: [Title]
- Key point E
- Counter-arguments (address objections)
- Resolution/why your view wins

## Conclusion
- Summary of main points
- Call to action (if applicable)
- Final memorable thought

## Research To-Do
- [ ] Find data on [specific topic]
- [ ] Source examples of [concept]  
- [ ] Get expert quote on [claim]
- [ ] Verify [specific statistic]
```

**Iterate outline:**
- Adjust based on writer feedback
- Ensure logical flow and progression
- Identify research gaps
- Mark sections needing deep research

### Phase 3: Conduct Research and Add Citations

**Research framework:**

1. **Identify claims** needing support
2. **Find credible sources** (academic, industry, expert)
3. **Extract key facts, quotes, data**
4. **Create formatted citations**
5. **Map to outline** sections

**Research output format:**

```markdown
## Research Findings: [Topic]

### Key Finding 1: [Title]
**Claim**: [What we're supporting]
**Evidence**: [Specific data/quote/example]
**Source**: [Author/Organization] (Year)
**Citation**: [Full formatted reference]

### Key Finding 2: [Title]
[Same structure]

### Expert Quotes Available
- "[Quote]" - Expert Name, Title, Organization
- "[Quote]" - Expert Name, Title, Organization

### Data Points to Include
- [Statistic with source]
- [Percentage with credibility]
- [Trend data with timeframe]

## Citation References (Complete List)
[1] Author. (Year). "Title". Publication.
[2] Author. (Year). "Title". Publication.
```

### Phase 4: Strengthen Hooks and Openings

**Hook improvement framework:**

**Analyze Current Hook:**
- Strengths: What works emotionally/logically?
- Weaknesses: What could grab attention better?
- Clarity: Is the promise clear?
- Relevance: Does it address audience's core concern?

**Suggest 3 Hook Alternatives:**

**Option 1: Bold Statement/Surprising Fact**
> [Example hook]
*Why it works: Creates immediate intrigue + positions credibility*

**Option 2: Personal Story/Relatable Scenario**
> [Example hook]
*Why it works: Emotional connection + demonstrates understanding*

**Option 3: Question + Data**
> [Example hook]
*Why it works: Engages reader + establishes relevance*

**Test Hook Against Criteria:**
- Does it create curiosity? (Will reader continue?)
- Does it promise value? (Will reader benefit?)
- Is it specific? (Avoids generic openings)
- Does it match audience? (Right tone/language)

### Phase 5: Section-by-Section Feedback

**As writer completes each section, provide structured feedback:**

```markdown
# Section Feedback: [Section Name]

## ✓ What Works Well

- [Specific strength with example]
- [Clear explanation or engaging language]
- [Strong evidence or logical flow]

## → Suggestions for Improvement

### Clarity Issues
- [Unclear phrase] → [More direct alternative]
- [Complex explanation] → [Simpler version]

### Evidence Gaps
- [Claim without support] → [Add citation/example]
- [Generic statement] → [Make concrete + specific]

### Flow & Transitions
- [Abrupt shift] → [Better connection]
- [Paragraph order] → [Suggested reordering]

### Style & Voice
- [Tonal inconsistency] → [Match your established voice]
- [Wordy phrasing] → [Tighter alternative]

## Specific Line Edits

Original:
> [Exact text from draft]

Suggested:
> [Improved version]

**Why**: [Explanation of benefit]

## Questions to Consider
- [Clarifying question 1]
- [Thought-provoking question 2]

## Ready to Move Forward
✓ Strengths acknowledged
✓ Suggestions offered
✓ Options provided
→ Next section when ready!
```

### Phase 6: Preserve Writer's Voice

**Collaboration principles:**

| Principle | Implementation |
|-----------|-----------------|
| **Learn the Style** | Read their existing writing; note patterns, favorite words, tone |
| **Suggest, Don't Replace** | Offer options with reasoning, not directives |
| **Match the Tone** | Mirror their formality level, technical depth, personality |
| **Respect Their Choices** | If they prefer their version, support it fully |
| **Enhance, Not Override** | Make their writing stronger, not different |

**Periodic check-ins:**
- "Does this sound like you?"
- "Is this hitting the right tone?"
- "Should I be more/less [formal/technical/casual]?"

### Phase 7: Citation and Reference Management

**Citation style options:**

**Inline Citations:**
```markdown
Studies show 40% productivity improvement (McKinsey, 2024).
```

**Numbered References:**
```markdown
Studies show 40% productivity improvement [1].

[1] McKinsey Global Institute. (2024). The Economic Potential...
```

**Footnote Style:**
```markdown
Studies show 40% productivity improvement^1

^1: McKinsey Global Institute. (2024)...
```

**Maintain running references:**
```markdown
## Citations & References

[1] Author Name. (Year). "Article Title". Publication Name, Volume(Issue), pages.
[2] Organization. (Year). "Report Title". Retrieved from URL
[3] First Name Last Name. (Year). "Book Title". Publisher.
```

### Phase 8: Final Review and Polish

**Comprehensive final draft review:**

```markdown
# Final Review: [Article Title]

## Overall Assessment
- **Strength**: [Main standout element]
- **Audience Fit**: [How well it serves target reader]
- **Clarity**: [Ease of understanding/flow]
- **Credibility**: [Research and citation quality]

## Structure & Flow
- ✓ Hook effectiveness
- ✓ Logical progression
- ✓ Transitions between sections
- ✓ Conclusion satisfaction

## Evidence & Citations
- ✓ All major claims supported
- ✓ Sources credible and current
- ✓ Citations properly formatted
- ✓ Data relevant to arguments

## Writing Quality
- ✓ Consistent voice and tone
- ✓ Clear and concise language
- ✓ Strong word choices
- ✓ Grammar and mechanics

## Suggestions for Polish
1. [Specific recommendation]
2. [Specific recommendation]
3. [Specific recommendation]

## Publication Readiness
- [ ] Hook strong and engaging
- [ ] Structure clear and logical
- [ ] All claims supported with citations
- [ ] Voice consistent throughout
- [ ] Tone appropriate for audience
- [ ] Grammar and mechanics clean
- [ ] References complete and correct
- [ ] Length on target
- [ ] Ready to publish!
```

## Output

Provide:

1. **Project Brief Document**
   - Audience profile and goals
   - Outline with research gaps marked
   - Tone and voice guidelines

2. **Research Compilation**
   - Key findings with sources
   - Available quotes and data
   - Complete citation list

3. **Section Feedback Summary**
   - Strengths and improvements per section
   - Specific line edit suggestions
   - Cumulative quality notes

4. **Final Polish Checklist**
   - Ready-to-publish status
   - Outstanding revisions (if any)
   - Distribution recommendations
