oma-market

Market research skill for pain-point extraction, trend detection, competitor positioning, and discovery across community sources (Reddit, X, YouTube, TikTok, HN, Polymarket, GitHub, arXiv, Techmeme, Bluesky, web and more). Delegates research to the always-latest mvanhorn/last30days engine via `oma market run`, adds oma's detect-trap preflight, intent-auto SWOT / Porter's 5F / PESTEL framing, and a single LAW-compliant brief. Use for market research, pain point analysis, trend detection, competitor research, user complaints, voice-of-customer, 시장조사, 사용자 페인, 트렌드, 경쟁구도.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written operational contract with concrete commands, explicit validation gates, and sound reference structure. Minor gains are available from de-duplicating the gate descriptions and confirming the referenced resource files ship with the bundle.

Suggestions

Consolidate the detect-trap / oma-market-resolve gate descriptions so each is stated once (e.g., in Structural Flow) and only referenced elsewhere, reducing token redundancy.

Verify the referenced `resources/intent-rules.md`, `resources/frameworks/`, `resources/output-laws.md`, and `resources/execution-protocol.md` files exist in the skill bundle so the signaled references resolve.

Consider a one-line 'When NOT to use' pointer in the body summary to reinforce distinctiveness from oma-search / oma-scholar.

Dimension	Reasoning	Score
Conciseness	Dense and operational with no concept padding, but the detect-trap / resolve gates are restated across Scheduling, Structural Flow, and Failure-and-recovery, giving minor redundancy that could be tightened.	4 / 5
Actionability	Provides fully executable guidance — exact subcommands (`oma market detect-trap`, `oma market resolve --json`, `oma market run`), exit codes (2/4), file paths, and a copy-paste canonical command path with a real example.	5 / 5
Workflow Clarity	A clearly sequenced Entry → Scenes (PREPARE/UPSTREAM/RUN/SYNTHESIZE/FINALIZE) → Exit flow with explicit validation checkpoints (detect-trap gate, resolve ok-check, output-laws self-check) and feedback loops for error recovery.	5 / 5
Progressive Disclosure	Well-structured overview with clearly signaled one-level-deep references (`resources/intent-rules.md`, `resources/frameworks/`, `resources/output-laws.md`, `resources/execution-protocol.md`, upstream SKILL.md) and bulk detail appropriately split out, though no bundle files are present to verify the referenced paths.	4 / 5
	Total	18 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that pairs concrete capabilities with explicit trigger phrases and good synonym coverage. It would score perfectly with a brief negative-scope clause to separate it from oma-search/oma-scholar.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — "pain-point extraction, trend detection, competitor positioning, and discovery" — plus concrete mechanisms (detect-trap preflight, SWOT/Porter's 5F/PESTEL framing, single LAW-compliant brief, delegation via `oma market run`), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (market research via community sources, engine delegation, frameworks, brief) and when (a concrete "Use for ..." trigger list), matching the anchor for a clear what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	The "Use for market research, pain point analysis, trend detection, competitor research, user complaints, voice-of-customer" clause gives comprehensive natural-term coverage including synonyms, and even adds Korean equivalents.	5 / 5
Distinctiveness Conflict Risk	Clear niche (community-signal market research with a named source set and frameworks) with distinct triggers, but "market research" / "web and more" is somewhat broad and the description omits the when-NOT-to-use disambiguation present in the body, leaving minor overlap risk with general search skills.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: first-fluke/oh-my-agent
Path: .agents/skills/oma-market/SKILL.md
Commit: 75b3fbc

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.