kb-article

To convert resolved support tickets into knowledge base articles, draft the documented workaround or solution into a structured format with clear sections and metadata. This standardizes content for self-service portals and improves searchability.

The best way to structure a KB article for customer self-service is to organize content with clear sections, apply standardized metadata, and use a Markdown body that delivers step-by-step guidance, ensuring readability and searchability.

Yes, you can use YAML frontmatter to standardize internal documentation workflows by providing required metadata like name and description, while the Markdown body delivers the steps and guidance used at activation.

Drafting KB articles from common questions improves self-service by standardizing responses and converting recurring questions into searchable How-To or Known Issue articles, which reduces future inbound support requests.

To draft publish-ready KB articles from support issues, you need a resolved issue, common question, or documented workaround, which is then structured with clear sections and metadata to ensure the content is search-ready.

A limitation of using Markdown for knowledge base article writing is that the SKILL.md requires a YAML frontmatter providing at least the name and description; without this structure, the steps and guidance cannot be properly activated.