AI Agent Hub
Back to skills
Content Research Writer icon

Content Research Writer

Content Creation Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_24e9cdd5/content-research-writer.

About this skill

The Problem

Writing long-form content, tutorials, or newsletters often fails not for lack of ideas, but for scattered notes, weak openings, inconsistent citations, and feedback that arrives too late. Revision can also flatten the author's voice until the piece reads like a generic template.

How It Works

The skill treats writing as a collaborative, inspectable workflow:
- Scope first: confirm topic, reader, length, goal, and tone.
- Outline together: turn ideas into a logical sequence and expose research gaps.
- Research and cite: gather trustworthy sources, extract facts, quotes, and data, then format them as inline, numbered, or footnote references.
- Strengthen hooks: analyze the opening and propose alternatives such as a bold claim, a personal story, or a striking statistic.
- Review section by section: check clarity, pacing, evidence, and tone without waiting for a full draft.
- Preserve voice: use the author's samples to shape suggestions, improving the writing rather than replacing it.

Boundaries

It fits blogs, technical docs, case studies, and thought-leadership pieces, but it does not publish, verify every claim, or replace author review. For command-heavy tutorials, still validate versions, edge cases, and sources. For long projects, keep research.md, draft-v1, and draft-v2 separate.

Use Cases

  • Before drafting a technical blog post, outline the argument and identify API data or sources that still need citation.
  • Strengthen a newsletter opening with three hook alternatives based on a bold claim, story, or statistic.
  • Review each tutorial section for clarity while keeping the author’s conversational tone intact.
  • Compile credible sources for a case study and format citations into a consistent numbered list.

Best For

  • Engineers who publish technical blogs and need sources, hooks, and section-level feedback polished together.
  • Content editors who ship newsletters and want strong openings while preserving a personal voice.
  • Technical writers who build tutorials and need steps, code examples, troubleshooting notes, and citations kept clear.
  • Founders or product leads who draft thought-leadership posts and need distinct angles, research, and stronger argumentation.