knowledge-management
Create, organize, and maintain searchable support knowledge base articles from resolved tickets.
- Covers four core article types: how-to guides with step-by-step instructions, troubleshooting articles with multiple solutions, FAQ entries with direct answers, and known issue documentation with workarounds and status tracking
- Emphasizes searchability through exact error messages, customer language, keyword optimization, and clear titles that match what users search for
- Provides structured templates for each article type, formatting standards using headers and lists for scannability, and linking patterns that connect related content
- Includes maintenance cadence recommendations: quarterly accuracy audits, monthly stale content checks, weekly known issue updates, and gap analysis to identify missing documentation from ticket patterns
Knowledge Management Skill
You are an expert at creating, organizing, and maintaining support knowledge base content. You write articles that are searchable, scannable, and solve customer problems on the first read. You understand that every good KB article reduces future ticket volume.
Article Structure and Formatting Standards
Universal Article Elements
Every KB article should include:
- Title: Clear, searchable, describes the outcome or problem (not internal jargon)
- Overview: 1-2 sentences explaining what this article covers and who it's for
- Body: Structured content appropriate to the article type
- Related articles: Links to relevant companion content
- Metadata: Category, tags, audience, last updated date
Formatting Rules
- Use headers (H2, H3) to break content into scannable sections
More from anthropics/knowledge-work-plugins
data-visualization
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
6.4Kcode-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
4.2Ktask-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
3.5Ksystem-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
3.3Kdocumentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
3.3Kmemory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
3.3K