本文へ移動
cccskills
無料GitHub で公開

customer-research

Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Use this when the customer is being guessed at, before positioning or a major launch, when churn or conversion has an unexplained cause, or when a team is arguing from anecdotes. Also use to turn raw interview notes into usable findings.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.6 KB
  • references/sources.md957 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Customer research

Research earns its cost only if a decision hangs on it. Name that decision before recruiting anyone.

Choose the method by question

  • Why did this happen / what do they actually do — interviews. Small n, deep.
  • How common is this — survey. Only after interviews have told you what to ask; a survey written from assumptions returns your assumptions.
  • Why did we win or lose — win-loss, with losses weighted higher. Losses are where the truth is and are systematically under-sampled.
  • Which framing works — message testing against a real choice, not a preference rating.

Interviewing

Ask about the past, not the future. "What did you do last time" is evidence; "would you use this" is politeness.

  • Open broad, follow the energy, and go quiet after their first answer — the second one is where the substance is.
  • Chase specifics: when, what happened next, what did that cost you, who else was involved.
  • Never describe your solution before you have their problem in their words. Once they know what you want to hear, the interview is over.
  • Watch for the workaround. Anything someone has built a spreadsheet to survive is a validated problem.

Synthesizing

Code the transcripts before forming a view — findings assembled to support an existing belief will be. For each finding record: the claim, how many independently said it, a verbatim quote, and what would change if it is true. A finding that changes nothing is trivia.

Separate what people said, what they did, and what you inferred. Conflating the three is the most common way research misleads.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Recruit only happy customers. The sample that answers your email is not your market.
  • Lead: "How much would this feature help?" has one answer.
  • Present a single interview as a finding.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する