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
- Research Assistance: Finds relevant information and adds citations
- Hook Improvement: Strengthens your opening 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 you improve through multiple drafts
How to Use
Setup Your Writing Environment
Create a dedicated folder for your article:
CODEBLOCK0
Create your draft file:
CODEBLOCK1
Open Claude Code from this directory and start writing.
Basic Workflow
- 1. Start with an outline:
CODEBLOCK2
- 2. Research and add citations:
CODEBLOCK3
- 3. Improve the hook:
CODEBLOCK4
- 4. Get section feedback:
CODEBLOCK5
- 5. Refine and polish:
CODEBLOCK6
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:
CODEBLOCK7
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:
CODEBLOCK8
- 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:
CODEBLOCK9
- 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:
CODEBLOCK10
Numbered References:
CODEBLOCK11
Footnote Style:
CODEBLOCK12
Maintain a running citations list:
CODEBLOCK13
- 8. Final Review and Polish
When draft is complete, provide comprehensive feedback:
CODEBLOCK14
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
- Identifies research needs
- User starts writing introduction
- Reviews and improves the hook
- User writes each section
- Provides feedback after each section
- Conducts research and adds citations
- Final review of complete draft
- 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:
CODEBLOCK15
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. Product management will never be the same."
Option 2 (Question):
"What if you could talk to every customer, read every review, and analyze every support ticket—all before your morning coffee?"
Option 3 (Story):
"Sarah spent two weeks building the wrong feature. Not because she didn't understand her users, but because she couldn't process the hundreds of interviews fast enough to spot the pattern."
Example 4: Section Feedback
User: "Just finished my 'Common Mistakes' section. Thoughts?"
Response:
CODEBLOCK16
Writing Workflows
Blog Post Workflow
- 1. Outline together
- Research key points
- Write introduction → get feedback
- Write body sections → feedback each
- Write conclusion → final review
- Polish and edit
Newsletter Workflow
- 1. Discuss hook ideas
- Quick outline (shorter format)
- Draft in one session
- Review for clarity and links
- Quick polish
Technical Tutorial Workflow
- 1. Outline steps
- Write code examples
- Add explanations
- Test instructions
- Add troubleshooting section
- Final review for accuracy
Thought Leadership Workflow
- 1. Brainstorm unique angle
- Research existing perspectives
- Develop your thesis
- Write with strong POV
- Add supporting evidence
- Craft compelling conclusion
Pro Tips
- 1. Work in VS Code: Better than web Claude for long-form writing
- One section at a time: Get feedback incrementally
- Save research separately: Keep a research.md file
- Version your drafts: article-v1.md, article-v2.md, etc.
- Read aloud: Use feedback to identify clunky sentences
- Set deadlines: "I want to finish the draft today"
- Take breaks: Write, get feedback, pause, revise
File Organization
Recommended structure for writing projects:
CODEBLOCK17
Best Practices
For Research
- - Verify sources before citing
- Use recent data when possible
- Balance different perspectives
- Link to original sources
For Feedback
- - Be specific about what you want: "Is this too technical?"
- Share your concerns: "I'm worried this section drags"
- Ask questions: "Does this flow logically?"
- Request alternatives: "What's another way to explain this?"
For Voice
- - Share examples of your writing
- Specify tone preferences
- Point out good matches: "That sounds like me!"
- Flag mismatches: "Too formal for my style"
Related Use Cases
- - Creating social media posts from articles
- Adapting content for different audiences
- Writing email newsletters
- Drafting technical documentation
- Creating presentation content
- Writing case studies
- Developing course outlines
内容研究写作
该技能作为您的写作伙伴,协助您研究、规划大纲、起草和优化内容,同时保持您独特的个人风格。
何时使用该技能
- - 撰写博客文章、专题文章或新闻通讯
- 创建教育内容或教程
- 起草思想领导力文章
- 研究和撰写案例研究
- 制作带来源的技术文档
- 使用恰当的引用和参考文献进行写作
- 优化开篇和引言
- 在写作过程中获取逐节反馈
该技能的功能
- 1. 协作式大纲规划:帮助您将想法组织成连贯的大纲
- 研究辅助:查找相关信息并添加引用
- 开篇优化:强化您的开头以吸引注意力
- 章节反馈:在您写作时审阅每个章节
- 风格保持:维护您的写作风格和语气
- 引用管理:正确添加和格式化参考文献
- 迭代优化:通过多轮草稿帮助您改进
使用方法
设置写作环境
为您的文章创建一个专用文件夹:
mkdir ~/writing/my-article-title
cd ~/writing/my-article-title
创建草稿文件:
touch article-draft.md
从该目录打开Claude Code并开始写作。
基本工作流程
- 1. 从大纲开始:
帮我为关于[主题]的文章创建大纲
- 2. 研究并添加引用:
研究[具体主题]并为我的大纲添加引用
- 3. 优化开篇:
这是我的引言。请帮我让开篇更具吸引力。
- 4. 获取章节反馈:
我刚完成了为什么这很重要部分。请审阅并给出反馈。
- 5. 优化和润色:
审阅完整草稿的流畅性、清晰度和一致性。
操作说明
当用户请求写作协助时:
- 1. 了解写作项目
提出澄清性问题:
- 主题和主要论点是什么?
- 目标受众是谁?
- 期望的长度/格式是什么?
- 您的目标是什么?(教育、说服、娱乐、解释)
- 是否有需要包含的现有研究或来源?
- 您的写作风格是什么?(正式、对话式、技术性)
- 2. 协作式大纲规划
帮助组织内容:
markdown
# 文章大纲:[标题]
## 开篇
- [开场白/故事/统计数据]
- [读者为何应该关注]
## 引言
- 背景和上下文
- 问题陈述
- 本文涵盖内容
## 主要章节
### 第1节:[标题]
- 关键点A
- 关键点B
- 示例/证据
- [需要研究:具体主题]
### 第2节:[标题]
- 关键点C
- 关键点D
- 需要的数据/引用
### 第3节:[标题]
- 关键点E
- 反驳论点
- 解决方案
## 结论
- 主要观点总结
- 行动号召
- 最终思考
## 研究待办事项
- [ ] 查找关于[主题]的数据
- [ ] 获取[概念]的示例
- [ ] 为[主张]查找引用来源
迭代大纲:
- 根据反馈进行调整
- 确保逻辑流畅
- 识别研究空白
- 标记需要深入探讨的章节
- 3. 进行研究
当用户请求研究某个主题时:
- 搜索相关信息
- 查找可信来源
- 提取关键事实、引文和数据
- 按要求的格式添加引用
输出示例:
markdown
## 研究:AI对生产力的影响
关键发现:
1. 生产力提升:研究表明内容创作任务可节省40%的时间[1]
2. 采用率:67%的知识工作者每周使用AI工具[2]
3. 专家引文:AI增强而非取代人类创造力——Jane Smith博士,MIT[3]
引用:
[1] McKinsey全球研究所。(2024)。生成式AI的经济潜力
[2] Stack Overflow开发者调查(2024)
[3] Smith, J. (2024)。MIT技术评论访谈
已添加到第2节大纲下。
- 4. 优化开篇
当用户分享引言时,分析并强化:
当前开篇分析:
- 优点:[积极元素]
- 可加强之处:[改进空间]
- 情感影响:[当前 vs. 潜力]
建议替代方案:
方案1:[大胆陈述]
> [示例]
为何有效:[解释]
方案2:[个人故事]
> [示例]
为何有效:[解释]
方案3:[令人惊讶的数据]
> [示例]
为何有效:[解释]
开篇检查问题:
- 是否引发好奇心?
- 是否承诺价值?
- 是否足够具体?
- 是否匹配受众?
- 5. 提供逐节反馈
当用户写完每个章节时,审阅以下内容:
markdown
# 反馈:[章节名称]
## 优点 ✓
- [优点1]
- [优点2]
- [优点3]
## 改进建议
### 清晰度
- [具体问题] → [建议修改]
- [复杂句子] → [更简单的替代]
### 流畅性
- [过渡问题] → [更好的连接]
- [段落顺序] → [建议重新排序]
### 证据
- [需要支持的主张] → [添加引用或示例]
- [泛泛陈述] → [使其更具体]
### 风格
- [语气不一致] → [更好地匹配您的风格]
- [用词选择] → [更强的替代]
## 具体行级修改
原文:
> [草稿中的确切引用]
建议:
> [改进版本]
原因:[解释]
## 需要考虑的问题
- [发人深省的问题1]
- [发人深省的问题2]
可以进入下一节了!
- 6. 保持作者风格
重要原则:
- 学习他们的风格:阅读现有的写作样本
- 建议而非替代:提供选项,而非指令
- 匹配语气:正式、随意、技术性、友好
- 尊重选择:如果他们更喜欢自己的版本,支持它
- 增强而非覆盖:让他们的写作变得更好,而非不同
定期询问:
- 这听起来像你吗?
- 语气合适吗?
- 我应该更/不那么[正式/随意/技术性]吗?
- 7. 引用管理
根据用户偏好处理参考文献:
行内引用:
markdown
研究表明生产力提升40%(McKinsey,2024)。
编号参考文献:
markdown
研究表明生产力提升40%[1]。
[1] McKinsey全球研究所。(2024)...
脚注风格:
markdown
研究表明生产力提升40%^1
^1: McKinsey全球研究所。(2024)...
维护一个持续更新的引用列表:
markdown
## 参考文献
1. 作者。(年份)。标题。出版物。
2. 作者。(年份)。标题。出版物。
...
- 8. 最终审阅和润色
当草稿完成时,提供全面反馈:
markdown
# 完整草稿审阅
## 总体评估
优点:
- [主要优点1]
- [主要优点2]
- [主要优点3]
影响力:[整体效果评估]
## 结构与流畅性
- [组织结构评论]
- [过渡质量]
- [节奏评估]
## 内容质量
- [论证力度]
- [证据充分性]
- [示例有效性]
## 技术质量
- 语法和机制:[评估]
- 一致性:[评估]
- 引用:[完整性检查]
## 可读性
- 清晰度评分:[评估]
- 句子多样性:[评估]
- 段落长度:[评估]
## 最终润色建议
1. 引言:[具体改进]
2. 正文:[具体改进]
3. 结论:[具体改进]
4. 标题:[如需则提供选项]
## 发布前检查清单
- [ ] 所有主张都有来源
- [ ]