ericrisco/rsc-harness / skills/market-research
market-research
VerifiedUse 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| evals/README.md | markdown | 1.5 KB |
| evals/cases.yaml | config | 3.5 KB |
| references/demand-signals.md | markdown | 3.7 KB |
| references/sizing-playbook.md | markdown | 5.0 KB |
| scripts/verify.shexecutable | script | 8.2 KB |
evals/cases.yaml
View on GitHubskill: market-research
should_trigger:
- prompt: "How big is the market for AI legal-research tools in Spain?"
why: Core sizing request for a whole market — Job 1, the central case for this skill.
- prompt: "Sanity-check this TAM before our seed raise — does $2B hold up?"
why: Non-obvious; cross-checking an existing number IS the triangulation core, not deck design or modeling.
- prompt: "Cut our addressable market into segments and tell me which one to attack first."
why: Segmentation plus naming the beachhead — Job 2 of this skill.
- prompt: "Is there actually demand for a B2B carbon-accounting product, or are we imagining it?"
why: Demand-signal validation of a market hypothesis — Job 3, secondary-then-primary.
- prompt: "Should we size this top-down from the industry report or bottom-up from our customers?"
why: Non-obvious; the top-down-vs-bottom-up choice and triangulation gate are this skill's method, not a generic data pull.
- prompt: "¿Qué tamaño tiene el mercado de software de reservas para restaurantes y cuál es el TAM/SAM/SOM?"
why: Spanish-language ask for the full sizing job — TAM/SAM/SOM explicitly requested.
- prompt: "Quina mida té el mercat d'apps de reserves i hi ha demanda real?"
why: Catalan-language ask combining market size and demand validation — both core jobs.
should_not_trigger:
- prompt: "Profile Competitor X — their pricing tiers, feature gaps, and recent product launches."
route_to: competitor-watch
why: A named-rival dossier with moves over time, not market-as-a-whole understanding.
- prompt: "Build me a list of 200 SaaS companies in fintech with the VP Eng contact for each."
route_to: lead-gen
why: An actionable list of named accounts/contacts to sell to, not a sized market.
- prompt: "Turn this market sizing into the opportunity slide for our deck."
route_to: pitch-deck
why: Presenting an already-produced sizing as a slide, not producing the sizing.
- prompt: "Build the 3-year revenue model off our SOM."
route_to: financial-model
why: Modeling forward revenue/costs off the SOM, not sizing the market.
- prompt: "Forecast next year's demand from our last 24 months of sales data."
route_to: forecasting
why: A single-series statistical forecast from existing history, not market sizing or signal validation.
capability:
- scenario: >
Product idea: a B2B scheduling tool for dental clinics in Spain. Assumed ACV is
€1,200/clinic/year. You have access to web research. Produce a market memo.
must_include:
- TAM, SAM and SOM all present with numeric values, and SOM <= SAM <= TAM nesting holds.
- BOTH a top-down figure (industry/segment source) AND a bottom-up figure (ACV × ICP account count), with an explicit convergence/divergence note.
- A segment table cutting the market by firmographic/behavioral/JTBD axes with exactly one named beachhead.
- At least one demand signal cited, with the Google-Trends-is-relative caveat respected (no Trends curve treated as absolute size).
- A sources table where every load-bearing figure has a citation/URL AND an access or publication date.
- SAM and SOM derived from stated reasons (reach, language/geography, competition, capacity) — not assumed as flat 20%/10% of TAM.
- No named competitor products treated as dossiers; competition appears only as a SOM-shrinking force.
- An explicit hand-off note (pitch-deck for the slide, financial-model for revenue, lead-gen for the list, competitor-watch for rivals).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |