agentleFS
nesnilnehcnesnilnehc/ai-cortex/skills/market-research/SKILL.md

market-research

Skill8 starsChanged 2 months agoMITView on GitHub

Define a market and examine customers, demand, segments, trends, and defensible size estimates with transparent evidence.

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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 99 edited versions we read keep these.

  • 0

    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. Very specific:

    If sizing is defensible, show formula, source inputs, assumptions, range, units and date.

    line 22

“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

Skill: Market Research

Purpose

Study a defined market without assuming that a popular category or vendor estimate is a real demand signal. Apply deep-research and preserve its Research Report as the evidence core.

Procedure

  1. Define geography, segment, buyer and user, included products, exclusions, period and currency before searching. Record definition changes across sources.
  2. Decompose demand, customer jobs, adoption, budgets, size, growth, supply and shifts. Prefer authorized customer interviews and observed use for need; method-bearing datasets, filings and associations for size. Attribute vendor, consultant and media estimates.
  3. Inspect methodology, sample, denominator, year and provenance family. Cross-check important numbers against independent sources where possible. Do not add incompatible figures.
  4. If sizing is defensible, show formula, source inputs, assumptions, range, units and date; map each input to finding IDs. If it is not, state unsupported and list missing inputs instead of inventing TAM/SAM/SOM.
  5. Separate demand evidence from awareness or sales assertions. Classify every material statement and preserve contradictory estimates in conflicts. Add domain: "market" and domain_details only if useful; never replace common source or finding fields.

Self-check

The reader can reproduce the market boundary and any estimate. Vendor claims remain attributed; trend and demand evidence are dated. Missing customer signals and unsupported sizing appear as gaps.

Examples

Reproducible estimate

Input: estimate annual spending for a defined buyer segment in one country. Output: show the segment boundary, source-backed buyer count and spend assumptions, formula, dated range, and finding IDs for each input.

Incompatible estimates

Input: two sources use different definitions of the market, and neither discloses a denominator. Output: keep the figures separate as attributed claims, mark sizing unsupported, and name the missing inputs needed for a defensible estimate.

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.