agentleFS
Sign inStart free
velonxvelonx/agent-skills/skills/market-research/SKILL.md

market-research

Skill1 starsChanged 51 days agoMITView on GitHub

Size and describe a market - segments, customers, trends, pricing norms and demand signals - from public sources, with every number sourced. Use when the user asks how big a market is, who the customers are, whether there is demand, or wants a market overview for a product idea.

113 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-outreach

    Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.

    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

  • tpavanipradeepSkill

    nextjs-turbopack

    Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

    Also in 14 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

  • +1 more from Infopibe

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 99 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Demand signals: search trends, funding activity, job postings, community size.

    line 40
  2. Distinctive:

    No access to paid databases.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 99 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

Overview

Produces a sourced market overview: definition, size (top-down and bottom-up), segments, buyer needs, trends, pricing, and demand signals — with assumptions visible so the user can challenge them.

When to Use

  • "How big is the market for…", "who would buy…", "is there demand for…"
  • Early product or startup validation, investor memo prep, go-to-market planning.

For a head-to-head look at specific competitors, use competitive-analysis.

Usage

  1. Define the market precisely: product category, geography, customer type (B2B/B2C), year.
  2. Size it two ways:
    • Top-down: find published market estimates; note publisher, year and method. Estimates often disagree — show the range.
    • Bottom-up: number of target customers × adoption rate × price. Source each input; label assumptions as assumptions.
  3. Segment by the dimension that changes buying behaviour (company size, use case, income, region).
  4. Customer needs: what job they hire the product for, current alternatives, switching costs. Use reviews, forums and surveys as evidence.
  5. Trends: 3–5 forces changing the market (regulation, technology, cost curves), each with a source.
  6. Pricing norms: typical price points and models.
  7. Demand signals: search trends, funding activity, job postings, community size.
  8. Output as a brief with a TL;DR, the sections above, a sizing table with formulas, and a source list. End with the 3 biggest unknowns.

Examples

Prompt: "How big is the market for AI meeting-notes tools for small businesses in India?"

The agent defines the segment (SMBs with 10–200 employees), finds SMB counts from government statistics, estimates adoption from comparable SaaS categories, applies local pricing, and shows the top-down range from analyst reports alongside the bottom-up estimate.

Limitations

  • Public market-size reports vary wildly in quality; treat them as rough ranges.
  • Bottom-up numbers are only as good as their assumptions — they are shown so the user can change them.
  • No access to paid databases.

Changelog

  • 1.0.0 — Initial release.

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.

Check your setup, free