help-center-article
Write a help-center / knowledge-base article that actually resolves the issue and deflects tickets. Use when asked to write a help doc, KB article, FAQ entry, how-to, or support documentation. Produces a findable, skimmable article — task-based title, the answer up front, numbered steps, screenshots-to-add markers, troubleshooting, and related links — written so users self-serve instead of contacting support.
npx skills add mohitagw15856/pm-claude-skills --skill help-center-article --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Help Center Article Skill A help article's job is deflection: the user finds it, solves their problem, and never opens a ticket. That requires a *findable* title (what they'd search), the answer **up front** (not after three paragraphs of preamble), and skimmable steps. This skill writes that — task-based, scannable, and SEO/search-friendly so it surfaces both in your help center and in Google. ## Required Inputs Ask for these only if they aren't already provided: - **The task/problem** — what the user is trying to do or fix (phrased as they'd search it). - **The solution** — the steps or answer. - **Audience** — end-user vs. admin/developer (changes depth and terminology). - **Edge cases / gotchas** — common failure points and prerequisites. ## Output Format ### [Task-based title — what the user searches] *e.g. "How to reset your password" / "Why is my export failing?" — not "Password Management."* **1. Short answer (TL;DR)** — resolve it in 1–2 sentences right at the top for the people who just need the quick fix. Then the detail for those who need it. **2. Before you start** — prerequisites/permissions, if any (so step 3 doesn't fail silently). **3. Steps** — numbered, one act
- Required Inputs
- Output Format
- [Task-based title — what the user searches]
- Quality Checks
- Anti-Patterns
- Based On
What does the help-center-article skill do?
Write a help-center / knowledge-base article that actually resolves the issue and deflects tickets. Use when asked to write a help doc, KB article, FAQ entry, how-to, or support documentation. Produces a findable, skimmable article — task-based title, the answer up front, numbered steps, screenshots-to-add markers, troubleshooting, and related links — written so users self-serve instead of contacting support.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill help-center-article --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.