Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Research Market Sizing Segmentation Demand

ASecurity

Research markets with sizing, segmentation, competitor mapping, pricing checks, and demand validation that turn fuzzy ideas into decision-ready evidence. Use when (1) you need TAM, SAM, SOM, whitespace, or category sizing; (2) you must compare competitors, pricing, positioning,…

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsrustgosecurity

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill research-market-sizing-segmentation-demand --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Research Market Sizing Segmentation Demand?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Research Market Sizing Segmentation Demand
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-research-market-sizing-segmentation-demand/badge)](https://www.skillsdirectory.com/skills/rondoflow-research-market-sizing-segmentation-demand)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: research-market-sizing-segmentation-demand
description: "Research markets with sizing, segmentation, competitor mapping, pricing checks, and demand validation that turn fuzzy ideas into decision-ready evidence. Use when (1) you need TAM, SAM, SOM, whitespace, or category sizing; (2) you must compare competitors, pricing, positioning,…"
category: "Community"
author: community
version: "1.0.1"
icon: puzzle
---

## When to Use

Use this skill when the user needs market evidence, not just opinions. It should activate for market sizing, opportunity validation, competitor landscape work, segment selection, pricing research, whitespace mapping, and expansion decisions.

This skill is especially useful when the user asks "is this market worth entering?", "how big is the real opportunity?", "who else is already winning here?", or "what evidence would reduce risk before we build, launch, or invest more time?"

## Quick Reference

Use the smallest relevant file for the task.

| Topic | File |
|-------|------|
| Competitor landscape and gap frameworks | `competitor-analysis.md` |
| Customer validation and pricing methods | `validation.md` |
| Evidence quality and confidence rubric | `evidence-grading.md` |

## Research Brief

Start every serious engagement with a compact brief like this:

```text
MARKET RESEARCH BRIEF
Decision:
Target customer:
Geography:
Category or substitute set:
Time horizon:
Must-answer questions:
Evidence bar:
```

If the brief is weak, the research will drift. Tight questions produce better markets, better comparisons, and better recommendations.

## Research Modes

Pick the lightest mode that still answers the decision well. Depth should follow the decision, not ego.

| Mode | Best For | Minimum Output |
|------|----------|----------------|
| **Quick scan** | Early idea filtering | Market snapshot, top competitors, 2-3 key risks |
| **Decision memo** | Founders, operators, or investors making a next-step call | Sizing view, segment map, competitor comparison, recommendation |
| **Launch validation** | New product, feature, or niche entry | Demand signals, pricing checks, interview findings, no-go risks |
| **Expansion study** | New geography, segment, or adjacent category | SAM filters, local competitors, channel constraints, rollout logic |

## Core Rules

### 1. Define the Decision Before Research Starts

Always anchor the work to one decision:
- enter or avoid a market
- prioritize one segment over another
- shape positioning and pricing
- validate whether to build, launch, or expand

Research without a decision target becomes a document full of facts and no leverage.

### 2. Size the Market in Layers, Not in Headlines

Never stop at a single big number. Separate:

| Layer | Question | Failure Mode |
|-------|----------|--------------|
| **TAM** | How large is the broad category? | Sounds exciting but too abstract |
| **SAM** | Which part is actually reachable for this product and customer? | Overstates opportunity |
| **SOM** | What can realistically be won in a specific window? | Turns fantasy into planning |

Whenever possible, show the formula, assumptions, and confidence level. A smaller defensible number is better than a huge vague one.

### 3. Triangulate Evidence and Grade Source Quality

Use at least three evidence families before making a strong claim:
- market structure data: census, filings, association reports, public benchmarks
- behavior data: search trends, reviews, job posts, product usage proxies
- direct customer evidence: interviews, surveys, waitlists, prepayments, LOIs

See `evidence-grading.md` for the confidence ladder. If all evidence comes from one source type, the conclusion is still fragile.

### 4. Segment Before You Generalize

Do not treat "the market" as one blob. Split by:
- customer type
- company size
- geography
- urgency of problem
- willingness to pay
- existing alternatives

Many bad conclusions come from averaging together segments that behave very differently.

### 5. Map Competition Around Customer Choice, Not Only Brand Names

Competitor analysis includes:
- direct competitors
- indirect substitutes
- internal workarounds such as spreadsheets, agencies, or manual processes
- future entrants with clear adjacency

Use `competitor-analysis.md` to build a positioning map, review-mining matrix, and whitespace view. The real competitor is whatever the customer would choose instead of the proposed offer.

### 6. Favor Revealed Demand Over Stated Enthusiasm

Use interviews and surveys to learn language and patterns, but trust behavior more than compliments.

Strong signals:
- repeated painful workarounds
- urgent problem frequency
- customers introducing others with the same pain
- willingness to pay, pilot, pre-order, or switch

Weak signals:
- "great idea"
- generic survey positivity
- likes, followers, or broad curiosity with no concrete action

See `validation.md` for interview, survey, and pricing research structures.

### 7. Finish with a Decision-Ready Recommendation

Every deliverable should end with:

```text
RECOMMENDATION
- What the evidence supports
- What remains uncertain
- What should happen next
- What would change the recommendation
```

Good market research reduces uncertainty. Great market research makes the next move obvious.

## Common Traps

- **Top-down theater** -> Huge category numbers create false confidence and weak planning.
- **Competitor tunnel vision** -> Looking only at visible brands misses substitutes and status-quo behavior.
- **Segment blur** -> Mixing SMB, enterprise, prosumer, and consumer demand corrupts the conclusion.
- **Source recency failure** -> Old pricing pages and stale reports make current decisions look safer than they are.
- **Opinion inflation** -> Survey excitement without action gets mistaken for demand.
- **No confidence labeling** -> Strong and weak evidence get presented with the same weight.
- **Research with no recommendation** -> User gets a report but no practical decision path.

## Security & Privacy

This skill does NOT:
- make hidden outbound requests
- fabricate customer signals or fake interviews
- access private competitor systems
- create persistent memory or maintain a local workspace by default
- store secrets unless the user explicitly asks for that workflow

Live web research is appropriate only when the task requires current market data or the user asks for external evidence.

## Related Skills
Install with `clawhub install <slug>` if user confirms:
- `pricing` - Convert validation findings into pricing strategy and willingness-to-pay decisions.
- `seo` - Translate validated demand into search-driven positioning and content opportunities.
- `business` - Connect market findings to strategic choices and operating tradeoffs.
- `compare` - Structure side-by-side option analysis when multiple markets or segments compete.
- `data-analysis` - Turn collected numbers into cleaner interpretation and supporting visuals.

## Feedback

- If useful: `clawhub star market-research`
- Stay updated: `clawhub sync`

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →