knowledge-management

Create and optimize searchable knowledge base articles with standardized headings and metadata.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent, hard-to-find, and ineffective support documentation by providing a repeatable framework for creating organized, searchable knowledge base articles that reduce future support ticket volume.

Core Features & Use Cases

  • Article templates and structure: Standardized how-to, troubleshooting, FAQ, and known-issue formats to ensure consistency and scannability.
  • Search and keyword guidance: Advice on titles, synonyms, and exact error phrasing to improve discoverability.
  • Maintenance cadence and lifecycle: Schedules and criteria for review, updates, archiving, and retirement to keep content accurate.
  • Linking and taxonomy: Best practices for categories, internal linking, and avoiding circular references to guide users between related content.
  • Use Case: Turn a resolved support ticket into a published how-to article with verification steps and related links to reduce repeat tickets.

Quick Start

Create a scannable how-to article for configuring SSO with Okta that includes a one-sentence overview, prerequisites, step-by-step actions, verification steps, common issues, 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 create a knowledge base article from a resolved support ticket?

To create a knowledge base article from a resolved ticket, structure the content with a one-sentence overview, prerequisites, step-by-step actions, verification steps, common issues, and related links to reduce repeat tickets.

What is the best way to structure troubleshooting articles for scannability?

The best way to structure troubleshooting articles is using standardized formats with scannable headings, exact error phrasing, and metadata-rich content, ensuring users can quickly find and verify solutions.

How do I make support documentation more searchable and reduce support ticket volume?

Make support documentation more searchable by applying keyword guidance, using exact error phrasing in titles, incorporating synonyms, and maintaining standardized how-to and known-issue article formats.

Can I use standardized templates for how-to guides and FAQs?

Yes, you can use standardized templates for how-to guides and FAQs to ensure content consistency, scannability, and metadata richness across all customer support documentation.

How do I maintain knowledge base content accuracy over time?

Maintain knowledge base content accuracy by applying a scheduled maintenance cadence that defines specific criteria for reviewing, updating, archiving, and retiring articles.

Why do I need internal linking and taxonomy in a knowledge base?

Internal linking and taxonomy are needed to organize categories, guide users between related content, and avoid circular references, ensuring effective navigation across support documentation.