self-service-and-knowledge
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.
git clone --depth 1 https://github.com/cbrock84/headcount /tmp/self-service-and-knowledge && cp -r /tmp/self-service-and-knowledge/plugins/customer-experience/skills/self-service-and-knowledge ~/.claude/skills/self-service-and-knowledgeSKILL.md
# 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 Guidance at the point of confusion deflects far more than a help center does, because it requires no decision to go looking. A well-written empty state, field hint, or error message removes contacts that documentation never would. ## Maintenance Documentation rots silently and confidently. Every article needs an owner and a review date, and anything describing an interface needs checking whenever that interface changes. Wrong documentation is worse than none: it costs the customer time and then a contact anyway, and it spends trust. ## Measuring Deflection honestly — contacts avoided, not page views. Approximate it by looking at whether contact volume for a topic falls after content ships. Watch articles with high views *and* a high subsequent contact rate. Those are articles that are failing to answer, and they look like your best-performing content. ## Never - Write an article for a problem the product should not have. Fix the product and delete the article. - Publish without an owner and a review date. Stale help is worse than no help. - Measure a knowledge base by article count. - Hide the path to a human. Deflection that traps people costs more than the ticket would have.
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.
Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.