Agent skill

Help Center Article Generator

by gooseworks-ai in gooseworks-ai/goose-skills

Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders…

MITAuto-check passedSales & Support

Install Help Center Article Generator

skills CLI
$ npx skills add gooseworks-ai/goose-skills --skill help-center-article-generator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gooseworks-ai/goose-skills help-center-article-generator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content/composites/help-center-article-generator .claude/skills/help-center-article-generator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
help-center-article-generator
GitHub stars
1.2k
Used in
1 other repo
Token cost
~2.1k tokens
SKILL.md length
556 words
Files
2
Skills in repo
273
Repo updated
First seen
Licence
MIT

At a glance

Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders…

  • Works in 5 steps: Intake → Topic Clustering (Batch Mode) → Article Generation → …
  • Tasks that involve Help center and FAQ content
  • SKILL.md covers When to Use, Phase 0: Intake, Phase 1: Topic Clustering… and Phase 2: Article Generation, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Help Center Article Generator is an agent skill from gooseworks-ai/goose-skills. Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders, troubleshooting sections, and related article links. Batch mode generates multiple articles from a ticket export. Pure reasoning skill.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).

It sits in Sales & Support, covering Help center and FAQ content and Customer support. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.

When your agent uses it

  • Tasks that involve Help center and FAQ content
  • Tasks that involve Customer support

Example prompts

  • “/help-center-article-generator”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Intake
  2. Topic Clustering (Batch Mode)
  3. Article Generation
  4. Article Quality Check
  5. Output

What it can do on your machine

Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Help Center Article Generator loads about 2.1k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 556 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 556 words, ~2,137 tokens.

Download SKILL.mdSave it as .claude/skills/help-center-article-generator/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
help-center-article-generator
description
Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders, troubleshooting sections, and related article links. Batch mode generates multiple articles from a ticket export. Pure reasoning skill.
tags
content

Help Center Article Generator

Turn support tickets into self-serve answers. Takes repeated questions, feature docs, or product specs and generates help center articles that reduce ticket volume.

Built for: Early-stage teams where the same 20 questions make up 80% of support tickets, and nobody has time to write help docs. The goal is to turn one afternoon of article generation into months of ticket deflection.

When to Use

  • "Write help center articles for our top support questions"
  • "Turn these support tickets into FAQ articles"
  • "Generate docs for [feature]"
  • "Build out our knowledge base"
  • "Our support volume is too high — help me create self-serve content"

Phase 0: Intake

Content Source (provide any/all)
  1. Support ticket export — CSV/list of recent tickets (subject, description, resolution). The skill will cluster them to find the top recurring topics.
  2. FAQ list — Already know the top questions? Provide them directly.
  3. Feature documentation — Internal docs, PRDs, or specs for features that need customer-facing articles.
  4. Product walkthrough — Describe the workflow step-by-step and the skill generates the article.
  5. Existing articles to improve — URLs or text of current help articles that need rewriting.
Configuration
  1. Product name — What's the product called?
  2. Audience — Who reads these? (Technical users, non-technical, mixed)
  3. Tone — Casual/friendly, professional, technical/developer-docs?
  4. Article structure preference:
    • Standard — Overview → Steps → Troubleshooting → Related
    • Developer — Overview → API reference → Code examples → Errors
    • Quick start — What → Why → How (3 steps max) → Next
  5. Screenshot convention — Do you use screenshots? (The skill will insert [Screenshot: description] placeholders)
  6. Batch or single? — One article or generate multiple from a ticket export?

Phase 1: Topic Clustering (Batch Mode)

If provided a ticket export, cluster tickets into article topics:

Clustering Approach
  1. Group by similarity — Cluster tickets with similar subject/description
  2. Rank by frequency — Most common clusters = highest priority articles
  3. Identify article type per cluster:
TypeWhen to UseExample
How-to"How do I do X?""How to set up email integration"
Troubleshooting"X isn't working""Fix: emails not sending"
Concept/Overview"What is X?""Understanding billing plans"
Reference"What are the options for X?""API rate limits and quotas"
Getting StartedFirst-time setup"Quick start: your first campaign"
Show full SKILL.md (200 more words)Show less
Cluster Output
TOPIC CLUSTERS (ranked by ticket frequency):

1. [Topic] — [N tickets] — Type: [How-to]
   Common phrasing: "[How customers ask this question]"
   Resolution pattern: [What support typically tells them]

2. [Topic] — [N tickets] — Type: [Troubleshooting]
   ...

3. ...

Phase 2: Article Generation

Article Template — How-to
markdown
# [Action-oriented title — e.g., "How to Set Up Email Integration"]

[1-2 sentence overview: What this article covers and who it's for]

**Time to complete:** [X minutes]
**Prerequisites:** [What they need before starting — e.g., "Admin access, API key"]

---

## Step 1: [Action verb + what to do]

[1-2 sentences explaining this step]

[Screenshot: Description of what the user should see — e.g., "Settings page with Integrations tab highlighted"]

> **Tip:** [Helpful context or shortcut]

## Step 2: [Action verb + what to do]

[Instructions]

[Screenshot: Description]

## Step 3: [Action verb + what to do]

[Instructions]

---

## Verify It Worked

[How to confirm the setup was successful]

[Screenshot: Description of success state]

---

## Troubleshooting

### [Common problem 1]
**Symptom:** [What the user sees]
**Cause:** [Why this happens]
**Fix:** [Step-by-step resolution]

### [Common problem 2]
**Symptom:** [...]
**Cause:** [...]
**Fix:** [...]

---

## FAQ

**Q: [Common follow-up question]**
A: [Answer]

**Q: [Another common question]**
A: [Answer]

---

## Related Articles

- [[Article title]] — [1-line description of when to read it]
- [[Article title]] — [...]
Article Template — Troubleshooting
markdown
# Fix: [Problem description — e.g., "Emails Not Sending"]

[1-2 sentences: When you'd encounter this problem]

---

## Quick Fix

Try this first (resolves ~80% of cases):

1. [Most common fix — step 1]
2. [Step 2]
3. [Verify]

---

## If That Didn't Work

### Check 1: [First thing to verify]
[How to check + what to look for]

✅ If [expected result] → This isn't the issue. Move to Check 2.
❌ If [unexpected result] → [Specific fix for this case]

### Check 2: [Second thing to verify]
[How to check]

✅ If OK → Move to Check 3.
❌ If not → [Fix]

### Check 3: [Third thing to verify]
[How to check]

✅ If OK → Move to "Still Not Working?"
❌ If not → [Fix]

---

## Still Not Working?

If none of the above resolved your issue:

1. [What information to gather — e.g., "Screenshot of the error message"]
2. [Where to get help — e.g., "Email support@company.com with the above info"]
3. [Expected response time]

---

## Why This Happens

[2-3 sentences explaining the root cause for curious users. Optional but builds trust.]

## Related Articles

- [[Article]] — [Context]
Article Template — Getting Started / Quick Start
markdown
# Getting Started with [Feature/Product]

[1-sentence: What you'll accomplish by the end of this guide]

**Time:** [X minutes] | **Difficulty:** [Beginner/Intermediate]

---

## What You'll Need

- [Prerequisite 1]
- [Prerequisite 2]

---

## Step 1: [First thing to do] (2 min)

[Clear instructions]

[Screenshot: Description]

## Step 2: [Second thing] (3 min)

[Instructions]

## Step 3: [Third thing] (2 min)

[Instructions]

---

## You're All Set! 🎉

[What they can now do]

**Next steps:**
- [Logical next action — link to next article]
- [Power user tip — link to advanced article]
- [Join community — link if applicable]

Phase 3: Article Quality Check

For each generated article, verify:

  • Title is action-oriented — Starts with "How to", "Fix:", "Getting Started", or "Understanding"
  • Scannable — Headers, numbered steps, bold key terms. No walls of text.
  • Complete — Covers the full workflow, not just the happy path
  • Troubleshooting included — At least 2 common failure scenarios
  • No jargon — Uses the customer's language, not internal terminology
  • Screenshot placeholders — Every step that involves UI has a placeholder
  • Related articles linked — Cross-references to keep users in the help center
  • Search-friendly — Title and first paragraph contain keywords customers actually search for

Phase 4: Output

Single Article Mode

Save to the current working directory as [article-slug].md.

Batch Mode

Save all articles to a help-center/ subdirectory in the current working directory, with an _index.md table of contents.

Index Template
markdown
# Help Center — [Product Name]
Generated: [DATE] | Articles: [N]

## Getting Started
- [[getting-started-guide.md]] — First-time setup walkthrough
- [[quick-start.md]] — 5-minute quick start

## How-To Guides
- [[how-to-setup-email.md]] — Set up email integration
- [[how-to-invite-team.md]] — Invite team members
- ...

## Troubleshooting
- [[fix-emails-not-sending.md]] — Emails not sending
- [[fix-login-issues.md]] — Can't log in
- ...

## Reference
- [[api-rate-limits.md]] — API limits and quotas
- [[billing-plans.md]] — Plan comparison and billing FAQ

Cost

ComponentCost
All article generationFree (LLM reasoning)
TotalFree

Tools Required

None. Pure reasoning skill — takes raw input and produces structured articles.

Trigger Phrases

  • "Write help center articles from our support tickets"
  • "Generate docs for [feature]"
  • "Build out our knowledge base"
  • "Turn our FAQs into help articles"
  • "Run help center article generator"

© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/content/composites/help-center-article-generator of gooseworks-ai/goose-skills.

  • SKILL.md
  • skill.meta.json

Open the folder on GitHubat commit c650c6d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Help Center Article Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Help Center Article Generator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Help Center Article Generator this skillgooseworks-ai/goose-skills1.2k1 repos~2.1kAutomated safety check: PassMIT
Okx Guideaiskillstore/marketplace4331 repos~835Automated safety check: PassMIT
Customer Support Customer Servicechendongqi/OPB-Skills126—~861Automated safety check: PassNone
Customer Support Technical Supportchendongqi/OPB-Skills126—~971Automated safety check: PassNone
Customer Supportericrisco/rsc-harness180—~2.9kAutomated safety check: PassMIT
Helpdesk Automationdavepoon/buildwithclaude3.6k7 repos~1.5kAutomated safety check: PassMIT

Similar skills

  • Okx Guide

    aiskillstore/marketplace

    Onchain OS onboarding and guide hub for first-time use, product introductions, OKX.AI, and customer-support intents.

    433 GitHub starsUsed in 1 repo~835 tokens
    Sales & SupportAuto-check passed
  • 客服助手 - 专业的客户服务与支持体系专家。适用场景: (1) 客服话术设计与优化 (2) FAQ知识库构建与维护 (3) 客户问题分类与处理流程 (4) 投诉处理与升级机制 (5) 客户满意度分析与改进 (6) 客服培训材料编写 (7) 自动回复与机器人话术 触发关键词:客服话术、FAQ、客户投诉、客户满意度、知识库、客服培训、自动回复、工单处理、客户咨询、售后服务

    126 GitHub stars~861 tokensUpdated 8 mo ago
    Sales & SupportAuto-check passed
  • 技术支持助手 - 专业的技术问题诊断与解决方案专家。适用场景: (1) 技术问题诊断与分析 (2) 故障排查与解决方案 (3) 技术文档编写(FAQ/手册/指南) (4) 用户操作指导与培训 (5) 技术工单处理与升级 (6) 产品使用问题解答 (7) 系统/软件问题处理 触发关键词:技术支持、故障排查、技术问题、报错、Bug、系统问题、软件问题、操作指导、技术文档、解决方案

    126 GitHub stars~971 tokensUpdated 8 mo ago
    Sales & SupportAuto-check passed
  • Customer Support

    ericrisco/rsc-harness

    A skill your agent uses when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or…

    180 GitHub stars~2.9k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Helpdesk Automation

    davepoon/buildwithclaude

    Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields.

    3.6k GitHub starsUsed in 7 repos~1.5k tokens
    Productivity & AutomationAuto-check passed
  • Siftrank

    noperator/siftrank

    Find needles in haystacks with SiftRank. An agent skill from noperator/siftrank.

    225 GitHub stars~2.9k tokensUpdated 21 days ago
    Sales & SupportAuto-check passed

More from gooseworks-ai/goose-skills

All 273 skills in this repo
  • Reddit Post Finder

    gooseworks-ai/goose-skills

    Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Create Image Fal

    gooseworks-ai/goose-skills

    Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.

    1.2k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Render Hook Replacement

    gooseworks-ai/goose-skills

    Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.

    1.2k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Blog Feed Monitor

    gooseworks-ai/goose-skills

    Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.

    1.2k GitHub starsUsed in 1 repo~578 tokens
    Auto-check passed
  • Competitor Post Engagers

    gooseworks-ai/goose-skills

    Find leads by scraping engagers from a competitor's top LinkedIn posts.

    1.2k GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check: notes
  • Render Chatgpt Chat

    gooseworks-ai/goose-skills

    Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…

    1.2k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Categories

Questions about Help Center Article Generator

What does Help Center Article Generator do?

Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders…. Help Center Article Generator is an agent skill from gooseworks-ai/goose-skills. Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders, troubleshooting sections, and related article links.

When should I use Help Center Article Generator?

Help Center Article Generator fits situations like: tasks that involve Help center and FAQ content; tasks that involve Customer support.

How do I install Help Center Article Generator in Claude Code?

Run `npx skills add gooseworks-ai/goose-skills --skill help-center-article-generator -a claude-code`. Or copy the skill folder (skills/content/composites/help-center-article-generator in gooseworks-ai/goose-skills) into .claude/skills/help-center-article-generator in your project. Claude Code loads it when a task matches its description.

How do I install Help Center Article Generator in Codex?

Run `npx skills add gooseworks-ai/goose-skills --skill help-center-article-generator -a codex`. Or copy the skill folder (skills/content/composites/help-center-article-generator in gooseworks-ai/goose-skills) into .agents/skills/help-center-article-generator in your project. Codex loads it when a task matches its description.

Can I use Help Center Article Generator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill help-center-article-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/help-center-article-generator, .gemini/skills/help-center-article-generator, .github/skills/help-center-article-generator and .opencode/skills/help-center-article-generator in your project.

What does Help Center Article Generator need to run?

SKILL.md names no scripts, command-line tools or credentials: Help Center Article Generator is instructions for the agent only.

Does Help Center Article Generator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Help Center Article Generator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Help Center Article Generator use?

Help Center Article Generator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Help Center Article Generator use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Help Center Article Generator?

Skills that share tags, products or a category with Help Center Article Generator: Okx Guide (aiskillstore/marketplace, 433 stars), Customer Support Customer Service (chendongqi/OPB-Skills, 126 stars), Customer Support Technical Support (chendongqi/OPB-Skills, 126 stars) and Customer Support (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Help Center Article Generator?

gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.

Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.