Agent skill

Market Research

by ericrisco in ericrisco/rsc-harness

A skill your agent uses when a MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge, cut into reachable segments with one named beachhead…

MITAuto-check passedMarketing & SEO

Install Market Research

skills CLI
$ npx skills add ericrisco/rsc-harness --skill market-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ericrisco/rsc-harness market-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/market-research .claude/skills/market-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
market-research
GitHub stars
180
Token cost
~2.7k tokens
SKILL.md length
1,393 words
Files
6 (incl. scripts, references)
Skills in repo
233
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge, cut into reachable segments with one named beachhead…

  • Works in 5 steps: Hypothesis — the one-line market… → TAM / SAM / SOM block — all three with… → Segment table — market cut by… → …
  • A MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge
  • SKILL.md covers The hard stop: no named entities, The three jobs, Job 1 — Size it (triangulate… and Job 2 — Segment it (reachable…, plus 5 more sections
  • Runs Shell scripts from its folder

What it does

Market Research is an agent skill from ericrisco/rsc-harness. Use when a MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge, cut into reachable segments with one named beachhead, demand proven real, and a dated source behind every figure. NOT profiling named rivals and their moves (that is competitor-watch), NOT building a list of accounts to sell to (that is lead-gen).

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/demand-signals.md`).

It sits in Marketing & SEO, covering Market research, Market sizing and Lead generation. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.

When your agent uses it

  • A MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge
  • Cut into reachable segments with one named beachhead
  • Demand proven real
  • A dated source behind every figure

Example prompts

  • “/market-research”

Requirements

  • A Bash shell

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Hypothesis — the one-line market question being tested.
  2. TAM / SAM / SOM block — all three with numeric values, both methods shown, and an explicit convergence/divergence note. SOM ≤ SAM ≤ TAM…
  3. Segment table — market cut by firmographic/behavioral/JTBD axes, with one named beachhead.
  4. Demand-signal evidence — the signals, with the Google-Trends-is-relative caveat respected.
  5. Sources table — every load-bearing figure with a citation AND an access/publication date. No undated number survives this row.

What it can do on your machine

Read from SKILL.md and the folder at commit 1f8d9bb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Market Research loads about 2.7k tokens when it runs, and up to ~5k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 1,393 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ericrisco/rsc-harness at commit 1f8d9bb, republished under its MIT licence (© ericrisco). 1,393 words, ~2,724 tokens.

Download SKILL.mdSave it as .claude/skills/market-research/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
market-research
description
Use when a MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge, cut into reachable segments with one named beachhead, demand proven real, and a dated source behind every figure. NOT profiling named rivals and their moves (that is `competitor-watch`), NOT building a list of accounts to sell to (that is `lead-gen`).
tags
market-research, tam-sam-som, market-sizing, segmentation, demand-signals, jtbd, opportunity
recommends
competitor-watch, lead-gen, pitch-deck, financial-model, pricing, forecasting, content-engine
origin
risco

Market research — the size/segment/signal engine

You are the market-understanding engine. Someone hands you a fuzzy "is there a market for X?" and you hand back a sized, segmented, sourced market memo: how big the market is, who is in it, whether demand is real and moving, and where every number came from. Three jobs, in this order — size it → segment it → read the demand — and one hard stop you never cross.

The test of this work is not the number. It is whether someone else can audit the number. A $50B TAM you assert is a guess wearing a suit. A $48M you can re-derive two ways, cut into reachable segments, and back with dated sources is research. Every load-bearing figure in your memo carries a citation and an access date or it does not ship.

The hard stop: no named entities

This skill produces understanding of a market as a whole — never a named buyer you can call today, never a named competitor dossier. The moment the ask turns into "who specifically," stop and route it: a list of accounts with contacts is a sales list → ../lead-gen/SKILL.md; a rival's tiers, gaps and recent launches is a dossier → ../competitor-watch/SKILL.md.

Competition is only a force that shrinks SOM in this memo, never a per-company teardown. If you find yourself typing a competitor's product name into the sizing, you have crossed the line.

The three jobs

JobOne governing rule
Size itNever ship a number without a second, independent method
Segment itCut by the job buyers hire you for, then prove the slice is reachable AND distinct
Read demandSecondary to form the hypothesis, primary to decide it

Do them in order — sizing tells you what to segment, segments tell you where to read demand. The artifact at the end ties all three together with a sources table.

Job 1 — Size it (triangulate or it's a guess)

Two instruments, two different errors. Run both and force them to agree.

MethodStart fromFormulaStrengthFailure mode
Top-downA published industry figure (Gartner/IDC/Statista, e.g. "$70B CRM market")industry size × your segment share %Fast, anchors to a named sourceInherits and amplifies the report's error; easy to hand-wave the share %
Bottom-upYour customers + priceACV × number of ICP-fitting accountsGrounded in your own pricing; survives investor scrutinySlow; needs a real ICP and a real account count
The triangulation gate

Triangulation is the credibility test, not the number itself. 2026 investors treat a size as credible when the two methods converge within ~15–20%. A 3–5× divergence means your assumptions are broken — that is a signal to re-check the share %, the ACV, or the account count, never a menu to pick the bigger figure from. Lead the memo with the bottom-up number (real customer math) and triangulate it with top-down.

text
Bad   "TAM = $50B."                          # one number, no method, no source, no check
Good  Bottom-up:  960 ICP accounts × $50K ACV       = $48M
      Top-down:   18% of a $290M reachable segment  = $52M
      Converge within 8% → credible. Lead with $48M.
TAM / SAM / SOM are nested, not interchangeable
  • TAM — total demand if you owned 100% of the market.
  • SAM — the slice your business model + geography can actually serve.
  • SOM — the slice you can realistically capture near-term, given competition and sales capacity.

The funnel SAM ≈ 20% of TAM, SOM ≈ 10% of SAM is an illustrative example to defend, not a constant to assume. Derive SAM from your real reach (model, geography, language) and SOM from the competitive pressure and your sales capacity — then state why. Worked top-down and bottom-up calculations, the convergence math, the SAM-then-SOM derivation logic, and the full memo template with its sources/provenance schema live in references/sizing-playbook.md.

Job 2 — Segment it (reachable AND distinct, with a named beachhead)

Four classic axes — geographic, demographic, behavioral, firmographic (~81% of B2B marketers use firmographics). The 2025 edge is Jobs-to-be-Done: cluster buyers by the outcome they hire the product for, not by who they are. The why is blunt — people buy outcomes, not demographics. Best results come from a hybrid (firmographic + behavioral + JTBD) that yields a defensible beachhead.

Name the beachhead — the one segment you win first. Then run every segment through this test before it earns a row in the memo:

  • Distinct need? Does this slice hire the product for a different job than the others?
  • Reachable channel? Is there a concrete way to get in front of them (not "the internet")?
  • Big enough to matter? Does it move the SOM, or is it a rounding error?
  • Different enough to message separately? If the pitch is identical to another segment, it is not a real segment.

A segment that fails "reachable" or "distinct" is a demographic, not a market.

Job 3 — Read the demand (signal vs vanity)

Secondary and primary research answer different questions. Secondary first (industry reports, government statistics, filings, analyst data) — cheap, fast, right for the first pass, but vet recency and credibility in fast-moving sectors. Then primary to fill the gap that decides the call (surveys, interviews) — current and specific, but slow and small-sample. Form the hypothesis on secondary; spend primary only on the question that actually decides yes/no.

The hard caveat: Google Trends is RELATIVE interest, never absolute volume. Rising search interest is a verified leading sign of growth (Google still ~90% of search), but a Trends curve is normalized 0–100 — you never convert a Trends curve into a market size. Pair it with absolute-volume tools (Keywords Everywhere for volume/CPC, Exploding Topics which flags breakout niches growing >5,000%) before you treat a trend as size.

text
Bad   "Search interest doubled on Google Trends → the market is $2B."   # relative ≠ size
Good  Rising Trends curve  +  Keywords Everywhere shows 40K/mo absolute
      +  Exploding Topics flags it breakout  +  3 buyer interviews say "I'd pay"
      → a real, triangulated demand signal.

A real signal is rising search plus breakout-topic confirmation plus paying-intent from a primary interview. Vanity is one viral spike, a single curve, or a report with no date. The signal-source catalog and a source-grading rubric (recency, methodology, sample size, credibility) are in references/demand-signals.md.

Show full SKILL.md (466 more words)Show less

The market memo (the artifact)

Every market-research output has the same fixed shape so it can be audited and handed off:

  1. Hypothesis — the one-line market question being tested.
  2. TAM / SAM / SOM block — all three with numeric values, both methods shown, and an explicit convergence/divergence note. SOM ≤ SAM ≤ TAM must hold.
  3. Segment table — market cut by firmographic/behavioral/JTBD axes, with one named beachhead.
  4. Demand-signal evidence — the signals, with the Google-Trends-is-relative caveat respected.
  5. Sources table — every load-bearing figure with a citation AND an access/publication date. No undated number survives this row.

This is exactly what scripts/verify.sh checks. Keep it Markdown so the linter can parse it.

Anti-patterns

BadGoodWhy
Ship one TAM number, no second methodRun top-down AND bottom-up, state the convergenceA lone figure is unfalsifiable; readers discount it
"$50B market" with no source or yearCite the report + access date for every figureUndated/unsourced = a guess; markets move fast
Top-down and bottom-up are 4× apart, pick the biggerRe-check inputs until they converge ≤~20%3–5× divergence means broken assumptions, not a choice
Convert a Google Trends curve into a market sizePair with absolute-volume tools before sizingTrends is RELATIVE interest, never absolute volume
Segment by demographics aloneAdd JTBD/behavioral; name a reachable beachheadDemographics miss why people buy, and a market with no beachhead is one you can't enter
Treat SAM/SOM as fixed 20%/10% of TAMDerive SAM from reach, SOM from competition + capacityThose ratios are illustrative, not constants
Name specific competitor products in the memoTreat competition as a SOM-shrinking forceA dossier is scope creep — hand to competitor-watch
List named target accounts as "the market"Hand the segment to lead-gen to build the listThat is a sales list, not market understanding
All secondary data, no primary check on the decisive questionUse interviews/survey to fill the gap that decidesStale or misaligned reports mislead the call — you just confirm your own bias

Verify

The memo is a checkable artifact, so scripts/verify.sh lints a produced memo file (read-only — it never edits) for the three things above that keep "market sizing" honest: the numeric SOM ≤ SAM ≤ TAM nesting, both methods plus a stated convergence/divergence note (one method alone fails), and a citation and date on every load-bearing figure.

bash
./scripts/verify.sh                     # scan ./ for *memo*/*market*.md
./scripts/verify.sh --path memo.md      # check one memo
./scripts/verify.sh --path research/    # scan a directory of memos
./scripts/verify.sh --strict            # treat warnings as failures (CI gate)

It exits 0 on a clean or empty target — a missing memo is a skip, never a false failure.

Hand-offs

The memo is the start of a chain. When it is done, route:

  • Present the sizing as the opportunity slide → ../pitch-deck/SKILL.md.
  • Model revenue off the SOM → ../financial-model/SKILL.md.
  • Turn a named segment into an actionable account list → ../lead-gen/SKILL.md.
  • Profile the rivals that shrink the SOM → ../competitor-watch/SKILL.md.
  • Set the ACV the bottom-up math depends on → ../pricing/SKILL.md.
  • Project the demand series forward from history → ../forecasting/SKILL.md.
  • Act on the keyword/topic demand signals → ../content-engine/SKILL.md.

© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/market-research of ericrisco/rsc-harness.

  • SKILL.md
  • evals/README.md
  • evals/cases.yaml
  • references/demand-signals.md
  • references/sizing-playbook.md
  • scripts/verify.sh

Open the folder on GitHubat commit 1f8d9bb

Compare with similar skills

Market Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Market Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Market Research this skillericrisco/rsc-harness180—~2.7kAutomated safety check: PassMIT
Startup Designferdinandobons/startup-skill1.2k—~8.1kAutomated safety check: PassMIT
Market Research ReportsK-Dense-AI/claude-scientific-writer2.4k1 repos~3.5kAutomated safety check: PassMIT
Market Research Analysismanojbajaj95/claude-gtm-plugin105—~2.6kAutomated safety check: PassMIT
Product Strategistnicepkg/auto-company1951 repos~2.4kAutomated safety check: PassNone
Market Researchshawnpang/startup-founder-skills343—~1.9kAutomated safety check: PassMIT

Similar skills

  • Startup Design

    ferdinandobons/startup-skill

    Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.

    1.2k GitHub stars~8.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Market Research Reports

    K-Dense-AI/claude-scientific-writer

    Builds market research reports and market sizing or forecast scenarios in which every claim, source, assumption and uncertainty can be traced and audited.

    2.4k GitHub starsUsed in 1 repo~3.5k tokens
    Marketing & SEOAuto-check passed
  • Market Research Analysis

    manojbajaj95/claude-gtm-plugin

    Comprehensive market research and analysis skill. An agent skill from manojbajaj95/claude-gtm-plugin.

    105 GitHub stars~2.6k tokensUpdated 22 days ago
    Marketing & SEOAuto-check passed
  • Product Strategist

    nicepkg/auto-company

    Expert product strategy covering market analysis, competitive positioning, go-to-market planning, and product-led growth.

    195 GitHub starsUsed in 1 repo~2.4k tokens
    Marketing & SEOAuto-check passed
  • Market Research

    shawnpang/startup-founder-skills

    When the user needs to estimate market size, understand market dynamics, or validate that a market opportunity is large enough to pursue.

    343 GitHub stars~1.9k tokensUpdated 6 mo ago
    Marketing & SEOAuto-check passed
  • Market Research

    gustavscirulis/snapgrid

    Deep market analysis for iOS/macOS apps including market sizing (TAM/SAM/SOM), growth trends, market maturity, entry barriers, distribution channels, and revenue potential.

    116 GitHub starsUsed in 1 repo~3.1k tokens
    Marketing & SEOAuto-check passed

More from ericrisco/rsc-harness

All 233 skills in this repo
  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    180 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    180 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Ads

    ericrisco/rsc-harness

    A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…

    180 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Agent Eval

    ericrisco/rsc-harness

    A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…

    180 GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • AI Media

    ericrisco/rsc-harness

    A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…

    180 GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Analytics

    ericrisco/rsc-harness

    A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.

    180 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Questions about Market Research

What does Market Research do?

A skill your agent uses when a MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge, cut into reachable segments with one named beachhead…. Market Research is an agent skill from ericrisco/rsc-harness. Use when a MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge, cut into reachable segments with one named beachhead, demand proven real, and a dated source behind every figure.

When should I use Market Research?

Market Research fits situations like: A MARKET as a whole needs a defensible picture — TAM/SAM/SOM sized top-down AND bottom-up until the two converge; cut into reachable segments with one named beachhead; demand proven real; A dated source behind every figure.

How do I install Market Research in Claude Code?

Run `npx skills add ericrisco/rsc-harness --skill market-research -a claude-code`. Or copy the skill folder (skills/market-research in ericrisco/rsc-harness) into .claude/skills/market-research in your project. Claude Code loads it when a task matches its description.

How do I install Market Research in Codex?

Run `npx skills add ericrisco/rsc-harness --skill market-research -a codex`. Or copy the skill folder (skills/market-research in ericrisco/rsc-harness) into .agents/skills/market-research in your project. Codex loads it when a task matches its description.

Can I use Market Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill market-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/market-research, .gemini/skills/market-research, .github/skills/market-research and .opencode/skills/market-research in your project.

What does Market Research need to run?

Going by SKILL.md and its folder, Market Research needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Market Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Market Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Market Research use?

Market Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Market Research use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Market Research?

Skills that share tags, products or a category with Market Research: Startup Design (ferdinandobons/startup-skill, 1.2k stars), Market Research Reports (K-Dense-AI/claude-scientific-writer, 2.4k stars), Market Research Analysis (manojbajaj95/claude-gtm-plugin, 105 stars) and Product Strategist (nicepkg/auto-company, 195 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Market Research?

ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 180 GitHub stars. The repository holds 233 skills in this directory. The repository was last updated on October 9, 2026.

Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.