knowledge-management

Create and organize customer-facing knowledge base articles with templates and metadata.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/yethikrishna/humble --skill knowledge-management-yethikrishna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/yethikrishna/humble/tree/main/core/kortix-master/opencode/skills/GENERAL-KNOWLEDGE-WORKER/knowledge-management
Command: npx skills add https://github.com/yethikrishna/humble --skill knowledge-management-yethikrishna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many support teams lack consistent, searchable knowledge base content, causing repeated ticket volume and slow customer resolution. This Skill provides a repeatable framework for writing KB articles that are scannable, findable, and actionable so customers solve problems on first read.

Core Features & Use Cases

  • Article templates for how-tos, troubleshooting, FAQs, and known issues that enforce title, overview, body, related articles, and metadata.
  • Search and findability guidance including title best practices, keyword optimization, and customer-language recommendations to improve search relevance.
  • Maintenance cadence and lifecycle guidance to audit, update, archive, and retire content to prevent decay and stale guidance.
  • Use case: turn a frequent support ticket into a verified how-to article with step-by-step steps, verification instructions, and links to troubleshooting guidance to reduce repeat tickets.

Quick Start

Draft a concise, searchable KB article with a clear title, a 1–2 sentence overview, structured numbered steps, related links, and metadata including category, tags, audience, and last updated date.

Frequently Asked Questions about knowledge-management

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

FAQPage Schema
How do I write a knowledge base article that reduces support tickets?

To write a knowledge base article that reduces tickets, draft scannable content with a clear title, a 1-2 sentence overview, numbered steps, and metadata. This structure helps customers discover and solve problems on their first read without contacting support.

What is the best way to structure a troubleshooting guide for a SaaS product?

The best way to structure a SaaS troubleshooting guide is using a template that enforces a clear title, concise overview, step-by-step body, related article links, and metadata like category and tags to ensure searchability and fast resolution.

How do I make my support documentation more searchable for customers?

Make support documentation searchable by applying title best practices, keyword optimization, and customer-language recommendations. Using the exact terms customers search for improves search relevance and content findability across your knowledge base.

What types of KB articles should my support team create for web products?

Support teams should create KB articles for how-tos, troubleshooting guides, FAQs, known issues, and maintenance procedures for web products. Using structured templates ensures these articles remain scannable, findable, and actionable for customers.

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

Maintain a knowledge base and prevent stale content by following a maintenance cadence and lifecycle guidance. This involves scheduling regular audits to update, archive, or retire outdated articles so customers never encounter decayed guidance.

Can I turn frequent support tickets into verified how-to articles?

You can turn frequent support tickets into verified how-to articles by applying a structured framework. Transform the ticket resolution into numbered steps, add verification instructions, and link to troubleshooting guidance to reduce repeat tickets.