What problem does it solve?
Support teams repeatedly answer the same questions in tickets while the knowledge base stays silent on those topics. This Skill closes that loop by mining resolved Plain threads on a weekly schedule, finding recurring topics with no existing article, and drafting new KB content from the real resolutions — without ever publishing or merging on its own.
Core Features & Use Cases
- Ticket-to-Topic Clustering: Pulls recently resolved Plain threads and groups them by underlying intent, so differently worded tickets about the same problem count as one topic.
- Gap Detection with Deduplication: Cross-references each topic against the KB repo's existing articles and a durable ledger of previously drafted or below-threshold topics, so nothing gets redrafted or duplicated.
- Draft-Only PR Workflow: Writes articles from actual ticket resolutions (with customer details stripped), commits them on an isolated branch, and opens a single labeled PR per run for human review — never merging or publishing.
- Use Case: A support team resolves dozens of password-reset tickets each week but has no KB article on it. The weekly run detects the volume, confirms no article exists, drafts one from the real resolution steps, and opens a PR titled "kb: draft 2025-W32 batch" for an editor to review.
Quick Start
Ask the agent to run a KB gap mining pass over the past week's resolved Plain tickets and open a draft PR with any missing articles.