---
name: knowledge-base-article-writer
description: Write clear knowledge base and help-center articles that let users solve problems without asking a human. Use this skill whenever a user needs a help article, a knowledge base entry, support documentation, an FAQ answer, or says 'write a help article for', 'document this for our KB', or 'reduce these repeat support questions'. Trigger whenever a recurring question or task should become self-serve documentation.
---

# Knowledge Base Article Writer

## What this does and why it matters
Every recurring question a human answers is a knowledge base article waiting to be written. This skill turns a problem or task into a clear, findable help article that lets the user solve it themselves, cutting support load and frustration. Good self-serve docs scale support without scaling headcount.

## Inputs to gather
1. The question or task the article addresses.
2. The steps to resolve it, and any prerequisites.
3. The audience's technical level.
4. Common variations, errors, or related questions.

## Method

### 1. Title as the user's question
Write the title the way a user would search, phrased as their problem ("How to reset your password"), so it is findable. Findability is half of a help article's job.

### 2. Answer or orient immediately
Start with the answer or a one-line orientation, not background. A help-seeker is impatient and mid-problem.

### 3. Give clear, ordered steps
Numbered, specific steps at the user's technical level, with what they will see at each point so they know they are on track. Note where a screenshot would help.

### 4. Handle the common variations and errors
Address the "what if" and the frequent error messages inline, since those are the reasons users escalate to a human.

### 5. Link related articles
Point to adjacent topics, so the user can self-serve the next question too.

### 6. Keep it current-friendly
Structure so it is easy to update when the product changes.

## Output format
ALWAYS use:

# [Title as the user's question]
## Quick answer / what this covers
## Before you start (prerequisites)
## Steps (numbered, with what the user will see)
## Troubleshooting (common errors and fixes)
## Related articles

## Anti-patterns to avoid
- A title no user would ever search.
- Background before the answer.
- Steps that skip what the user should see, so they lose their place.
- Ignoring the common errors, which are the real reason people ask a human.

## Example
An article titled "How to connect your CRM" opens with a one-line summary, lists prerequisites, gives six numbered steps noting the confirmation screen, troubleshoots the two most common connection errors, and links to the sync-settings article.