knowledge-management

Create knowledge base articles from resolved customer tickets.

2|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/GACLove/feishu-aily-skills --skill knowledge-management-gaclove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/GACLove/feishu-aily-skills/tree/main/skills/knowledge-management
Command: npx skills add https://github.com/GACLove/feishu-aily-skills --skill knowledge-management-gaclove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and standardize solutions from resolved support tickets so knowledge is searchable, actionable, and reduces repeat incidents. This Skill prevents knowledge loss, speeds future troubleshooting, and ensures answers are discoverable by customers and agents.

Core Features & Use Cases

  • Structured article templates for how-to guides, troubleshooting, FAQs, and known issues that enforce overview, prerequisites, step-by-step solutions, verification, and related links.
  • Search and discoverability optimization including title best practices, keyword guidance, and tagging so customers find answers by symptom or common phrasing.
  • Governance & maintenance cadence with review schedules, stale content checks, analytics-driven gap analysis, and clear signals for when to update versus create new articles.
  • Use case: Convert a resolved "Connection refused during data import" ticket into a how-to KB article with reproduction steps, root cause, fix, verification steps, and links to related configuration docs.

Quick Start

Create a KB article summarizing the resolved ticket "Connection refused during data import" using the How-to template with overview, prerequisites, step-by-step resolution, verification steps, metadata, and related links.

Frequently Asked Questions about knowledge-management

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

FAQPage Schema
How do I turn resolved support tickets into a searchable knowledge base?

Create a knowledge base from resolved tickets by applying structured templates that enforce overviews, prerequisites, step-by-step solutions, verification steps, metadata, and related links to ensure content is searchable and scannable.

What is the best way to write a troubleshooting article for a known issue?

Writing a troubleshooting article for a known issue requires a structured template covering the overview, reproduction steps, root cause, fix, verification steps, and related links to ensure customers can resolve the problem.

How do I optimize KB content for search and discoverability?

Optimize KB content for search and discoverability by applying title best practices, keyword guidance based on common customer phrasing, and systematic metadata tagging so articles surface by symptom.

When should I update an existing KB article versus create a new one?

Decide to update an existing KB article versus creating a new one by using governance signals like stale content checks and analytics-driven gap analysis to determine if the current content covers the resolved issue.

How do I maintain and review a knowledge base to prevent stale content?

Maintain a knowledge base and prevent stale content by establishing a governance and maintenance cadence with scheduled reviews, analytics-driven gap analysis, and clear signals for when to update existing articles.