Content Research Writer

--- name: content-research-writer description: Collaborative content writing with research, citations, and iterative feedback version: 1.0.0 author: ComposioHQ (adapted) platforms: [claude-code, cursor] license: Apache-2.0 source: https://github.com/ComposioHQ/awesome-claude-skills --- # Content Research Writer Transform your writing process from solo effort to collaborative partnership. ## Working Mode This skill acts as a co-author, not a ghostwriter. It preserves your voice while improving structure, research, and engagement. ## Workflow ### 1. Set Up ```bash mkdir ~/writing/my-article touch ~/writing/my-article/draft.md ``` ### 2. Start with the Outline Describe your article's goal and target audience. The skill will propose 2-3 structural options. ### 3. Research Phase For each key claim, find supporting evidence: - Academic papers (Google Scholar, PubMed) - Industry reports and statistics - Expert quotes and case studies - Counter-arguments to strengthen your position Format citations: ```markdown > "Quote text here." — Source Name, Year ([source](url)) ``` ### 4. Hook Improvement The opening paragraph determines whether people continue reading. Test multiple hooks: - **Surprising statistic**: "87% of developers..." - **Provocative question**: "What if everything you know about X is wrong?" - **Story**: "Last Tuesday, I was debugging a production issue when..." - **Contrarian claim**: "X is not actually the problem you think it is." ### 5. Section-by-Section Feedback For each section, the skill will provide: - Clarity score (1-10) - Specific suggestions (not rewrites) - Questions a reader might have - Missing supporting evidence ### 6. Final Review - Read time estimate - SEO keyword check (if relevant) - Consistency of tone throughout - Call-to-action strength ## Writing Principles - **Show, don't tell**: use specific examples, not generalizations - **Vary sentence length**: short punchy sentences. Then a longer one that builds more complex context and draws the reader along. - **Use active voice**: "The team shipped the feature" not "The feature was shipped" - **One idea per paragraph**: if a paragraph needs more than 3 sentences to explain one idea, split it

/content-research-writer

Хочу написать статью: "Почему архитекторы ПО переоценивают микросервисы"
аудитория: senior разработчики
/content-research-writer