voc-source-chatlisted

# /voc-source-chat — Mine Internal Chat for Customer Voice Your team already does VoC work. They paste customer quotes into channels named things like `#wins`, `#churn-risk`, `#feature-requests` and `#sales-questions`, where the quote gets four emoji reactions and is never seen again. This is the highest-yield source per unit of setup effort in the whole pipeline, and it is the one every VoC tool ignores because it is not a customer-facing system. ## Requires | What | Value | |---|---| | Chat MCP server | Slack, Discord, Teams — whatever your team uses | | Config | `context/product-context.md` → `chat_channels` | | Cost | Free. | ### Wiring the tools **This skill deliberately does not hardcode chat MCP tool names.** They vary by server, and a skill that declares a tool name your server does not expose fails at its first step while looking like it ran. To connect yours: 1. Add your chat MCP server to `.mcp.json` (see `.mcp.json.example`) 2. Run `/mcp` in Claude Code to list the tool names your server actually exposes 3. Add those names to this file's `allowed-tools` If you skip step 2 and guess, you will get a skill that reads no messages and reports no error. --- ## Execution ### Step 1 — Resolve channels Read `chat_channels` from your context file. Each entry: ```yaml chat_channels: - name: "#wins" signal_type: praise reliability: high - name: "#sales-questions" signal_type: objection reliability: medium ``` If unconfigured, ask which chann