voc-source-customlisted

# /voc-source-custom — Bring Your Own Source The pipeline does not care where a signal came from. It cares that the signal arrives in a known shape with honest metadata. This skill is the on-ramp for everything the dedicated source skills do not cover. Common uses: NPS and survey open-text, support tickets, CRM email threads, community and forum posts, churn exit interviews, app store reviews, sales-lost reason fields, win/loss interviews. ## Requires | What | Value | |---|---| | Access | An MCP server, an API you can call from Bash, or an export file | | Config | `context/product-context.md` → `custom_sources` | | Cost | Depends on the source. Most are free. | --- ## The contract Every signal file written anywhere under `outputs/voc/sources/` must have this shape. Get this right and everything downstream works without modification. ```json { "channel": "survey", "verbatim": "exact text as the customer wrote or said it", "fidelity": "verbatim", "company": "Northwind Trading", "speaker_role": "Operations Director", "date": "2026-04-22", "signal_type": "pain", "source_link": "https://...", "source_file": "outputs/voc/sources/survey/raw-2026-04-22.json", "notes": "NPS detractor, score 4" } ``` | Field | Rule | |---|---| | `channel` | **A new, distinct name.** This is what the confirmation rule counts. Do not reuse an existing channel name for a different source — and do not invent two names for the same source, which manufactures false corroboration.