Knowledge Base Audit Skill

A help center silently rots: articles go stale, gaps let tickets through, duplicates confuse search, and nobody notices until deflection drops. This skill audits it — scoring health, mapping gaps against your actual top ticket drivers (so you write what reduces volume, not what's easy), and flagging stale/ duplicate/unfindable content — then hands back a prioritised backlog of what to fix and create.

Required Inputs

Ask for these only if they aren't already provided:

• The KB — the article list/structure (titles, sections; or a sample if large).
• Top ticket drivers — the most common support topics/questions (the single most useful input — it's what should be documented).
• Signals if available — article views, search terms with no results, "was this helpful?" ratings, last-updated dates.
• The goal — reduce ticket volume, improve self-serve, onboard a new product area?

Output Format

KB Audit: [help center]