feedback

Analyze Slack feedback and generate structured bug reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill feedback-taptap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/test/skills/feedback
Command: npx skills add https://github.com/taptap/agents-plugins --skill feedback-taptap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aiohttp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill analyzes Slack messages from the #taptap-feedback channel to quickly identify feedback that may require a bug, and it guides rapid response by generating structured analysis reports and bug tickets when appropriate.

Core Features & Use Cases

  • Slack feedback analysis: extracts key details (user, device, app version, and content) and classifies issue types.
  • Knowledge-base guidance: consults knowledge-base entries to surface historical cases and owner mappings.
  • Bug workflow automation: prepares bug tickets, assigns responsible teams, and outputs a ready-to-share summary for Slack.

Quick Start

Analyze the latest feedback in the #taptap-feedback channel.

Frequently Asked Questions about feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Slack feedback analysis to identify bugs?

Automate Slack feedback analysis by extracting key details like user, device, and app version from messages, classifying issue types, and applying knowledge-base lookups to determine if bug creation is needed. This process generates structured analysis reports and suggests next actions with assignee mapping.

Can I automatically generate bug tickets from Slack channel messages?

Yes, you can generate bug tickets from Slack messages by applying a deterministic workflow that uses Slack APIs and local mappings. The process evaluates extracted feedback signals, checks knowledge-base historical cases, and outputs a ready-to-share summary and an optional bug creation payload for downstream systems.

What is the best way to map Slack feedback to responsible teams for bug triage?

Mapping Slack feedback to responsible teams is achieved through local assignee mappings combined with knowledge-base lookups. The workflow extracts key signals from feedback, surfaces historical owner mappings, and suggests next actions to ensure the generated bug ticket is assigned to the correct team.

Does this bug triage workflow require a specific Slack API setup?

The workflow relies on Slack APIs to extract feedback messages and device details from the channel. It also requires local mappings for assignee routing and a knowledge-base to surface historical cases, ensuring the generated analysis and bug creation payload are accurate.

How to extract app version and device info from Slack feedback for triage?

Extracting app version and device info from Slack feedback uses Slack APIs to parse message content within the channel. The workflow isolates these key details, classifies the issue type, and prepares the data for knowledge-base lookup and subsequent bug creation.