content-research-writer by composiohq/awesome-claude-skills
npx skills add https://github.com/composiohq/awesome-claude-skills --skill content-research-writer此技能可作为您的写作伙伴,帮助您研究、规划大纲、起草和润色内容,同时保持您独特的文风和风格。
为您的文章创建一个专用文件夹:
mkdir ~/writing/my-article-title
cd ~/writing/my-article-title
创建您的草稿文件:
touch article-draft.md
从此目录打开 Claude Code 并开始写作。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
从大纲开始:
Help me create an outline for an article about [topic]
研究并添加引用:
Research [specific topic] and add citations to my outline
优化开头:
Here's my introduction. Help me make the hook more compelling.
获取章节反馈:
I just finished the "Why This Matters" section. Review it and give feedback.
润色和完善:
Review the full draft for flow, clarity, and consistency.
当用户请求写作协助时:
了解写作项目
询问澄清性问题:
协作大纲规划
帮助构建内容结构:
# 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]
迭代大纲:
进行研究
当用户请求研究某个主题时:
示例输出:
## 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.
优化开头
当用户分享引言时,分析并强化:
当前开头分析:
建议的替代方案:
选项 1:[大胆的陈述]
[示例] 为何有效:[解释]
选项 2:[个人故事]
[示例] 为何有效:[解释]
选项 3:[令人惊讶的数据]
[示例] 为何有效:[解释]
评估开头的问题:
提供逐节反馈
当用户撰写每个章节时,审阅以下方面:
# 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!
保持作者风格
重要原则:
定期询问:
引用管理
根据用户偏好处理参考文献:
文内引用:
Studies show 40% productivity improvement (McKinsey, 2024).
编号参考文献:
Studies show 40% productivity improvement [1].
[1] McKinsey Global Institute. (2024)...
脚注风格:
Studies show 40% productivity improvement^1
^1: McKinsey Global Institute. (2024)...
维护一个持续的引用列表:
## References
1. Author. (Year). "Title". Publication.
2. Author. (Year). "Title". Publication.
...
最终审阅与润色
当草稿完成时,提供全面的反馈:
# 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! 🚀
用户:"我正在写一篇关于持续发现的文章。帮我创建一个大纲。"
流程:
结果:一篇研究充分、引用得当的文章,以 Teresa 的风格撰写,结构清晰,行文流畅。
用户:"我正在写关于 AI 对产品管理影响的文章。帮我找找当前的数据和例子。"
输出:
## 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.
用户原始开头:
"Product management is changing because of AI. In this article, I'll discuss some ways AI affects product managers."
改进选项:
选项 1(数据驱动):
"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."
选项 2(提问式):
"What if you could talk to every customer, read every review, and analyze every support ticket—all before your morning coffee?"
选项 3(故事式):
"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."
用户:"刚写完我的'常见错误'部分。有什么想法?"
回复:
# Feedback: Common Mistakes Section
## What Works Well ✓
- Strong examples (the Slack notification story)
- Clear structure (3 mistakes, clean layout)
- Practical advice for each mistake
## Suggestions
### Make It More Specific
Your second point says "Bad prioritization" but could be stronger:
Current:
> "Many teams prioritize badly by focusing on features instead of outcomes."
Suggested:
> "I've watched teams ship 14 features in a quarter yet move none of their key metrics. They prioritized activity over progress."
### Add Data
The third mistake would benefit from evidence:
> "[Add citation]: Studies show teams without regular user contact are 3x more likely to build unused features [needs source]"
### Flow Improvement
Consider reordering: Mistake 3 → Mistake 2 → Mistake 1
This builds from small to big impact.
Ready for the next section!
推荐写作项目的结构:
~/writing/article-name/
├── outline.md # 您的大纲
├── research.md # 所有研究和引用
├── draft-v1.md # 第一稿
├── draft-v2.md # 修订稿
├── final.md # 准备发布的版本
├── feedback.md # 收集的反馈
└── sources/ # 参考资料
├── study1.pdf
└── article2.md
每周安装量
2.5K
仓库
GitHub 星标数
47.3K
首次出现
Jan 20, 2026
安全审计
安装于
opencode2.1K
gemini-cli2.0K
codex2.0K
cursor1.8K
github-copilot1.8K
kimi-cli1.6K
This skill acts as your writing partner, helping you research, outline, draft, and refine content while maintaining your unique voice and style.
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.
Help me create an outline for an article about [topic]
Research [specific topic] and add citations to my outline
Here's my introduction. Help me make the hook more compelling.
I just finished the "Why This Matters" section. Review it and give feedback.
Review the full draft for flow, clarity, and consistency.
When a user requests writing assistance:
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! 🚀
User : "I'm writing an article about continuous discovery. Help me create an outline."
Process :
Result : Well-researched, properly cited article written in Teresa's voice with strong structure and flow.
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.
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."
User : "Just finished my 'Common Mistakes' section. Thoughts?"
Response :
# Feedback: Common Mistakes Section
## What Works Well ✓
- Strong examples (the Slack notification story)
- Clear structure (3 mistakes, clean layout)
- Practical advice for each mistake
## Suggestions
### Make It More Specific
Your second point says "Bad prioritization" but could be stronger:
Current:
> "Many teams prioritize badly by focusing on features instead of outcomes."
Suggested:
> "I've watched teams ship 14 features in a quarter yet move none of their key metrics. They prioritized activity over progress."
### Add Data
The third mistake would benefit from evidence:
> "[Add citation]: Studies show teams without regular user contact are 3x more likely to build unused features [needs source]"
### Flow Improvement
Consider reordering: Mistake 3 → Mistake 2 → Mistake 1
This builds from small to big impact.
Ready for the next section!
Recommended structure for writing projects:
~/writing/article-name/
├── outline.md # Your outline
├── research.md # All research and citations
├── draft-v1.md # First draft
├── draft-v2.md # Revised draft
├── final.md # Publication-ready
├── feedback.md # Collected feedback
└── sources/ # Reference materials
├── study1.pdf
└── article2.md
Weekly Installs
2.5K
Repository
GitHub Stars
47.3K
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
opencode2.1K
gemini-cli2.0K
codex2.0K
cursor1.8K
github-copilot1.8K
kimi-cli1.6K
头脑风暴技能:AI协作设计流程,将创意转化为完整规范与实施计划
75,000 周安装
AI智能体长期记忆系统 - 精英级架构,融合6种方法,永不丢失上下文
1,200 周安装
AI新闻播客制作技能:实时新闻转对话式播客脚本与音频生成
1,200 周安装
Word文档处理器:DOCX创建、编辑、分析与修订痕迹处理全指南 | 自动化办公解决方案
1,200 周安装
React Router 框架模式指南:全栈开发、文件路由、数据加载与渲染策略
1,200 周安装
Nano Banana AI 图像生成工具:使用 Gemini 3 Pro 生成与编辑高分辨率图像
1,200 周安装
SVG Logo Designer - AI 驱动的专业矢量标识设计工具,生成可缩放品牌标识
1,200 周安装