💬 Customer Support · Ticket Excellence

Close the loop from tickets to knowledge base

Every resolved pattern becomes a KB article; every article deflects future tickets measurably.

intermediate~30 minSupport EngineersCX LeadsHelpdesk Teams

Steps

1Tag tickets that needed a nonexistent article — queue them for writing
2Write from the customer's search phrase, not internal terminology
3Structure: symptom → quick fix → why it happens → when to escalate
4Link new articles in macro responses; measure deflection per view
5Prune/update top-20 articles quarterly against current product UI
6Celebrate deflection numbers alongside CSAT — both matter

Common Pitfalls

▲KB as dusty archive nobody updates after releases
▲Articles written to satisfy audits rather than searches

Commands

Install with skills CLI

$ npx skills add aniruddhaadak80/skills --skill kb-article-loop

Install globally

$ npx skills add aniruddhaadak80/skills --skill kb-article-loop -g

Tags

#knowledge-base#deflection#process#customer-support#ticket-excellence

Install this skill

$ npx skills add aniruddhaadak80/skills --skill kb-article-loop -a opencode

SKILL.md

# Close the loop from tickets to knowledge base

> Every resolved pattern becomes a KB article; every article deflects future tickets measurably.

## When to Use This Skill

Every resolved pattern becomes a KB article; every article deflects future tickets measurably.

## Steps

1. Tag tickets that needed a nonexistent article — queue them for writing
2. Write from the customer's search phrase, not internal terminology
3. Structure: symptom → quick fix → why it happens → when to escalate
4. Link new articles in macro responses; measure deflection per view
5. Prune/update top-20 articles quarterly against current product UI
6. Celebrate deflection numbers alongside CSAT — both matter

## Common Pitfalls

- KB as dusty archive nobody updates after releases
- Articles written to satisfy audits rather than searches

View source on GitHub ↗

Acknowledge → diagnose → act → verify structure with tone that survives angry Mondays.

💬 Customer Support·~25m

Open →

Diagnose with question trees, not guessworkintermediate

Branching diagnostics per issue class reaching root cause in minimum round-trips.

💬 Customer Support·~30m