synthesize-customer-research

Installation
SKILL.md

Synthesize Customer Research

Contract

Read the full evidence set before naming themes. Preserve the chain from source to evidence unit to pattern to insight to recommendation. Do not present a model summary as a customer quote.

Workflow

  1. Define the research question, decision, included sources, date range, segments, and exclusions.
  2. Normalize atomic evidence units with source ID, speaker or respondent, date, segment, text or observation, and evidence type.
  3. Tag without forcing consensus. Keep contradictory and negative cases visible.
  4. Cluster by shared job, barrier, trigger, behavior, or outcome rather than vocabulary alone.
  5. Write findings as claims. For each, attach supporting units, counterevidence, prevalence within the sample, and confidence.
  6. Derive implications and recommendations separately. Mark which recommendations are decisions, experiments, or follow-up questions.
  7. Check whether one account, researcher, source type, or prompt dominates the result.

BuildBetter Acceleration

If BuildBetter MCP is available, search organization skills first. Retrieve stable evidence pages from calls, transcripts, signals or extractions, survey responses, documents, and people. Record returned IDs and filters. Use aggregates for counts and row-level tools for representative evidence; do not infer coverage from one result page.

Installs
1
GitHub Stars
4
First Seen
Oct 27, 2026