AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Support Signal

skill-etrebels-claude-code-growth-os-support-signal · by etrebels

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.

↗ Website ↗ Repository
— No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-etrebels-claude-code-growth-os-support-signal

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-etrebels-claude-code-growth-os-support-signal)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Support Signal? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Hand the top themes to product-signal. Emit each as a line it can triage into ops/roadmap-signals.md — FEATURE-REQUEST or adoption-friction, with the account tie — so the clustering and the routing compose into one loop (handoff H4 in [docs/operating-model.md](../../../docs/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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills