agentleFS
fatihkanfatihkan/badi/.claude/skills-vault/market-research/SKILL.md

market-research

Skill8 starsChanged 3 months agoMITView on GitHub

Market and demand research procedures. Niche discovery, demand sizing, competitor/gap analysis, opportunity scoring, and pricing/positioning signals BEFORE building. Triggers on: market research, demand, niche, opportunity sizing, competitor analysis, TAM, positioning, pricing, go-to-market, validate idea, is there demand.

118 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use everything-claude-code, everything-claude-code-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • InfopibeSkill

    everything-claude-code

    Also in 9 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • InfopibeSkill

    investor-materials

    Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.

    Also in 22 projects that use this

  • shawnpangSkill

    competitor-monitoring

    When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".

    Also in 3 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 7 projects that use this

  • CodeWithBehnamSkill

    dmux-workflows

    Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

    Also in 15 projects that use this

  • +1 more from Infopibe

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 104 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search the language users actually use (forums, reviews, search suggest, social).

    line 21
  2. Distinctive:

    Look for existing spend: are people already paying for a worse alternative?

    line 23
  3. Distinctive:

    Prefer a narrow segment you can dominate over a wide one you can't.

    line 30
  4. Distinctive:

    Put a credible number on the prize.

    line 33
  5. Very specific:

    Run /market for an agent-driven synthesis, or badi market discover|reviews|difficulty for App Store data.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 104 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Market Research Skills

Structured procedures for validating demand and sizing an opportunity before you build. Pairs with the market-researcher agent and the /market command; for App Store metrics use badi market.

Skill List

1. Demand validation

Confirm a real, expressed need exists before committing build time.

  • Search the language users actually use (forums, reviews, search suggest, social).
  • Distinguish vitamin (nice-to-have) from painkiller (urgent, paid-for) demand.
  • Look for existing spend: are people already paying for a worse alternative?
  • Output: a demand verdict (strong / weak / none) with the evidence quoted.

2. Niche discovery

Find an under-served, winnable segment instead of a crowded horizontal.

  • Decompose a broad market into segments by user, use-case, and platform.
  • Score each on demand × competition × your unfair advantage.
  • Prefer a narrow segment you can dominate over a wide one you can't.

3. Opportunity sizing

Put a credible number on the prize.

  • Top-down (category size × reachable share) sanity-checked bottom-up (reachable users × conversion × price).
  • State assumptions explicitly; size a range, not a false-precise point.
  • Flag when the honest answer is "too small to matter".

4. Competitor + gap analysis

Map who's already here and where the opening is.

  • List incumbents; for each: positioning, pricing, strengths, weak reviews.
  • Mine 1-2★ reviews of incumbents for the unmet need to build around.
  • Name the specific gap (segment, feature, price point, channel) to win on.

5. Positioning + pricing signal

Decide how to enter, not just whether.

  • Anchor pricing to the value/alternative, not cost; find the willingness-to-pay band.
  • Draft a one-line positioning: for [who] who [need], [product] is [category] that [benefit].
  • Identify the wedge channel where the target user already congregates.

6. Go / shrink / pass decision

Convert research into a decision.

  • Synthesize demand + size + gap into a verdict with a confidence level.
  • Define the single kill-signal that would reverse a "go".
  • Record the read so /ceo-review can challenge it.

How to use

Run /market for an agent-driven synthesis, or badi market discover|reviews|difficulty for App Store data. This skill provides the methodology the agent and command follow; activate it with badi skills add market-research.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.