Skip to content

gracefullight/pkgs / .agents/skills/oma-market

oma-market

Unverified

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

resources/intent-rules.md

View on GitHub
# Intent classification rules for oma-market — maps the request to one of 4 intents, then to engine flags and frameworks.

## Precedence

1. Explicit flag `--intent <pain|trend|competitor|discovery>` always wins.
2. `--vs <entity>` present → intent = `competitor`.
3. `" vs "` / `" 대 "` / "비교" in the topic → `competitor`.
4. Keyword scan (table below) → highest-scoring intent wins; tie-break `competitor > pain > discovery > trend`.
5. Fallback: complaint keyword → `pain`; else → `trend`.

| Intent | English keywords |
|---|---|
| pain | broken, bug, crash, slow, freeze, lag, outage, migrate, ditched, quit, alternative, replacing, painful, frustrating, hate, worst, unusable, deprecated |
| trend | trend, trending, growth, adoption, rising, popular, new, emerging, hot, forecast, survey, report, state of, this month |
| competitor | vs, versus, alternative, replaced, switched, comparison, compare, benchmark, better than, worse than, switch from |
| discovery | wish, need, missing, underrated, underserved, I want, if only, why doesn't, gap, overlooked, unmet, what's exploding |

Korean / Japanese / Chinese prompts are classified by reading the prompt directly (activation tokens live in `.agents/hooks/core/triggers.json §oma-market`).

## Intent → engine invocation → frameworks

<!-- oma-docs:ignore-start -->
The engine is `oma market run` (= upstream `scripts/last30days.py`). Flags below are additive to whatever the upstream SKILL.md resolves in its Steps 0.5–0.75 (`--plan`, `--subreddits`, `--x-handle`, …).
<!-- oma-docs:ignore-end -->

| Intent | Topic shaping / engine flags | Frameworks (`--frameworks auto`) |
|---|---|---|
| pain | topic as "<subject> problems / complaints"; `--days 30` default; `--deep` when the corpus is thin | SWOT |
| trend | topic as-is; `--days 30` (7 for "this week", 90/180 for "this year"); `--discover "<domain>"` for "what's hot in X" | SWOT |
| competitor | `"<A> vs <B>"` topic → upstream COMPARISON flow (pass A, pass B, head-to-head); `--x-related` when handles resolved | SWOT + Porter's 5F |
| discovery | `--discover` (global) or `--discover "<domain>"`; then `--drill` on the chosen cluster when the user follows up | SWOT + PESTEL |

Person, company, ticker, and hiring topics keep the upstream behaviour (person mode, `--github-user`, `--hiring-signals`, StockTwits auto-activation); frameworks default to `none` for person topics unless asked.

`--frameworks none` suppresses all framework sections; an explicit list (`swot,5f,pestel`) overrides the table.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall