Goose Skills is a library of workflows and data APIs that lets coding agents handle growth and go-to-market work such as advertising, social media, content, SEO, lead generation, and customer research. It is intended for teams using Claude Code, Cursor, Codex, and similar agents. The catalogue entries are its reusable skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add gooseworks-ai/goose-skills --skill help-center-article-generatorgit clone --depth 1 https://github.com/gooseworks-ai/goose-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gooseworks-ai/goose-skills/help-center-article-generator)<a href="https://agentmods.dev/skills/gooseworks-ai/goose-skills/help-center-article-generator"><img src="https://agentmods.dev/badge/skills/gooseworks-ai/goose-skills/help-center-article-generator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gooseworks-ai/goose-skills/help-center-article-generator"><img src="https://agentmods.dev/badge/skills/gooseworks-ai/goose-skills/help-center-article-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.02080 |
| Opus 5 | $0.00028 | $0.01040 |
| Sonnet 5 | $0.00011 | $0.00416 |
| Haiku 4.5 | $0.00006 | $0.00208 |
Grade A, and why
help-center-article-generator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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)
- Support ticket export — CSV/list of recent tickets (subject, description, resolution). The skill will cluster them to find the top recurring topics.
- FAQ list — Already know the top questions? Provide them directly.
- Feature documentation — Internal docs, PRDs, or specs for features that need customer-facing articles.
- Product walkthrough — Describe the workflow step-by-step and the skill generates the article.
- Existing articles to improve — URLs or text of current help articles that need rewriting.
Configuration
- Product name — What's the product called?
- Audience — Who reads these? (Technical users, non-technical, mixed)
- Tone — Casual/friendly, professional, technical/developer-docs?
- Article structure preference:
- Standard — Overview → Steps → Troubleshooting → Related
- Developer — Overview → API reference → Code examples → Errors
- Quick start — What → Why → How (3 steps max) → Next
- Screenshot convention — Do you use screenshots? (The skill will insert
[Screenshot: description]placeholders) - 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:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 318 lines · 57 tokens per session scan A b8b1db33e60d
help-center-article-generator is a skill published in the GitHub repository gooseworks-ai/goose-skills (1,202 stars, last pushed 11d ago), licensed MIT. It adds 57 tokens to every session and 2,080 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
mass-ulw
Drives dependency-ordered child work through the native workflow tool, one run per phase with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only.…
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
trace
Read or explicitly record project progress using the existing deterministic trace script.
Article Repurposer
Takes a long-form article and repurposes it into multiple formats: tweet thread, LinkedIn post, TL;DR, and key quotes.