customer-research

customer-research is a skill for Claude Code, Codex from Global-mindee/WAY. It costs 181 tokens per session (2,610 once invoked), scanned A, a copy of customer-research, MIT.

A guide for collecting and analyzing what customers say, do, and struggle with. Customer research can include interviews, surveys, support requests, reviews, and other feedback used to understand customer needs.

In plain words
What is it for?
Use it to analyze interview transcripts, surveys, support tickets, reviews, customer personas, and ideal-customer research.
Why use it?
It helps replace guesses about customers with evidence from their own words and experiences. This can reveal problems, buying triggers, objections, and the outcomes people want.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to analyze interview transcripts, surveys, support tickets, reviews, customer personas, and ideal-customer research.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/global-mindee/way/customer-research
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 Global-mindee/WAY --skill customer-research
Clone the repo
git clone --depth 1 https://github.com/Global-mindee/WAY

Made for: Claude Code, Codex.

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.

agentmods badge for customer-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/global-mindee/way/customer-research/github.svg)](https://agentmods.dev/skills/global-mindee/way/customer-research)
Your own site
<a href="https://agentmods.dev/skills/global-mindee/way/customer-research"><img src="https://agentmods.dev/badge/skills/global-mindee/way/customer-research/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.

agentmods 80×15 button for customer-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/global-mindee/way/customer-research"><img src="https://agentmods.dev/badge/skills/global-mindee/way/customer-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 181 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,610 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 89% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00181 $0.02610
Opus 5.5 $0.00072 $0.01044
Sonnet 5.5 $0.00036 $0.00522
Haiku 4.5 $0.00018 $0.00261

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

Security

Grade A, and why

customer-research 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 1mo 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.

Origin

This is a copy

89% identical to customer-research — 60 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/03_business/customer-research/SKILL.md · 271 lines

How it starts

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

Customer Research

You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with — so that everything from positioning to product to copy is grounded in reality rather than assumption.

Before Starting

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context to skip questions already answered.


Two Modes of Research

Mode 1: Analyze Existing Assets

You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal.

Mode 2: Go Find Research

You need to gather intel from online sources (Reddit, G2, forums, communities, review sites). Your job is to know where to look and what to extract.

Most engagements combine both. Establish which mode applies before proceeding.


Mode 1: Analyzing Existing Research Assets

Asset Types

Customer interview / sales call transcripts

  • Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered
  • Look for: the moment they decided to look for a solution, what they tried before, what success looks like to them

Survey results

  • Segment responses by customer tier, use case, or tenure before drawing conclusions
  • Flag: what open-ended answers say vs. what multiple-choice answers say (they often conflict)
  • Identify: the 20% of responses that contain the most useful signal

Customer support conversations

  • Mine for: recurring complaints, confusion points, feature requests, and "I wish it could…" language
  • Categorize tickets before analyzing — don't treat all tickets as equal signal
  • Separate bugs from confusion from missing features from expectation mismatches

Win/loss interviews and churned customer notes

  • Wins: what tipped the decision? What almost made them choose a competitor?
  • Losses and churn: was it price, features, fit, timing, or something else?
  • Segment by reason — don't average across different churn causes

Read the full file on GitHub · 271 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 1mo ago First seen · 271 lines · 181 tokens per session scan A 446eceb7c537

Subscribe to this mod's changes

customer-research is a skill published in the GitHub repository Global-mindee/WAY (11 stars, last pushed 1mo ago), licensed MIT. It adds 181 tokens to every session and 2,610 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to customer-research, differing in 60 lines, and is treated as a copy.

Related

Other skills, from other repositories

Research

Multi-agent web research with verified URLs and confidence-tagged output at four depths. USE WHEN research, do research, quick research, extensive research, deep investigation, find information, investigate, extract alpha, analyze content, retrieve content, AI trends, enhance content, extract knowledge, web scraping…

danielmiessler/LifeOS · 200 tokens

ExtractWisdom

Content-adaptive wisdom extraction (sections built around what the content holds, five depth levels, mandatory contrarian takes) and extract alpha (the N highest-alpha, net-new ideas as short ranked bullets) from videos, podcasts, articles, files or text, from the full source. USE WHEN extract wisdom, ew, extract…

danielmiessler/LifeOS · 123 tokens

Migrate

Intakes external content (notes, CLAUDE.md, Cursor rules, Obsidian/Notion/Apple Notes exports), classifies chunks against the LifeOS taxonomy, and commits with provenance after confidence-tiered approval. USE WHEN /migrate, migrate content, import from other LifeOS, bring in old notes, import Cursor rules, import…

danielmiessler/LifeOS · 104 tokens

Prompting

Meta-prompting standard library for generating, optimizing, and composing prompts programmatically via Standards, Handlebars Templates, and Tools; output is always a prompt to use elsewhere, not final content. USE WHEN meta-prompting, template generation, prompt optimization, prompt engineering, write a prompt, create…

danielmiessler/LifeOS · 111 tokens

WriteStory

Scaffolds a story the writer already wants to tell, deriving structure, wound, theme, and prose from their own notes across seven narrative layers, short story to series. USE WHEN write story, fiction, novel, chapter, story bible, character arc, plot outline, creative writing, worldbuilding, draft story, help me write…

danielmiessler/LifeOS · 111 tokens

ApertureOscillation

3-pass scope oscillation that holds a question constant while shifting zoom — narrow/tactical, wide/strategic, then synthesis — to surface design tensions, scope recommendations, and coherence assessments invisible at any single zoom level. USE WHEN aperture oscillation, oscillate scope, zoom in and out, tactical vs…

danielmiessler/LifeOS · 102 tokens