knowledge-management

Create searchable knowledge base documentation from resolved support issues.

7|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill knowledge-management-epiphytic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/Epiphytic/ai-plugin-translator/tree/main/packages/core/test/fixtures/regression-output/knowledge-work-plugins/customer-support/skills/knowledge-management
Command: npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill knowledge-management-epiphytic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps support teams turn resolved issues into clear, searchable knowledge base content that reduces repeat questions and improves customer self-service.

Core Features & Use Cases

  • Knowledge Base Writing: Create structured how-to guides, troubleshooting articles, FAQs, and known issue documentation.
  • Content Optimization: Apply search-friendly titles, customer-focused language, formatting standards, categorization, and linking practices.
  • Use Case: Document a resolved support ticket by transforming the solution into a searchable troubleshooting article that helps future customers resolve the same issue.

Quick Start

Create a knowledge base article from this resolved support issue and format it using the recommended structure.

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 searchable knowledge base article from a resolved support ticket?

To create a searchable knowledge base article, transform the resolved support issue into structured documentation using customer-focused language, search-friendly titles, and standardized formatting. This process ensures the troubleshooting solution is easily discoverable by future customers.

What is the best way to write troubleshooting documentation for a customer support knowledge base?

The best way to write troubleshooting documentation is to apply customer-focused writing standards, clear categorization, and search optimization practices. Structuring the content with recommended formatting ensures users can efficiently find and resolve their own issues.

How do I structure how-to guides and FAQs for customer self-service?

Structure how-to guides and FAQs by applying standardized article formatting, search-friendly titles, and logical categorization. This approach creates clear, self-service documentation that reduces repeat support questions and improves content discoverability.

Can I use this to document known issues and provide lifecycle maintenance for support content?

Yes, you can document known issues and apply lifecycle maintenance guidance to keep support content accurate. This ensures troubleshooting articles and FAQ records remain updated and relevant for ongoing customer self-service needs.

Why does my support team need structured knowledge base content instead of just saving ticket resolutions?

Structured knowledge base content is needed because it applies search optimization and customer-focused writing to raw ticket resolutions. This transforms isolated solutions into discoverable how-to guides that reduce repeat questions and enable self-service.

What are the limitations of relying on standard notes versus a structured knowledge base for customer support?

Standard notes lack the search-friendly titles, categorization, and structured formatting required for effective knowledge base management. Without these optimization practices, customers struggle to find troubleshooting solutions, leading to increased repeat support questions.