Agent skill
support-signal
Cluster a batch of support tickets or threads into ranked product themes, then hand them to product-signal for the roadmap.
Filed under Prospecting and list building and Onboarding, retention and expansion.
From etrebels/claude-code-growth-os · 20 skill entries · 21 · pushed 2026-10-03
What it does when it runs
Cluster a batch of support tickets or threads into ranked product themes, then hand them to product-signal for the roadmap. Trigger when there's a pile of support tickets, or the user says "what are the tickets telling us", "cluster these tickets", "support themes", "top issues this month", or wants raw support volume turned into product feedback.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/etrebels/claude-code-growth-os.git /tmp/claude-code-growth-os git -C /tmp/claude-code-growth-os sparse-checkout set ".claude/skills/support-signal" mkdir -p ~/.claude/skills/support-signal cp -R "/tmp/claude-code-growth-os/.claude/skills/support-signal/." ~/.claude/skills/support-signal/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from etrebels/claude-code-growth-os/blob/3e0c2d7d1fc545d35073011208d8da3f845183fb/.claude/skills/support-signal/SKILL.md, which is licensed MIT (repository). 362 words, 2 headings.
Support Signal
The front-end to product-signal. A roadmap fed by raw tickets is noise; this clusters the volume into a few ranked themes first, so what reaches product is a pattern, not a pile. It reads a batch of tickets — from a support tool over MCP, or a pasted / demo/support-tickets.md list — and emits the themes product-signal routes.
From the batch:
- Cluster by the underlying job, not the wording. Group tickets by what the customer was trying to do, not the words they used — three phrasings of "I can't get the data out" are one theme.
- Rank by frequency × severity. How many accounts raised it, and how much it hurts — is it blocking adoption or a renewal, or is it a papercut? A one-off annoyance isn't a theme; a recurring blocker is. Rank the themes; don't route a flat list.
- Split the types. Each theme is one of: adoption friction (a setup or UX gap — product), feature request (a missing capability — roadmap), bug (it's broken — engineering), or how-to (they couldn't find it — an enablement / docs gap, not a product one). The how-to pile is a signal too: it's where onboarding or the docs are failing.
- Tie themes to accounts. Name which customers each theme touches — especially any tied to a renewal or an expansion. That tie is what lifts a theme above raw count.
- Hand the top themes to
product-signal. Emit each as a line it can triage intoops/roadmap-signals.md—FEATURE-REQUESTor adoption-friction, with the account tie — so the clustering and the routing compose into one loop (handoff H4 indocs/operating-model.md).
Don't route every ticket; cluster first, route the pattern. The point is to turn volume into a short, ranked list product can actually act on.
Depth
- quick: the top 3 themes, ranked, with counts.
- standard: the full clustering above — themes ranked, typed, tied to accounts, handed to product-signal.
- deep: + the how-to / enablement split (the themes that are really a docs or onboarding gap, routed there instead) and a buyer-facing line for any theme already shipped.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- growth-signal-charts by ericosiu · 3,627
- personal-strategic-signal-intelligence by ericosiu · 3,627
- gh-issue-to-demand-signal by Varnan-Tech · 674
- support-ticket-triage by zapier · 342
- signal-monitor by janskuba · 204
- buying-signal-amplification by louisblythe · 179
- multilingual-support by louisblythe · 179
- niche-signal-discovery by getaero-io · 66
Need help setting it up?
This page tells you what support-signal does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.