content-research-writer

davila7/claude-code-templates · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/davila7/claude-code-templates --skill content-research-writer
0 commentsdiscussion
summary

Research-backed writing partner that outlines, researches, improves hooks, and refines content section by section.

  • Guides collaborative outlining, research compilation with citations, and iterative feedback on each section as you write
  • Preserves your unique voice and writing style while strengthening clarity, flow, and evidence
  • Handles citation management in multiple formats (inline, numbered, footnote) and maintains running reference lists
  • Supports diverse workflows: blog posts,
skill.md

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. 
how to use content-research-writer

How to use content-research-writer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add content-research-writer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/davila7/claude-code-templates --skill content-research-writer

The skills CLI fetches content-research-writer from GitHub repository davila7/claude-code-templates and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/content-research-writer

Reload or restart Cursor to activate content-research-writer. Access the skill through slash commands (e.g., /content-research-writer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.571 reviews
  • Sakura Sethi· Dec 24, 2024

    content-research-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Carlos White· Dec 20, 2024

    I recommend content-research-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Nia Yang· Dec 20, 2024

    Useful defaults in content-research-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mateo Khanna· Dec 16, 2024

    Solid pick for teams standardizing on skills: content-research-writer is focused, and the summary matches what you get after install.

  • Sophia Flores· Dec 12, 2024

    I recommend content-research-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sophia Sanchez· Dec 4, 2024

    We added content-research-writer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 23, 2024

    Registry listing for content-research-writer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Advait Brown· Nov 23, 2024

    Solid pick for teams standardizing on skills: content-research-writer is focused, and the summary matches what you get after install.

  • Harper Rahman· Nov 11, 2024

    Keeps context tight: content-research-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Carlos Thomas· Nov 11, 2024

    content-research-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 71

1 / 8