What is voc-source-chat?

A customer-feedback collector for internal team chat, such as Slack, Discord, or Teams. It finds real customer quotes among messages, keeps attribution, and saves standardized feedback files for the pipeline.

It helps collect quotes from configured channels covering wins, churn risks, feature requests, sales questions, and similar topics. It requires a chat MCP server and channel configuration.

It prevents useful customer comments pasted into internal channels from being lost among ordinary team conversation and reactions.

voc-source-chat — Skill for Claude Code by aatirar/voc-claude-skills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add aatirar/voc-claude-skills --skill voc-source-chat

Clone the repo

git clone --depth 1 https://github.com/aatirar/voc-claude-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-source-chat/github.svg)](https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-source-chat)

Your own site

<a href="https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-source-chat"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-source-chat/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-source-chat"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-source-chat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,242 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00070	$0.01242
Opus 5.5	$0.00028	$0.00497
Sonnet 5.5	$0.00014	$0.00248
Haiku 4.5	$0.00007	$0.00124

Measured 2mo ago against content hash a67c994499ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

voc-source-chat scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/voc-source-chat/SKILL.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/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:

Add your chat MCP server to .mcp.json (see .mcp.json.example)
Run /mcp in Claude Code to list the tool names your server actually exposes
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:

chat_channels:
  - name: "#wins"
    signal_type: praise
    reliability: high
  - name: "#sales-questions"
    signal_type: objection
    reliability: medium

If unconfigured, ask which channels carry customer quotes. Do not scan every channel — most chat volume is internal coordination and scanning it wastes tokens and buries the signal.

Step 2 — Pull the window

Read messages from the configured window. Include thread replies: the quote is often in the parent and the crucial context in a reply three deep.

Step 3 — Separate quote from relay

This is the work, and it is where naive implementations fail. Chat contains three things:

Type	Example	Keep?
Direct quote	`Customer said: "we can't get the data out fast enough"`	Yes, verbatim
Paraphrase	`Northwind is frustrated with export speed`	Yes, but mark `paraphrased: true`
Internal chatter	`has anyone seen the deck for tomorrow`	No

Read the full file on GitHub · 132 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 132 lines · 70 tokens per session scan A a67c994499ca

Subscribe to this mod's changes

voc-source-chat is a skill published in the GitHub repository aatirar/voc-claude-skills (0 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 1,242 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Research ai-agents b2b-saas claude-skills customer-research gong

voc-source-chat next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
voc-source-chataatirar/voc-claude-skills	Skill	0	2mo ago	MIT	A	70	Claude Code
bdr-enablement-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	131	Claude Code, Codex
competitive-battlecard-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	153	Claude Code, Codex
marketing-ops-sop-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	160	Claude Code, Codex
abm-program-orchestratorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	148	Claude Code, Codex
ceo-monthly-revenue-report-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	121	Claude Code, Codex
account-research-brief-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	122	Claude Code, Codex