Skip to main content
Skills/Customer Support/knowledge-base-writer

Knowledge Base Writer Skill

Creates help center articles and knowledge base entries from support conversations and product documentation.

A reusable skill package for Claude Code and Cowork.

When to use this skill

  • Converting resolved support tickets into KB articles
  • Building a self-service help center from scratch
  • Updating outdated help articles after product changes
  • Creating FAQ pages from common customer questions

What this skill does

Analyzes support conversations or product specs, identifies recurring questions, and writes clear, structured KB articles with step-by-step instructions, screenshot callouts, and troubleshooting sections.

How it works

  1. 1Identify the question or issue from source material (ticket, spec, or notes)
  2. 2Structure article: problem statement, prerequisites, step-by-step resolution, and related articles
  3. 3Write in plain language for the target audience (end-user or developer)
  4. 4Add troubleshooting section for common variations and edge cases

Full Skill Definition

---
name: knowledge-base-writer
description: "Creates help center articles and knowledge base entries from support conversations and product documentation."
---

# Knowledge Base Writer

## Overview

You are a technical writing specialist focused on creating clear, structured documentation.

## Purpose

Generate comprehensive, well-organized documentation from source material.

## When to Use

When a user needs to document APIs, features, workflows, or technical systems.

## Documentation Process

## Step 1: Analyze Source Material & Define Scope

Clarify the documentation's purpose and what it should cover. Read the code, API spec, or description provided. Identify the audience (developer, end-user, admin).

## Step 2: Structure Content

Organize into: Overview, Prerequisites, Getting Started, Core Concepts, API Reference (if applicable), Examples, Troubleshooting.

## Step 3: Write Documentation

Use clear, concise language. Include code examples. Follow the inverted pyramid — most important info first.

## Step 4: Cross-Reference & Validate

Link related sections. Add a table of contents for documents over 500 words. Review the documentation for accuracy against the source material and have a subject matter expert validate technical claims.

## Error Handling

## Incomplete Source Material

Note gaps in the documentation and ask the user to provide missing details.

## Ambiguous APIs

When behavior is unclear, document the observed behavior and flag it for verification.

## Maintenance Plan

Recommend a documentation update process that is tied to the development workflow (e.g., docs updated as part of PR reviews) to prevent documentation from drifting from reality.

Summary

Creates help center articles and knowledge base entries from support conversations and product documentation. Install this skill by placing the package in ~/.claude/skills/knowledge-base-writer/ for personal use, or .claude/skills/knowledge-base-writer/ for project-specific use.

FAQs

What help center platforms does it target?

It produces Markdown compatible with Intercom, Zendesk, Notion, Confluence, and any Markdown-based help center.

Can it batch-process multiple tickets into articles?

Yes. Share several resolved tickets on the same topic and it will synthesize them into a single comprehensive article.

Does it optimize articles for search?

Yes. It adds keyword-rich titles, tags, and related article links to improve in-product and Google search discoverability.

Download & install

Install paths

Claude Code — personal (all projects)

~/.claude/skills/knowledge-base-writer/SKILL.md

Claude Code — project-specific

.claude/skills/knowledge-base-writer/SKILL.md

Cowork — skill plugin

Upload .skill.zip via Cowork plugin manager

Compatible with Claude Code, Cowork, and any SKILL.md-compatible agent platform.

Skills in the registry are community starter templates provided as-is. skill.design and Designless do not guarantee accuracy, completeness, or fitness for any purpose. Always review, customize, and validate skills for your specific use case before deploying to production. You are responsible for the behavior of skills you install and use.