The market axis of the broad pass — sweep a domain wide for its visible structure: the segments, the ways money moves in the category, how people buy, and the observable sizes and spend, one line per entry with where it was observed. TRIGGER when a thread needs the domain's market structure enumerated before any one part is mined. DO NOT TRIGGER to mine one part deep (research-market), to enumerate the problems people voice (discover-problems), or to draw the competitive set (discover-competi...
Scanned 9/5/2026
Install to Claude Code
npx -y skills add heyJordanParker/dotfiles --skill discover-market --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Discover Market?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-discover-market)More formats (shields.io, HTML) on the badges page.
---
name: discover-market
description: The market axis of the broad pass — sweep a domain wide for its visible structure: the segments, the ways money moves in the category, how people buy, and the observable sizes and spend, one line per entry with where it was observed. TRIGGER when a thread needs the domain's market structure enumerated before any one part is mined. DO NOT TRIGGER to mine one part deep (research-market), to enumerate the problems people voice (discover-problems), or to draw the competitive set (discover-competitors).
---
# Discover Market
Run /discover; this adds only the market axis. discover owns the sweep, the trust check, the page gate, the find-with-search-record-from-the-page rule, the enumeration-only rule, and the write to `research/<subject>/discovery/` — hold to it and add only what follows.
Inputs: the one domain, named by its question, from the research `Brief.md` — nothing else. Excluded: owner facts, product facts, any persona or target buyer, and any solution shape — the market's structure is what the sweep finds, never a guess confirmed. The dispatch carries the domain only, with no reference to a sibling thread.
## The entry is a piece of the market's visible structure
The subject is the domain itself as a market. Sweep it wide and enumerate its visible structure long — one line per entry, each carrying where it was observed (the URL):
- **Segments** — the distinct sub-markets the domain splits into: the named tiers, verticals, and buyer bands the category itself talks about.
- **How money moves** — the ways the category is paid for as observed in the open: subscription, one-off, retainer, marketplace take, ad-supported, done-for-you — each an observed pricing or billing shape, not a guess.
- **How people buy** — the observed buying paths: self-serve signup, sales-led, through an agency, via a marketplace, through a community.
- **Observable sizes and spend** — the countable numbers the market shows about itself: category revenue figures, headcounts, subscriber or member counts, typical price points — each read off the page it sits on.
### Record the observed structure, never a market verdict
Each entry is a piece of structure observed on a page, never a claim that the market is big, growing, or worth entering. An observed price point is a record that one seller charges it, never the category's price. Whether a segment is a real market to enter is the judged-files step's, from these entries — never sized or ranked here.
### Enumerate the structure, name no competitor as the set
Naming a specific product only as an observed example of how money moves or how people buy is fine. Drawing the competitive set — who competes for this buyer's money — is discover-competitors' job, run as its own thread; never build that set here.

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!