Help Center Article Generator
Most help articles are written by people who already know the product, which makes them useless for anyone who doesn't. The Help Center Article Generator writes for the panicked user — answer in the first sentence, one action per step, no jargon, no preamble.
What this skill does
A help article is read by someone frustrated, probably in front of a client, who needs the thing to work right now. The Help Center Article Generator writes for that reader specifically. Answer first, explain later. The opening sentence resolves the 80% case; everything below is context, edge cases, or troubleshooting for the people who need it.
Every article runs the SOLVE framework: Start with the answer, Outline the steps, Layer the detail, Verify understanding, Eliminate jargon. The first sentence is the article — if someone reads only the opening paragraph and leaves, they should have what they came for. Numbered steps follow with one action each. "Click Settings, then scroll down and find Notifications and click on it" gets broken into three steps because compound instructions are where users lose their place.
Bold marks UI elements so they pop out during scanning. The skill assumes nobody is reading the article linearly — they're skimming for the button name and the next step. Headers break long articles into chunks. Confirmation lines tell the user what they should see at each step, which is the difference between a guide that builds confidence and one that leaves the user wondering whether they're on the right screen.
Troubleshooting is treated as part of the article, not a separate page. If a step commonly fails — pop-up blockers stop a download, filters silently exclude rows, a permission is required and not flagged — it gets surfaced inline as a note, and the recurring failure modes go in a Troubleshooting block at the bottom. A help article that doesn't anticipate the common failure has just generated a ticket.
Jargon gets stripped to the user's vocabulary. If a technical term is necessary — API key, OAuth, webhook — it gets defined in parentheses on first use. The skill reads the draft as if it has never seen the product, and flags any sentence that requires prior knowledge. Screenshots are referenced ([Screenshot: export button highlighted]) rather than relied on — the written steps stay complete on their own because screenshots go stale every product release, and users on screen readers need the text either way.
When this triggers
- ·You're shipping a feature and need a help article live before the support queue fills up
- ·Your existing docs assume context and customers keep needing to email anyway
- ·You want a knowledge base structured so a frustrated user finds the answer in 30 seconds
- ·You're standardising a help centre after a year of articles written by whoever was nearest
- ·An article keeps generating follow-up tickets and you need to figure out which step is failing
Example
Trigger
User: 'Write a help article for exporting reports as CSV. Web app only. Common confusion is that filters apply to the export — people don't realise.'
Output
How to export a report as a CSV To export a report, open the report, click Export in the top-right, choose CSV, and click Download. The export will include any filters you have applied. Before you start · You need at least Viewer access to the report · Pop-ups must be allowed for the download to trigger Steps Step 1: Open the report Click the report name in your Reports list. You should see the report load with your saved filters in the top bar. Step 2: Click Export Look for the **Export** button in the top-right corner. Step 3: Choose CSV Select **CSV** from the format options. > Note: any filters currently applied to the report > will apply to the export. If you want the full dataset, > clear the filters before exporting. Step 4: Click Download The file downloads to your default downloads folder, named [report-name]-[date].csv. You're done You should see the CSV file in your downloads. Opening it in Excel or Google Sheets will show your filtered data with column headers in the first row. Troubleshooting The download didn't trigger Check pop-up blockers. The file downloads silently in some browsers — look in your Downloads folder before retrying. The CSV is empty or missing rows Filters are applied to the export. Clear all filters and re-export to see the full dataset. Related articles · How to schedule a recurring export · How to export multiple reports at once Last updated: [date] | Applies to: Web
Get this skill + 7 more
Get the full Customer Support pillar (8 skills) or the complete library.
Get the full stack — $299What you get
- 148-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Customer Support
Not generic "just checking in" messages — strategic outreach timed to customer milestones, usage patterns, and relationship stages that make clients feel valued and remind them why they're paying
Takes messy ticket threads — multiple back-and-forth messages, emotional context, technical details — and distill them into a summary that lets the next person pick up the case immediately without…
Doesn't just reformat questions; it identifies the patterns, group by intent, write answers that resolve the issue, and structure the whole FAQ for findability
Writes responses that resolve the situation professionally — whether that means granting the refund gracefully, offering an alternative, or declining while preserving the relationship
Takes a product or service, identify the 10 most common support scenarios, and create templated response frameworks for each
Doesn't just answer the question — it reads the emotional temperature of the message, match the appropriate escalation level, resolve the issue clearly, and leave the customer feeling heard and helped
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles