Individual skill

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.

skills/help-center-article/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,539
Repository last updated: Nov 10, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

product-management Repository topic
productivity Repository topic
skills Repository topic
claude-skills Repository topic
agent-skills Repository topic
chatgpt Repository topic
claude-code Repository topic
cursor Repository topic
gemini Repository topic
prompt-engineering Repository topic
docs Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,502 bytes

Read excerpt


# 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).