Skip to content

ericrisco/rsc-harness / skills/market-research

market-research

Verified

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`).

FileKindSize
SKILL.mdskill md10.8 KB
evals/README.mdmarkdown1.5 KB
evals/cases.yamlconfig3.5 KB
references/demand-signals.mdmarkdown3.7 KB
references/sizing-playbook.mdmarkdown5.0 KB
scripts/verify.shexecutablescript8.2 KB

evals/README.md

View on GitHub
# Evals — market-research

`cases.yaml` holds three groups for this skill's router and capability. Run them against whatever eval harness the repo provides, or check by hand: feed each `should_trigger` prompt to the router and confirm it selects `market-research` (including the non-obvious ones — cross-checking an existing TAM, the top-down-vs-bottom-up method choice, and the Spanish/Catalan sizing asks); feed each `should_not_trigger` prompt and confirm it routes to the named sibling (`competitor-watch` for a named-rival dossier, `lead-gen` for a named account list, `pitch-deck` for the slide, `financial-model` for the revenue model, `forecasting` for a single-series forecast) and not here — these encode the boundaries that bleed. The `capability` case is graded against its `must_include` rubric on an actual generated memo for the dental-clinic scenario: tick each line (TAM/SAM/SOM with nesting, both methods plus a convergence note, a segment table with one beachhead, a demand signal that respects the Google-Trends-is-relative caveat, a dated sources table, derived rather than assumed SAM/SOM, no competitor dossier, and an explicit hand-off). Pair the capability grade with `scripts/verify.sh` against the generated memo file to confirm the artifact actually holds up — TAM/SAM/SOM nesting, both-methods-plus-convergence, and dated sources — where the rubric judges research quality and verify.sh judges structural integrity. No automated harness is assumed beyond reading the prompts and checking routing plus the rubric.
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: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
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: 115kUpdated Claude CodeCodexVerifiedInstall
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: 115kUpdated Claude CodeCodexVerifiedInstall