kb-article

Draft a publish-ready knowledge base article from a resolved support issue.

704|58|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/openyak/desktop --skill kb-article-openyak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-article
Source: https://github.com/openyak/desktop/tree/main/backend/app/data/plugins/customer-support/skills/kb-article
Command: npx skills add https://github.com/openyak/desktop --skill kb-article-openyak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a publish-ready knowledge base article from a resolved support issue, common question, or documented workaround. It helps document solutions for self-service, reduces repeated questions, and keeps information accessible.

Core Features & Use Cases

  • Draft publish-ready knowledge base articles from resolved issues, common questions, or documented workarounds.
  • Structure content for searchability and self-service.
  • Generate helpful metadata and templates to standardize publishing across teams.

Quick Start

Draft a publish-ready knowledge base article from a resolved issue or common question using the kb-article command.

Frequently Asked Questions about kb-article

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

FAQPage Schema
How do I turn a resolved support ticket into a knowledge base article?

To draft a knowledge base article from a resolved support ticket, you use template-driven drafting to transform the issue and workaround into structured, publish-ready content. This ensures consistent formatting and searchability for self-service reference materials.

What is the best way to format self-service content from common customer questions?

The best way to format self-service content from common questions is to apply article templates that standardize structure and generate helpful metadata. This approach ensures the drafted content is searchable and ready for publishing across knowledge bases.

Can I generate metadata for FAQ content using documented workarounds?

Yes, you can generate metadata for FAQ content from documented workarounds. The drafting process automatically applies template-driven structures to ensure the content meets requirements for searchability and consistent formatting across reference materials.

Does template-driven drafting work for customer-support content workflows at scale?

Template-driven drafting works for customer-support content workflows by standardizing the conversion of recurring questions and resolved issues into self-service articles. It enforces consistent formatting and metadata requirements across teams to maintain publishing readiness.

When should I use automated article drafting for ticket resolution documentation?

You should use automated article drafting for ticket resolution documentation when you need to reduce repeated questions and keep information accessible. It is designed for customer-support workflows where resolved tickets must become structured, publish-ready knowledge base articles.

Why do my knowledge base articles lack consistent formatting for self-service publishing?

Knowledge base articles lack consistent formatting when they bypass template-driven drafting and metadata generation. Applying structured article templates standardizes the content, ensuring it meets publishing readiness and searchability requirements across support teams.