BuildBetter Customer Voice

Use BuildBetter as an evidence layer. Separate direct customer statements from internal interpretations, and preserve enough scope and identifiers for another researcher to reproduce the result.

This skill composes the general-purpose read tools shipped on the current MCP surface. It does not replace MCP behavior, encode a tenant's taxonomy, or depend on feature-gated domains and mutation workflows.

Use buildbetter-mcp-research instead when the request primarily concerns internal documents, Projects Hub, or triage rather than customer evidence.

Evidence Standard

Rank evidence in this order:

1. Transcript text from an identified external speaker.
2. A signal's exactQuote with an external person boundary and unambiguous speaker attribution.
3. A signal summary, clearly labeled as a paraphrase.
4. Internal commentary, clearly separated as context rather than customer voice.

Never turn a summary into a quotation. If identity, boundary, or speaker attribution is missing, mark the evidence unverified and do not silently count it as direct customer voice.