oma-market
Market research skill for pain-point extraction, trend detection, competitor positioning, and discovery across community sources (Reddit, HN, Bluesky, Mastodon, GitHub Issues, web). Built-in harvest fetchers, deterministic CLI compute, intent-auto SWOT/Porter's 5F/PESTEL frameworks. Use for market research, pain point analysis, trend detection, competitor research, user complaints, voice-of-customer, 시장조사, 사용자 페인, 트렌드, 경쟁구도.
npx skills add first-fluke/oh-my-agent --skill oma-market --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Market Research Agent - Community Signal Intelligence ## Scheduling ### Goal Classify user intent into pain / trend / competitor / discovery, fan-out to community sources via `oma market harvest`, score and cluster findings with deterministic CLI compute, auto-apply strategic frameworks, and emit a single LAW-compliant markdown brief. ### 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. ### When to use - Extracting real user pain points from community posts (Reddit, HN, GitHub Issues, Bluesky, Mastodon) - Detecting trends in a product category over a time window (7d / 30d / 90d / 180d) - Competitor sentiment analysis and SWOT positioning - Open-ended discovery research across multiple sources ### When NOT to use - General web research without market framing -> use oma-search directly - Single-source queries only -> use `oma search fetch` standalone - Delta tracking or trend
- Scheduling
- Goal
- Intent signature
- When to use
- When NOT to use
- Expected inputs
- Expected outputs
- Dependencies
- Control-flow features
- Structural Flow
- Entry
- Scenes
- Transitions
- Failure and recovery
oma market detect-trap "$TOPIC" \
What does the oma-market skill do?
Market research skill for pain-point extraction, trend detection, competitor positioning, and discovery across community sources (Reddit, HN, Bluesky, Mastodon, GitHub Issues, web). Built-in harvest fetchers, deterministic CLI compute, intent-auto SWOT/Porter's 5F/PESTEL frameworks. Use for market research, pain point analysis, trend detection, competitor research, user complaints, voice-of-customer, 시장조사, 사용자 페인, 트렌드, 경쟁구도.
How do I install it?
Run `npx skills add first-fluke/oh-my-agent --skill oma-market --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.