# Self Service And Knowledge

Builds the help center, in-product guidance, and knowledge base that let customers...

- Repository: https://github.com/cbrock84/headcount (2554 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-18
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add cbrock84/headcount --skill self-service-and-knowledge -g -a claude-code -y`
Codex: `npx skills add cbrock84/headcount --skill self-service-and-knowledge -g -a codex -y`
Cursor: `npx skills add cbrock84/headcount --skill self-service-and-knowledge -g -a cursor -y`
Gemini CLI: `npx skills add cbrock84/headcount --skill self-service-and-knowledge -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add cbrock84/headcount`

## Description

Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone, content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Self-service and knowledge

Good self-service is the cheapest support you will ever run and the most neglected. It is also
frequently the wrong answer, an article explaining a confusing screen is a bandage on a design
problem.

## Decide what deserves an article

Before writing, ask whether the contact should exist. If people repeatedly need instructions for one
screen, the screen is the defect. Documenting it makes the problem permanent and invisible.

Write articles for things that are genuinely complex, genuinely occasional, or genuinely outside
your control. Not for things that are merely badly designed.

## What to write, and in what order

Rank by contact volume, not by feature importance. The most-viewed help content is almost never
what the team expected, it is billing, access, and the one confusing setting.

Structure each article around the customer's task, in their words, not your feature's name. People
search for what they are trying to do.

- **Answer first.** The steps in the first screen, context afterward. Nobody arrives wanting
  background.
- **One task per article.** Combined articles fail search, because the match lands on the wrong half.
- **Show the actual interface**, real labels, real button names, updated when they change.
- **Say what to do when it does not work.** The next step, and how to reach a human. Making that
  hard converts a solvable problem into a complaint about you hiding.

## Findability decides everything

An article nobody finds does not exist. Findability comes from titles matching real search language,
in-product links at the moment of confusion, and search that tolerates the words customers actually
use rather than your internal vocabulary.

Read your help-center search logs, especially the queries returning nothing. That list is your
content backlog, ranked by demand, already written for you.

## In-product beats the help center

The rest: https://github.com/cbrock84/headcount/blob/HEAD/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md