Skill-Details

content-writing

Direct match for researching, outlining, drafting, reviewing, and polishing articles.

ÜbereinstimmungDirektGeprüft für content-erstellung
Quelleeyadsibai/ltkExterne Quelle
Gemeldete Installationen169Nur Popularitätssignal

Vor Nutzung prüfen

Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.

Gespeicherte Quellvorschau

SKILL.md

Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.

---
name: content-writing
description: Use when "writing articles", "blog posts", "content creation", "research writing", "technical writing", or asking about "outlining", "citations", "improving hooks", "writing feedback"
version: 1.0.0
---

<!-- Adapted from: awesome-claude-skills/content-research-writer -->

# Content Research & Writing Guide

Collaborative writing partner for articles, blog posts, and documentation.

## Workflow Overview

1. **Outline** - Structure ideas collaboratively
2. **Research** - Find sources and add citations
3. **Write** - Draft section by section
4. **Feedback** - Get review on each section
5. **Polish** - Final review and refinement

## File Organization

```
~/writing/article-name/
├── outline.md          # Structure
├── research.md         # Sources and citations
├── draft-v1.md         # First draft
├── draft-v2.md         # Revised
├── final.md            # Publication-ready
└── sources/            # Reference materials
```

## Outline Template

```markdown
# 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
- [Research needed: topic]

### Section 2: [Title]
- Key point C
- Evidence/data needed

## Conclusion
- Summary
- Call to action
- Final thought

## Research To-Do
- [ ] Find data on [topic]
- [ ] Source for [claim]
```

## Hook Improvement

When reviewing introductions, consider:

- **Does it create curiosity?**
- **Does it promise value?**
- **Is it specific enough?**
- **Does it match the audience?**

### Hook Types

| Type | Example |
|------|---------|
| Bold statement | "Product management will never be the same." |
| Question | "What if you could talk to every customer before coffee?" |
| Story | "Sarah spent two weeks building the wrong feature..." |
| Data | "Last month, AI analyzed 500 interviews in 30 minutes." |

## Section Feedback Format

```markdown
# Feedback: [Section Name]

## What Works Well ✓
- [Strength 1]
- [Strength 2]

## Suggestions

### Clarity
- [Issue] → [Fix]

### Flow
- [Transition issue] → [Better connection]

### Evidence
- [Claim needing support] → [Add citation]

## Specific Line Edits

Original:
> [Quote from draft]

Suggested:
> [Improved version]

Why: [Explanation]
```

## Citation Formats

**Inline:**

```
Studies show 40% improvement (McKinsey, 2024).
```

**Numbered:**

```
Studies show 40% improvement [1].

[1] McKinsey Global Institute. (2024)...
```

## Pre-Publish Checklist

- [ ] All claims sourced
- [ ] Citations formatted
- [ ] Examples clear
- [ ] Transitions smooth
- [ ] Call to action present
- [ ] Proofread for typos

## Voice Preservation

- Learn writer's style from samples
- Suggest, don't replace
- Match tone (formal/casual/technical)
- Ask: "Does this sound like you?"
Vollständige Quelle auf GitHub lesen (öffnet externe Seite)
Kontext

Verwandte Arbeit