What is voc-orchestrator?

A coordinator for running a full Voice of Customer (VoC) process, which collects and studies what customers say about a product. It runs the configured stages in order, from gathering sources through creating usable drafts.

It helps run a recurring customer-intelligence review using calls, chat, notes, and other configured sources. A dry run can collect, analyze, and summarize feedback without routing it or creating final drafts.

It removes the need to run each research step manually and makes setup problems visible before processing starts. It can also limit the date range, skip selected sources, or stop before later stages.

voc-orchestrator — 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-orchestrator

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-orchestrator/github.svg)](https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-orchestrator)

Your own site

<a href="https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-orchestrator"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-orchestrator/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-orchestrator"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,300 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.00067	$0.01300
Opus 5.5	$0.00027	$0.00520
Sonnet 5.5	$0.00013	$0.00260
Haiku 4.5	$0.00007	$0.00130

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

Security

Grade A, and why

voc-orchestrator 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-orchestrator/SKILL.md · 142 lines

How it starts

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

/voc-orchestrator — The Weekly Run

One command, six phases. The intelligence lives in the individual skills; this is a coordinator that runs them in order and fails loudly instead of quietly.

Arguments

Flag	Effect
`--window 30d`	Override the default window
`--skip-sources chat,notes`	Skip named sources
`--dry-run`	Pull, analyze and synthesize, but do not route or dispatch
`--sources-only`	Stop after Phase 1

Use --dry-run for your first three runs. Read the synthesis by hand and check whether the confirmed themes match what you already believe from talking to customers. If they do not, the problem is almost always upstream configuration, not the rule.

Phase 0 — Preflight

Before pulling anything, verify the setup and print the result as a table. Do not proceed silently past a broken connector.

Preflight
  config/thresholds.json        ok
  context/product-context.md    ok
  CALL_PROVIDER=gong            credentials present
  Apify MCP                     connected
  CRM MCP                       NOT CONNECTED — signals will be tier U
  chat_channels                 3 configured
  notes_source                  not configured — skipping
  VOC_OUTPUT_DIR=./outputs      local, not synced   ok

Check VOC_OUTPUT_DIR for the strings Dropbox, Google Drive, OneDrive, iCloud. If it is inside a synced folder, warn before writing anything. This pipeline writes customer conversations to disk.

If fewer than confirmation.min_independent_sources sources are configured, say plainly that nothing can reach high confidence this run, and suggest either connecting more sources or lowering the threshold deliberately in the config.

Phase 1 — Pull sources

Run in parallel where the connectors are independent:

Order	Skill
1	`/voc-source-calls`
2	`/voc-source-reviews` — cost guard: this one spends money. Skip on weekly runs; monthly is enough. Reviews do not change fast.
3	`/voc-source-chat`
4	`/voc-source-notes`
5	`/voc-source-custom` for each registered custom source

Read the full file on GitHub · 142 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 · 142 lines · 67 tokens per session scan A a4ab0462683f

Subscribe to this mod's changes

voc-orchestrator is a skill published in the GitHub repository aatirar/voc-claude-skills (0 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 1,300 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.

Analytics and metrics Claude Code Marketing and SEO ai-agents b2b-saas claude-skills customer-research gong

voc-orchestrator next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
voc-orchestratoraatirar/voc-claude-skills	Skill	0	2mo ago	MIT	A	67	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