agentsclimarketplace
Sign in

Triage feedback loop

Skill alexe-ev/product-plugins/customer-success/skills/triage-feedback-loop

Establish a feedback intake and triage system that routes insights to the right product teams. Use this skill when a team needs a reliable system for processing incoming customer feedback.From its SKILL.md

Install
npx -y skills add alexe-ev/product-plugins --skill triage-feedback-loop

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 448 tokens by cl100k_base, as published. Nobody here has run it

Triage Feedback Loop

Purpose

Help teams design a structured feedback intake and triage system that ensures insights reach the right people and inform product decisions without creating noise.

Skill type

Conceptual skill

Use this skill when

  • Feedback is arriving from multiple channels without a clear routing process
  • Product teams are overwhelmed by raw feedback volume
  • High-signal feedback is getting lost in the noise
  • CS and support are not effectively passing feedback to product

Do not use this skill when

  • The goal is designing the full VoC program (use run-voc-program)
  • The goal is analyzing churn (use analyze-churn-retention)

Required inputs

  • Current feedback sources and volume (rough)
  • Teams involved in receiving and acting on feedback

Optional inputs

  • Current triage process (if any)
  • CRM or support tooling
  • Feedback tagging taxonomy

Upstream context

Works best when:

  • VoC program exists or is being designed
  • Product team structure is known

Downstream handoff

Output can feed:

  • synthesize-qualitative-research (triaged feedback is synthesized into insights)
  • identify-problem-opportunity (feedback themes become product problems)

Instructions

  1. Map all incoming feedback sources and their volume.
  2. Define a tagging taxonomy (product area, type, urgency, segment).
  3. Design the triage process: who reviews, how often, what criteria.
  4. Define routing rules: which feedback goes to which team.
  5. Define escalation for urgent or high-impact feedback.
  6. Design the feedback-to-action loop: how does feedback become a product decision?

Output

Provide:

  • Feedback source map with volume estimates
  • Tagging taxonomy
  • Triage process design (who, how often, criteria)
  • Routing rules by team
  • Escalation process
  • Feedback-to-action loop
  • Tooling requirements

Risks / caveats

  • Feedback that is collected but not routed creates the illusion of listening
  • Triage must be fast — delayed triage creates backlogs that are never cleared
  • Edge case feedback (one angry customer) must be distinguished from systematic signals

What ships with it: 4 files

7.8 KB alongside SKILL.md

examples/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.