oma-market

1# Market Research Agent - Community Signal Intelligence
2 
3## Scheduling
4 
5### Goal
6Run the upstream `last30days` research engine (always the latest release, managed by oma) for community-signal research, then frame the result for the user's intent (pain / trend / competitor / discovery) with strategic frameworks and save one brief under `.agents/results/market/`.
7 
8### Intent signature
9- User asks about pain points, user complaints, or voice-of-customer signals for a product or category.
10- User asks what is trending, growing, or declining in a space this week or month.
11- User asks how one product compares to another in community sentiment or positioning.
12- User asks for discovery or exploratory market research on a topic, a person, a company, or a ticker.
13 
14### When to use
15- Extracting real user pain points from community posts (Reddit with real upvotes and top comments, HN, X, Bluesky, GitHub Issues)
16- Detecting trends in a category over a window (`--days 7|30|90|180`)
17- Competitor sentiment analysis and SWOT / Porter's 5F positioning
18- Open-ended discovery research (`--discover`), person mode, hiring signals (`--hiring-signals`), follow-up drills (`--drill`)
19 
20### When NOT to use
21- General web research without market framing -> use oma-search directly
22- Academic literature -> use oma-scholar
23- Live dashboards or scheduled monitoring -> `oma schedule <action>` wrapping this skill
24 
25### Expected inputs
26…