content-research-writer

97
3
Source

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

Install

mkdir -p .claude/skills/content-research-writer && curl -L -o skill.zip "https://mcp.directory/api/skills/download/10" && unzip -o skill.zip -d .claude/skills/content-research-writer && rm skill.zip

Installs to .claude/skills/content-research-writer

About this skill

Content Research Writer

This skill acts as your writing partner, helping you research, outline, draft, and refine content while maintaining your unique voice and style.

When to Use This Skill

  • Writing blog posts, articles, or newsletters
  • Creating educational content or tutorials
  • Drafting thought leadership pieces
  • Researching and writing case studies
  • Producing technical documentation with sources
  • Writing with proper citations and references
  • Improving hooks and introductions
  • Getting section-by-section feedback while writing

What This Skill Does

  1. Collaborative Outlining: Helps you structure ideas into coherent outlines
  2. Research Assistance: Finds relevant information and adds citations
  3. Hook Improvement: Strengthens your opening to capture attention
  4. Section Feedback: Reviews each section as you write
  5. Voice Preservation: Maintains your writing style and tone
  6. Citation Management: Adds and formats references properly
  7. Iterative Refinement: Helps you improve through multiple drafts

How to Use

Setup Your Writing Environment

Create a dedicated folder for your article:

mkdir ~/writing/my-article-title
cd ~/writing/my-article-title

Create your draft file:

touch article-draft.md

Open Claude Code from this directory and start writing.

Basic Workflow

  1. Start with an outline:
Help me create an outline for an article about [topic]
  1. Research and add citations:
Research [specific topic] and add citations to my outline
  1. Improve the hook:
Here's my introduction. Help me make the hook more compelling.
  1. Get section feedback:
I just finished the "Why This Matters" section. Review it and give feedback.
  1. Refine and polish:
Review the full draft for flow, clarity, and consistency.

Instructions

When a user requests writing assistance:

  1. Understand the Writing Project

    Ask clarifying questions:

    • What's the topic and main argument?
    • Who's the target audience?
    • What's the desired length/format?
    • What's your goal? (educate, persuade, entertain, explain)
    • Any existing research or sources to include?
    • What's your writing style? (formal, conversational, technical)
  2. Collaborative Outlining

    Help structure the content:

    # Article Outline: [Title]
    
    ## Hook
    - [Opening line/story/statistic]
    - [Why reader should care]
    
    ## Introduction
    - Context and background
    - Problem statement
    - What this article covers
    
    ## Main Sections
    
    ### Section 1: [Title]
    - Key point A
    - Key point B
    - Example/evidence
    - [Research needed: specific topic]
    
    ### Section 2: [Title]
    - Key point C
    - Key point D
    - Data/citation needed
    
    ### Section 3: [Title]
    - Key point E
    - Counter-arguments
    - Resolution
    
    ## Conclusion
    - Summary of main points
    - Call to action
    - Final thought
    
    ## Research To-Do
    - [ ] Find data on [topic]
    - [ ] Get examples of [concept]
    - [ ] Source citation for [claim]
    

    Iterate on outline:

    • Adjust based on feedback
    • Ensure logical flow
    • Identify research gaps
    • Mark sections for deep dives
  3. Conduct Research

    When user requests research on a topic:

    • Search for relevant information
    • Find credible sources
    • Extract key facts, quotes, and data
    • Add citations in requested format

    Example output:

    ## Research: AI Impact on Productivity
    
    Key Findings:
    
    1. **Productivity Gains**: Studies show 40% time savings for 
       content creation tasks [1]
    
    2. **Adoption Rates**: 67% of knowledge workers use AI tools 
       weekly [2]
    
    3. **Expert Quote**: "AI augments rather than replaces human 
       creativity" - Dr. Jane Smith, MIT [3]
    
    Citations:
    [1] McKinsey Global Institute. (2024). "The Economic Potential 
        of Generative AI"
    [2] Stack Overflow Developer Survey (2024)
    [3] Smith, J. (2024). MIT Technology Review interview
    
    Added to outline under Section 2.
    
  4. Improve Hooks

    When user shares an introduction, analyze and strengthen:

    Current Hook Analysis:

    • What works: [positive elements]
    • What could be stronger: [areas for improvement]
    • Emotional impact: [current vs. potential]

    Suggested Alternatives:

    Option 1: [Bold statement]

    [Example] Why it works: [explanation]

    Option 2: [Personal story]

    [Example] Why it works: [explanation]

    Option 3: [Surprising data]

    [Example] Why it works: [explanation]

    Questions to hook:

    • Does it create curiosity?
    • Does it promise value?
    • Is it specific enough?
    • Does it match the audience?
  5. Provide Section-by-Section Feedback

    As user writes each section, review for:

    # Feedback: [Section Name]
    
    ## What Works Well ✓
    - [Strength 1]
    - [Strength 2]
    - [Strength 3]
    
    ## Suggestions for Improvement
    
    ### Clarity
    - [Specific issue] → [Suggested fix]
    - [Complex sentence] → [Simpler alternative]
    
    ### Flow
    - [Transition issue] → [Better connection]
    - [Paragraph order] → [Suggested reordering]
    
    ### Evidence
    - [Claim needing support] → [Add citation or example]
    - [Generic statement] → [Make more specific]
    
    ### Style
    - [Tone inconsistency] → [Match your voice better]
    - [Word choice] → [Stronger alternative]
    
    ## Specific Line Edits
    
    Original:
    > [Exact quote from draft]
    
    Suggested:
    > [Improved version]
    
    Why: [Explanation]
    
    ## Questions to Consider
    - [Thought-provoking question 1]
    - [Thought-provoking question 2]
    
    Ready to move to next section!
    
  6. Preserve Writer's Voice

    Important principles:

    • Learn their style: Read existing writing samples
    • Suggest, don't replace: Offer options, not directives
    • Match tone: Formal, casual, technical, friendly
    • Respect choices: If they prefer their version, support it
    • Enhance, don't override: Make their writing better, not different

    Ask periodically:

    • "Does this sound like you?"
    • "Is this the right tone?"
    • "Should I be more/less [formal/casual/technical]?"
  7. Citation Management

    Handle references based on user preference:

    Inline Citations:

    Studies show 40% productivity improvement (McKinsey, 2024).
    

    Numbered References:

    Studies show 40% productivity improvement [1].
    
    [1] McKinsey Global Institute. (2024)...
    

    Footnote Style:

    Studies show 40% productivity improvement^1
    
    ^1: McKinsey Global Institute. (2024)...
    

    Maintain a running citations list:

    ## References
    
    1. Author. (Year). "Title". Publication.
    2. Author. (Year). "Title". Publication.
    ...
    
  8. Final Review and Polish

    When draft is complete, provide comprehensive feedback:

    # Full Draft Review
    
    ## Overall Assessment
    
    **Strengths**:
    - [Major strength 1]
    - [Major strength 2]
    - [Major strength 3]
    
    **Impact**: [Overall effectiveness assessment]
    
    ## Structure & Flow
    - [Comments on organization]
    - [Transition quality]
    - [Pacing assessment]
    
    ## Content Quality
    - [Argument strength]
    - [Evidence sufficiency]
    - [Example effectiveness]
    
    ## Technical Quality
    - Grammar and mechanics: [assessment]
    - Consistency: [assessment]
    - Citations: [completeness check]
    
    ## Readability
    - Clarity score: [evaluation]
    - Sentence variety: [evaluation]
    - Paragraph length: [evaluation]
    
    ## Final Polish Suggestions
    
    1. **Introduction**: [Specific improvements]
    2. **Body**: [Specific improvements]
    3. **Conclusion**: [Specific improvements]
    4. **Title**: [Options if needed]
    
    ## Pre-Publish Checklist
    - [ ] All claims sourced
    - [ ] Citations formatted
    - [ ] Examples clear
    - [ ] Transitions smooth
    - [ ] Call to action present
    - [ ] Proofread for typos
    
    Ready to publish! 🚀
    

Examples

Example 1: Teresa Torres's Workflow

User: "I'm writing an article about continuous discovery. Help me create an outline."

Process:

  1. Collaborates on outline structure
  2. Identifies research needs
  3. User starts writing introduction
  4. Reviews and improves the hook
  5. User writes each section
  6. Provides feedback after each section
  7. Conducts research and adds citations
  8. Final review of complete draft
  9. Polish and prep for publishing

Result: Well-researched, properly cited article written in Teresa's voice with strong structure and flow.

Example 2: Research-Heavy Article

User: "I'm writing about AI's impact on product management. Help me find current data and examples."

Output:

## Research Compiled

### Recent Data
- Gartner: 80% of PMs will use AI tools by 2025 [1]
- Survey: 45% report faster feature shipping [2]
- Case study: Airbnb's AI-assisted prioritization [3]

### Expert Quotes
- "AI amplifies PM judgment, not replaces it" - Marty Cagan
- [Additional quotes with citations]

### Real Examples
1. **Company A**: Used AI for user research synthesis
   - Result: 60% time savings
   - Source: [citation]

2. **Company B**: AI-powered roadmap analysis
   - Result: Better stakeholder alignment
   - Source: [citation]

All added to your outline with proper citations.

Example 3: Hook Improvement

User's Original Hook:

"Product management is changing because of AI. In this article, I'll discuss some ways AI affects product managers."

Improved Options:

Option 1 (Data-driven):

"Last month, I asked AI to analyze 500 customer interviews. It took 30 minutes instead of 3 weeks. Pro


Content truncated.

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

8081,046

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

729779

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

466582

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

419442

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

556412

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

377250

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.