skills.rest
lilbom32
lilbom32COMMUNITY
Explore all skills by this author →
GitHub

knowledge-management

Create standardized knowledge base articles from resolved support tickets.

Updated Mar 15, 2026
Search Tags:#troubleshooting#faq#how-to#knowledge-management#knowledge-base#kb-articles#support-content
One-click install
npx skills add https://github.com/lilbom32/ketnoitrithuc --skill knowledge-management-lilbom32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/lilbom32/ketnoitrithuc/tree/main/.claude/skills/customer-support/1.1.0/skills/knowledge-management
Command: npx skills add https://github.com/lilbom32/ketnoitrithuc --skill knowledge-management-lilbom32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and maintaining knowledge base articles from resolved support issues can be time-consuming and error-prone. This skill standardizes documentation so teams produce clear, searchable content that reduces repeat tickets and speeds onboarding.

Core Features & Use Cases

  • KB Article Creation: Provides a consistent template to capture the title, overview, body, related articles, and metadata.
  • Content Structuring & Readability: Enforces headings, bullet lists, callouts, and formatting for scannability.
  • Maintenance & Audits: Guides quarterly reviews and updates to keep knowledge fresh.
  • Use Case: After closing a ticket, generate a how-to guide or troubleshooting article that can be linked from related topics.

Quick Start

Create a new KB article from a resolved ticket using the standard template.

Frequently Asked Questions about knowledge-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a knowledge base article from a resolved support ticket?▼

To create a knowledge base article from a resolved ticket, organize the solution into a standardized structure featuring a title, overview, body, related articles, and metadata including category, tags, audience, and last updated date.

What is the standard structure for writing searchable how-to guides and troubleshooting docs?▼

The standard structure for searchable how-to guides and troubleshooting docs includes a clear title, an overview, a scannable body with headings and bullet lists, related articles, and metadata like category and tags to improve searchability and reduce repeat support tickets.

How do I keep my support content and FAQ knowledge base fresh over time?▼

Keeping support content and FAQ knowledge bases fresh requires conducting quarterly maintenance reviews and audits to update articles, ensuring the troubleshooting documentation remains accurate and relevant for onboarding and support workflows.

Can I use this knowledge management approach for FAQs across different product areas?▼

Yes, you can apply this knowledge management approach to create FAQs, how-to guides, and troubleshooting docs across various support workflows and product areas by enforcing consistent formatting, metadata tagging, and standardized article templates.

What is the best way to format KB articles for scannability and readability?▼

The best way to format KB articles for scannability is to enforce headings, bullet lists, and callouts within the body, ensuring the support content remains structured and easy to read for users seeking troubleshooting steps.

Related Skills

Explore More Content & Communication Skills→
lohaslelohasle

knowledge-management

Generate knowledge base articles from resolved support issues.

Community
Intermediate
akiotanaka847akiotanaka847
2

write-an-article

Convert resolved support conversations into help-center drafts and status communications.

Community
Advanced
OneWave-AIOneWave-AI
245

inbound-lead-qualifier

Score inbound leads by ICP fit, intent, and urgency, then route them.

Official
Basic
pascallammerspascallammers
1

meeting-insights-analyzer

Extract action items, decisions, topics, and sentiment from meeting transcripts.

Community
Intermediate