customer-discovery

Find where potential customers discuss problems online and extract their language patterns. Provides starting points for community research, not exhaustive coverage.

16 stars

Best use case

customer-discovery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Find where potential customers discuss problems online and extract their language patterns. Provides starting points for community research, not exhaustive coverage.

Teams using customer-discovery should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/customer-discovery/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/product/customer-discovery/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/customer-discovery/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How customer-discovery Compares

Feature / Agentcustomer-discoveryStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Find where potential customers discuss problems online and extract their language patterns. Provides starting points for community research, not exhaustive coverage.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Customer Discovery

You help find where potential customers discuss problems online and extract their language patterns.

## Honest Limitations

**What you CAN do:**
- Search for communities discussing specific problems
- Find example discussions and pain points
- Extract language patterns from available sources
- Suggest platforms and search strategies

**What you CANNOT do:**
- Guarantee comprehensive coverage (web search has limits)
- Provide exact member counts or activity metrics
- Extract 50+ quotes from a single search
- Replace manual community research

Always caveat that results are a starting point, not exhaustive research.

## Process

1. **Clarify the problem space**
   - What problem does their product solve?
   - Who specifically are they trying to reach?
   - What solutions do these people currently use?

2. **Search for communities**
   - Use targeted searches: `[problem] site:reddit.com`, `[problem] forum`, etc.
   - Look for: subreddits, Facebook groups, Discord servers, forums, review sites
   - Note: You'll find some, not all. Be honest about coverage.

3. **Extract pain points**
   - From available discussions, pull actual quotes
   - Identify recurring themes and emotional language
   - Note what's missing from current solutions

4. **Deliver realistic output**

## Output Format

```
## Customer Discovery: [Problem Space]

### Communities Found
For each community discovered:
- **Platform**: [Reddit/Facebook/Forum/etc]
- **Name**: [Community name with link if available]
- **Why relevant**: [What discussions happen here]
- **Sample discussions**: [1-2 example threads/posts found]

### Pain Points Observed
From the discussions found:
1. **[Pain point]**: "[Actual quote if found]"
   - Frequency: [Common/mentioned/rare]
   - Emotional intensity: [Frustrated/annoyed/desperate]

### Language Patterns
Phrases people use to describe this problem:
- "[exact phrase]" → means [interpretation]

### Current Solutions & Gaps
What they're doing now and why it's not working.

### Recommended Next Steps
Manual research suggestions to expand on these findings:
- Specific communities to join and monitor
- Search queries to run
- Questions to ask in these communities

### Limitations
What this research did NOT cover and why manual follow-up matters.
```

## Key Principles

1. **Underpromise, overdeliver** - Better to find 3 real communities than fabricate 20
2. **Show your work** - Include actual links and quotes when found
3. **Acknowledge gaps** - Be explicit about what you couldn't find
4. **Enable manual follow-up** - Give them tools to continue research themselves

Related Skills

code-discovery

16
from diegosouzapw/awesome-omni-skill

Helpers to discover, rank, and invoke repository symbols from natural language with minimal context.

blueprint-discovery

16
from diegosouzapw/awesome-omni-skill

Discovery phase for blueprint workflow - interview triggers, acceptance criteria, and feature classification

ae-sdd-discovery

16
from diegosouzapw/awesome-omni-skill

Discover high-level architectural requirements for change-set specs

api-documentation-discovery

16
from diegosouzapw/awesome-omni-skill

Use when APIs fail repeatedly with version-related errors (method not found, wrong arguments, unknown flag) or when about to use library APIs with uncertain knowledge - guides finding current, accurate documentation instead of guessing from training data

guid-universal-technology-discovery

16
from diegosouzapw/awesome-omni-skill

Discover and identify any technology, framework, or system without prior knowledge. Analyzes files, configurations, dependencies, and usage patterns to understand project technology stack from C source files to Kubernetes manifests.

skills-discovery

16
from diegosouzapw/awesome-omni-skill

Search for and install Agent Skills that give you specialized capabilities. Before starting work, ask might a skill exist that handles this better than my base knowledge? If the task involves specific technologies, frameworks, file formats, or expert domains. Search proactively, even if the user doesn't mention skills. Skills encode best practices, tools, and techniques you wouldn't otherwise have. Also use when users explicitly ask to find, install, or manage skills.

project-context-discovery

16
from diegosouzapw/awesome-omni-skill

Discover project structure, package managers, test frameworks, and automation without hardcoded assumptions

discovery-interview

16
from diegosouzapw/awesome-omni-skill

Deep interview process to transform vague ideas into detailed specs. Works for technical and non-technical users.

De-novo-motif-discovery

16
from diegosouzapw/awesome-omni-skill

This skill identifies novel transcription factor binding motifs in the promoter regions of genes, or directly from genomic regions of interest such as ChIP-seq peaks, ATAC-seq accessible sites, or differentially acessible regions. It employs HOMER (Hypergeometric Optimization of Motif Enrichment) to detect both known and previously uncharacterized sequence motifs enriched within the supplied genomic intervals. Use the skill when you need to uncover sequence motifs enriched or want to know which TFs might regulate the target regions.

customer-meeting-intelligence

16
from diegosouzapw/awesome-omni-skill

Comprehensive meeting intelligence system for customer-facing calls. Provides proactive pre-call briefings with account context, post-meeting action item extraction with draft approval, and thread continuity. Use when you need: (1) automated morning briefings for customer meetings, (2) post-meeting action item extraction from Fellow.ai and Gmail Gemini notes, (3) draft approval workflow before posting meeting notes, (4) customer context gathering including billing, support tickets, and communication history, (5) meeting follow-up automation with account intelligence.

architecture-discovery

16
from diegosouzapw/awesome-omni-skill

Guide users through discovering and defining system architecture through structured conversation. Triggers on "I want to build", "design a system", "architect", "planning a new project", "how should I build X".

architectural-pattern-discovery

16
from diegosouzapw/awesome-omni-skill

Discovers architectural and design patterns across all abstraction levels. Analyzes structural patterns, component relationships, recurring solution approaches, and design principles. Works with any technology stack without prior framework knowledge to provide comprehensive pattern understanding from code-level to system-level architecture.