content-research-writer
Skill8 starsChanged 3 months agoApache-2.0View on GitHub
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing section-by-section feedback. This skill should be used when Cline needs to help write blog posts, articles, newsletters, case studies, technical documentation, or any long-form content that benefits from research-backed insights and collaborative editing.
We split this skill into the rules it gives an agent
12 rules. 4 are common, 8 are distinctive, and 0 are very specific to this project.
4
Common
Most of the 67 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 90
When research is requested:
- Distinctive: line 91
Search for relevant information using available tools
- Common: line 94
Add citations in the requested format
- Common: line 112
When a user shares an introduction, analyze and strengthen:
- Common: line 168
Learn their style: Read existing writing samples
- Common: line 171
Respect choices: If they prefer their version, support it
- Distinctive: line 188
When the draft is complete:
- Distinctive: line 224
Voice preservation is critical: Never rewrite in your own style — enhance the writer's voice, don't replace it
- Distinctive: line 225
Research with web tools: Use Cline's browser and web fetch capabilities for research
- Distinctive: line 226
Iterative by default: Always offer feedback and alternatives rather than single rewrites
- Distinctive: line 227
Save work frequently: Keep drafts in numbered versions to prevent data loss
- Distinctive: line 228
Citation format flexibility: Ask which citation style the user prefers before adding references
“Common” is measured: kept by at least 6 in 10 of the 67 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Research Writer
This skill acts as a collaborative writing partner — helping research, outline, draft, and refine content while preserving 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
- Repurposing content across formats
What This Skill Does
- Collaborative Outlining: Helps structure ideas into coherent outlines
- Research Assistance: Finds relevant information and adds citations
- Hook Improvement: Strengthens openings to capture attention
- Section Feedback: Reviews each section as you write
- Voice Preservation: Maintains your writing style and tone
- Citation Management: Adds and formats references properly
- Iterative Refinement: Helps improve through multiple drafts
Process
Step 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)
Step 2: Create a Collaborative Outline
Develop structure together:
# 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
## Research To-Do
- [ ] Find data on [topic]
- [ ] Get examples of [concept]
- [ ] Source citation for [claim]Iterate on the outline: Adjust based on feedback, ensure logical flow, identify research gaps, and mark sections needing deep dives.
Step 3: Conduct Research
When research is requested:
- Search for relevant information using available tools
- Find credible sources and recent data
- Extract key facts, quotes, and statistics
- Add citations in the requested format
- Note contradictions or gaps in available information
Example research output:
## Research: [Topic]
Key Findings:
1. **[Finding 1]**: [Details] [Source citation]
2. **[Finding 2]**: [Details] [Source citation]
3. **Expert Quote**: "[Quote]" — [Name], [Title/Org] [Source citation]
Added to outline under Section [X].Step 4: Improve Hooks
When a user shares an introduction, analyze and strengthen:
Current Hook Analysis:
- What works: [positive elements]
- What could be stronger: [areas for improvement]
Suggested Alternatives:
| Approach | Example | Why It Works |
| Bold statement | "[Opening line]" | [Explanation] |
| Personal story | "[Opening line]" | [Explanation] |
| Surprising data | "[Opening line]" | [Explanation] |
| Provocative question | "[Opening line]" | [Explanation] |
Hook Questions:
- Does it create curiosity?
- Does it promise value?
- Is it specific enough?
- Does it match the audience?
Step 5: Provide Section-by-Section Feedback
For each section, review:
# Feedback: [Section Name]
## What Works Well ✓
- [Strength 1]
- [Strength 2]
## Suggestions
### Clarity
- [Issue] → [Suggested fix]
### Flow
- [Transition issue] → [Better connection]
### Evidence
- [Claim needing support] → [Add citation or example]
## Specific Line Edits
Original:
> [Quote from draft]
Suggested:
> [Improved version]
Why: [Explanation]Step 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
Step 7: Citation Management
Handle references based on user preference:
Inline: Studies show 40% improvement (McKinsey, 2024).
Numbered: Studies show 40% improvement [1]. → [1] McKinsey Global Institute. (2024). "Title."
Footnote: Studies show 40% improvement^1 → ^1: Full citation.
Maintain a running references list throughout the writing process.
Step 8: Final Review
When the draft is complete:
- Overall assessment of strengths and areas for refinement
- Structure and flow evaluation
- Content quality check (argument strength, evidence sufficiency)
- Technical quality review (grammar, consistency, citations)
- Pre-publish checklist: all claims sourced, citations formatted, transitions smooth
Writing Workflows
Blog Post
- Outline together → 2. Research key points → 3. Write intro → feedback → 4. Write body sections → feedback each → 5. Write conclusion → 6. Polish
Newsletter
- Discuss hook ideas → 2. Quick outline → 3. Draft in one session → 4. Review for clarity → 5. Quick polish
Technical Tutorial
- Outline steps → 2. Write code examples → 3. Add explanations → 4. Test instructions → 5. Add troubleshooting → 6. Final review for accuracy
Thought Leadership
- Brainstorm unique angle → 2. Research existing perspectives → 3. Develop thesis → 4. Write with strong POV → 5. Add evidence → 6. Craft conclusion
File Organization
writing/
└── article-name/
├── outline.md # Outline and structure
├── research.md # Research and citations
├── draft-v1.md # First draft
├── draft-v2.md # Revised draft
└── final.md # Publication-readyCline Workflow Notes
- Install location: Copy this skill directory to
.cline/skills/content-research-writer/(project-level) or~/.cline/skills/content-research-writer/(global) - Voice preservation is critical: Never rewrite in your own style — enhance the writer's voice, don't replace it
- Research with web tools: Use Cline's browser and web fetch capabilities for research
- Iterative by default: Always offer feedback and alternatives rather than single rewrites
- Save work frequently: Keep drafts in numbered versions to prevent data loss
- Citation format flexibility: Ask which citation style the user prefers before adding references
- One section at a time: Get feedback incrementally rather than reviewing entire drafts at once
Related Use Cases
- Creating social media posts from long-form articles
- Adapting content for different audiences and platforms
- Writing email newsletters from existing content
- Drafting technical documentation with examples
- Developing course outlines and educational materials
Other versions71 projects use a version of this.
Word for word · 0
None found.
Edited · 57
- ComposioHQ/awesome-claude-skills★ 75k24% same
- ComposioHQ/awesome-codex-skills★ 17k24% same
- composio-community/awesome-codex-skills★ 16k24% same
- anbeime/skill★ 7.9k23% same
- Prat011/awesome-llm-skills★ 1.7k24% same
- MoizIbnYousaf/Ai-Agent-Skills★ 1.1k24% same
- skillcreatorai/Ai-Agent-Skills★ 1.1k24% same
- MoizIbnYousaf/ai-agent-skills★ 1.1k24% same
- pedronauck/skills★ 64124% same
- maslennikov-ig/claude-code-orchestrator-kit★ 24824% same
47 more not listed
Wrote their own version · 14
- google/adk-recipes★ 11ksame name
- google/adk-samples★ 11ksame name
- Rylaispirit/rylai-codex-hermes-skills★ 56same name
- vignesh2027/Claude-Agentic-Skills2.0-version★ 6same name
- AthArvA-188/top-10-claude-skills★ 3same name
- gonzaloraknarok88/CLAUDE-HABILIDADES★ 3same name
- jasonmichaelbell78-creator/sonash-v0★ 2same name
- skytiger6724/qwen-skills★ 2same name
- sohaibdevv/Claude-Agentic-Skills2.0-version★ 2same name
- BenPrem/business-brain★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use skill-share, raffle-winner-picker and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ArogyaReddySkillskill-share
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Also in 22 projects that use this
ArogyaReddySkillraffle-winner-picker
Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
Also in 25 projects that use this
pepebot-spaceSkillllm-application-dev
Building applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration. Use for AI-powered features, chatbots, or LLM-based automation.
Also in 4 projects that use this
- +3 more from ArogyaReddy
In this repository49 other files it gives its agents.
- a-b-testingSkill
- api-devSkill
- article-extractorSkill
- audio-genSkill
- blog-writerSkill
- brainstormingSkill
- brand-guidelinesSkill
- canvas-designSkill
- changelog-generatorSkill
- code-refactorerSkill
- competitive-ads-extractorSkill
- database-managerSkill
- docker-deploySkill
- docxSkill
- domain-name-brainstormerSkill
- email-campaignsSkill
- finishing-a-development-branchSkill
- game-devSkill
- git-pushingSkill
- git-workflowSkill
- godot-helperSkill
- image-enhancerSkill
- ios-simulator-skillSkill
- langsmith-fetchSkill
- lead-research-assistantSkill
- lean-ctxSkill
- mcp-builderSkill
- meeting-insights-analyzerSkill
- pdfSkill
- playwright-skillSkill
- pptxSkill
- react-nextjs-builderSkill
- review-implementingSkill
- seo-optimizerSkill
- ship-learn-nextSkill
- skill-creatorSkill
- skill-builderSkill
- social-media-managerSkill
- staff-engineer-reviewSkill
- tailored-resume-generatorSkill
- test-driven-developmentSkill
- test-fixingSkill
- twitter-algorithm-optimizerSkill
- using-git-worktreesSkill
- video-framesSkill
- webapp-testingSkill
- xlsxSkill
- youtube-transcriptSkill
- your-skill-nameSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

