What do I need to use Help Center Article?

The task / problem; The solution; Audience; Edge cases / gotchas.

Is Help Center Article free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Help Center Article

Q: How do I know the Help Center Article output is good?

The skill verifies itself against its own quality checks: Title is a task/question the user would actually search (not an internal category name); The answer is at the top (TL;DR), not buried under preamble; Steps are numbered, one action each, with bolded UI labels and screenshot markers; Prerequisites are stated before the steps.

🔵 Stable🕐 updated 2026-10-06 🔷 SkillSpec L3 pm-support

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.

▶ Run it free — no key needed 📝 Grade your existing draft 📱 Use as an app View SKILL.md ↗ What changed

🗣 Say this to your agent

“Write a help doc.”“Write a knowledge-base article for this issue.”“Write a FAQ entry.”“Write support documentation that cuts tickets.”

What to give it

▸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.

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Title is a task/question the user would actually search (not an internal category name)

✓The answer is at the top (TL;DR), not buried under preamble

✓Steps are numbered, one action each, with bolded UI labels and screenshot markers

✓Prerequisites are stated before the steps

✓A troubleshooting section heads off the common follow-up tickets

✓Uses the user's vocabulary (findable in search), not internal jargon

⚠️ What it refuses to do

Do not bury the answer — front-load it; most readers want the quick fix, not your intro

Do not title by internal feature name — title by the user's task/question, or they won't find it

Do not skip troubleshooting — the "it didn't work" cases are exactly what generate the ticket you're trying to deflect

Do not use internal jargon — write the words users type

Do not cram multiple tasks into one article — one task per article = better search + clearer steps

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="help-center-article"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Help Center Article is one of 1307 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog