/oma-market

name: oma-market
description: Research customer pain points, trends, and competitors through the
  OMA market engine. Use for market discovery or voice-of-customer analysis.

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 classified per `resources/intent-rules.md`)
• Optional window (`--days`), `--vs <entity>` (competitor), `--frameworks auto|none|swot,5f,pestel`
• Any native last30days flag (see `oma market run --help`) — passed through verbatim

Expected outputs

• Single markdown brief at `.agents/results/market/{topic-slug}-{YYYYMMDD}.md`
• First line: the engine's badge (`🌐 last30days v{VERSION} · synced {date}`); body per the upstream OUTPUT CONTRACT; framework sections appended per intent; engine footer preserved
• Raw engine artifacts under `market.save_dir` (default `.agents/results/market/raw/`)

outputs:
  - name: market-brief
    description: Single LAW-compliant markdown brief with framework sections
    artifact: ".agents/results/market/*.md"
    required: true

Dependencies

• `oma market resolve` / `oma market run` — engine location, Python 3.12+ resolution, `--save-dir` default
• The upstream `SKILL.md` at the resolved engine root (`skillMd` in `oma market resolve --json`) — the authoritative research contract
• `resources/intent-rules.md`, `resources/frameworks/`, `resources/output-laws.md`, `resources/execution-protocol.md`

Control-flow features

• `oma market detect-trap` gate before anything else (exit 2 = REFUSE, exit 4 = invalid)
• Engine is the skills-CLI install of `last30days`: `oma market resolve` reads installed skill dirs (a `market.path` / `LAST30DAYS_HOME` pin wins); `oma market update` installs it when missing and updates it otherwise
• Sources needing keys/cookies auto-skip inside the engine; keyless sources (Reddit, HN, GitHub, Polymarket, arXiv, Techmeme, Digg, web) always run
• Framework auto-toggle by intent (pain/trend → SWOT; competitor → SWOT + Porter's 5F; discovery → SWOT + PESTEL)

Structural Flow

Entry

1. Run `oma market detect-trap "<topic>"`. Exit 2 → surface the REFUSE reason and reframe suggestion, stop. 2. Run `oma market resolve --json`. `ok: false` → report `reason` (missing engine → ask the user, then `oma market update`; missing Python → the install hint) and stop. Never fall back to WebSearch-only synthesis and present it as market research. 3. Read the upstream contract at `engine.skillMd` **top to bottom**. It is long by design; do not skim. Treat `engine.root` as its `SKILL_DIR`. 4. Classify intent per `resources/intent-rules.md`; map to engine flags and framework set.

Scenes

1. **PREPARE**: detect-trap, resolve, read upstream SKILL.md, classify intent. 2. **UPSTREAM STEPS**: follow the upstream SKILL.md exactly — Step 0 (first-run setup wizard, consent-driven), intent parsing, Step 0.45 (its own query-quality preflight), Step 0.5 / 0.55 (handle, subreddit, hashtag resolution when WebSearch is available), Step 0.75 (query plan). Skip only its "Runtime Preflight" Python-hunt block: `oma market run` already resolved the interpreter. 3. **RUN**: wherever the upstream contract says `"${LAST30DAYS_PYTHON}" "${SKILL_DIR}/scripts/last30days.py" <args>`, run `oma market run <args>` with the **same arguments** (foreground, 5-minute timeout, `--emit=compact`). `--save-dir` is added automatically from `market.save_dir` unless you pass one. 4. **SYNTHESIZE**: produce the brief exactly as the upstream OUTPUT CONTRACT dictates (badge first line, Ranked Evidence Clusters, LAWs). Then append the framework sections selected for the intent, using only clusters present in the engine output as evidence (`resources/frameworks/`). 5. **FINALIZE**: run the self-check in `resources/output-laws.md`, write `.agents/results/market/{topic-slug}-{YYYYMMDD}.md`, preview the first 50 lines.

Transitions

• `--vs <entity>` or "A vs B" phrasing → competitor intent → upstream COMPARISON flow (two passes + head-to-head as its contract specifies) → SWOT + Porter's 5F.
• Person / company / ticker topics → upstream person / hiring-signals / StockTwits handling applies unchanged.
• `engine.status: stale` → include the `note` in the report (research ran on the cached engine version).

Failure and recovery

• detect-trap exit 2 → REFUSE; do not run the engine; `--force` only on explicit user reconfirmation.
• `oma market resolve` not ok → stop with the reason; no engine run.
• Engine non-zero exit → report stderr verbatim; do not synthesize from partial stdout unless the upstream contract says the emitte