knowledge-management

Creates structured, searchable knowledge base articles from resolved support tickets.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/chelleboyer/reachy_mini_retail_assistant --skill knowledge-management-chelleboyer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/chelleboyer/reachy_mini_retail_assistant/tree/main/skills/customer-support/skills/knowledge-management
Command: npx skills add https://github.com/chelleboyer/reachy_mini_retail_assistant --skill knowledge-management-chelleboyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations often face ticket backlogs and repeated questions. This skill helps you write and maintain knowledge base content from resolved support issues to make them searchable and reusable, reducing future tickets.

Core Features & Use Cases

  • Universal Article Elements: Enforces a consistent structure with Title, Overview, Body, Related articles, and Metadata to improve findability.
  • Formatting Rules: Uses headers, numbered lists, bullet lists, bold terms, code blocks for commands, and tables to ensure readability and scannability.
  • Common Article Types: Supports How-to, Troubleshooting, FAQ, and Known Issue article formats, with examples and best practices.
  • Review & Maintenance Cadence: Defines draft, published, needs update, archived, and retired lifecycle, plus quarterly accuracy audits and weekly known-issues updates.
  • Linking & Taxonomy: Encourages category-based organization and safe internal linking to improve navigation.

Quick Start

Draft a How-to KB article detailing the resolution and step-by-step instructions from ticket 12345.

Frequently Asked Questions about knowledge-management

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

FAQPage Schema
How do I convert resolved support tickets into searchable knowledge base articles?

To create knowledge base articles from resolved support tickets, draft structured content using enforced elements like Title, Overview, Body, and Metadata. This ensures your post-resolution work becomes searchable and reusable.

What is the best structure for a knowledge base article to improve searchability?

The best structure for knowledge base searchability uses Title, Overview, Body, Related articles, and Metadata. Formatting rules enforce headers, numbered lists, bold terms, and code blocks to ensure scannability and findability.

What types of knowledge base articles can I create for support tickets?

You can create How-to, Troubleshooting, FAQ, and Known Issue knowledge base articles from support tickets. Each common article type includes specific examples and best practices for formatting and metadata tagging.

How do I maintain knowledge base content accuracy over time?

Maintain knowledge base accuracy through a defined lifecycle of draft, published, needs update, archived, and retired states. Conduct quarterly accuracy audits and update known-issues articles weekly to ensure ongoing consistency.

Can I use ticket resolution details to build a troubleshooting knowledge base?

Yes, you can build troubleshooting knowledge base articles directly from ticket resolution details. The process enforces consistent formatting, metadata tagging, and category-based linking to make troubleshooting steps easily searchable.