Knowledge Base Article Writer

What it does

Reads the original question and the agent's resolution steps from a closed ticket, strips out anything specific to that one customer, and rewrites it as a generalized how-to or troubleshooting article with a clear title, steps, and a fallback line. Checks the existing knowledge base first so it doesn't create a near-duplicate of an article that already exists.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/knowledge-base-article-writer/ (or ~/.claude/skills/knowledge-base-article-writer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/knowledge-base-article-writer/

OpenAI Codex

.codex/skills/knowledge-base-article-writer/

Cursor

.cursor/skills/knowledge-base-article-writer/ (or ~/.cursor/skills/knowledge-base-article-writer/ globally)

Compatibility

Any WordPress site with a knowledge base built on pages, a custom post type, or a documentation plugin; ticket source can be any helpdesk that exports resolved ticket text.

The complete SKILL.md for this skill:

---
name: knowledge-base-article-writer
description: Use when a user wants a resolved support ticket turned into a help-center article, or asks to "write a KB article" or "document this fix".
---

# Knowledge Base Article Writer

## When to use
A support ticket just got resolved and the fix is likely to come up again, so it's worth turning into a reusable knowledge base article instead of staying buried in a closed ticket.

## Procedure
1. Read the resolved ticket: the original question, and the exact steps the agent used to fix it.
2. Search the existing knowledge base for a similar title or topic to avoid duplicating an article.
3. Generalize the problem statement, removing the customer's name, account specifics, and one-off details.
4. Draft a title as a question or task, then numbered resolution steps.
5. Add a short "still need help?" line linking to support, and suggest 2-3 related articles to cross-link.
6. Mark the draft as pending review rather than publishing directly.

## Guardrails
- Never publish automatically, always leave the article as a draft since one ticket's fix may not generalize to every case.
- Don't include customer-identifying details (name, email, order number) in the generalized article.