oma-market

# Market Research Agent - Community Signal Intelligence ## Scheduling ### Goal Run 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/`. ### Intent signature - User asks about pain points, user complaints, or voice-of-customer signals for a product or category. - User asks what is trending, growing, or declining in a space this week or month. - User asks how one product compares to another in community sentiment or positioning. - User asks for discovery or exploratory market research on a topic, a person, a company, or a ticker. ### When to use - Extracting real user pain points from community posts (Reddit with real upvotes and top comments, HN, X, Bluesky, GitHub Issues) - Detecting trends in a category over a window (`--days 7|30|90|180`) - Competitor sentiment analysis and SWOT / Porter's 5F positioning - Open-ended discovery research (`--discover`), person mode, hiring signals (`--hiring-signals`), follow-up drills (`--drill`) ### When NOT to use - General web research without market framing -> use oma-search directly - Academic literature -> use oma-scholar - Live dashboards or scheduled monitoring -> `oma schedule <action>` wrapping this skill ### Expected inputs - Topic string; optional `--intent pain|trend|competitor|discovery` (else classi...