- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-market -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-market -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-market -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-market -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/first-fluke/oh-my-agent/tree/HEAD/.agents/skills/oma-marketDe l'éditeur
Run the installed upstream last30days research engine 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/.
--days 7|30|90|180)--discover), person mode, hiring signals (--hiring-signals), follow-up drills (--drill)oma schedule <action> wrapping this skill--intent pain|trend|competitor|discovery (else classified per resources/intent-rules.md)--days), --vs <entity> (competitor), --frameworks auto|none|swot,5f,pestelengine.skillMd) — passed through verbatim.agents/results/market/{topic-slug}-{YYYYMMDD}.md🌐 last30days v{VERSION} · synced {date}); body per the upstream OUTPUT CONTRACT; framework sections per intent after the body; engine footer lastmarket.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
No CLI gate reads this block for oma-market (oma verify checks outputs: only for agent-type skills); the self-check in resources/output-laws.md enforces the brief.
oma market resolve / oma market run — engine location, Python 3.12+ resolution, --save-dir defaultoma market detect-trap <topic> — preflight gateoma market update — installs the last30days skill when missing, otherwise runs bunx skills update last30days -g -ylast30days: oma market resolve reads installed skill dirs such as ~/.agents/skills/last30days/ (a market.path / LAST30DAYS_HOME pin wins)SKILL.md at the resolved engine root (skillMd in oma market resolve --json) — the authoritative research contractresources/intent-rules.md, resources/frameworks/, resources/output-laws.md, resources/execution-protocol.md--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.--force only on explicit user reconfirmation.oma market resolve not ok → stop with the reason; no engine run.oma market resolve stops before the upstream setup wizard. Relay its install hint; after an authorized interpreter installation, retry resolution. Do not expect the skipped upstream Python preflight to install it.oma market detect-trap "<topic>" before anything else. Exit 2 → surface the REFUSE reason and reframe suggestion, stop. Exit 4 → invalid topic, stop.oma market resolve --json. It is ok when the engine is present and Python ≥ 3.12 is found on PATH, via uv, or pinned with market.python / LAST30DAYS_PYTHON. ok: false → report reason (missing engine → ask the user, then oma market update; missing Python → the install hint) and stop.engine.skillMd top to bottom. It is long by design; do not skim. Treat engine.root as its SKILL_DIR.resources/intent-rules.md; map to engine flags and framework set. Record the intent, flags, and frameworks with subject market.route-selection per ../_shared/runtime/route-selection.md (explicit flag, --vs, or the keyword score that decided it).oma market run already resolved the interpreter."${LAST30DAYS_PYTHON}" "${SKILL_DIR}/scripts/last30days.py" <args>, run oma market run <args> with the same arguments (foreground, 5-minute timeout, --emit=compact); it passes them through to the resolved upstream engine's Python entry point. --save-dir is added automatically from market.save_dir unless you pass one.resources/frameworks/)..agents/results/market/{topic-slug}-{YYYYMMDD}.md, run the self-check in resources/output-laws.md against the written file, fix and re-check, then preview the first 50 lines.TOPIC="VS Code pain points"
oma market detect-trap "$TOPIC"
oma market resolve --json # read .engine.skillMd, then follow it
# … upstream Steps 0 / 0.45 / 0.5 / 0.55 / 0.75 …
oma market run "$TOPIC" --plan "$QUERY_PLAN_FILE" --subreddits=vscode --emit=compact --save-suffix=v3
.agents/results/market/{topic-slug}-{YYYYMMDD}.md and raw engine files to market.save_dir.~/.config/last30days/.env with user consent; ~/.config/last30days/ holds the engine config and keys.oma market run starts the resolved upstream Python entry point.oma market update.resources/execution-protocol.mdresources/intent-rules.mdresources/output-laws.mdresources/frameworks/swot.md, resources/frameworks/porters-5f.md, or resources/frameworks/pestel.md (load only the selected framework)resources/checklist.mdresources/error-playbook.mdengine.skillMd path from oma market resolve --json; upstream scripts belong to the installed engine, not to this skill's resources.Research customer pain points, trends, and competitors through the OMA market engine. Use for market discovery or voice-of-customer analysis.
---name: oma-marketdescription: Research customer pain points, trends, and competitors through the OMA market engine. Use for market discovery…---# .agents/skills/oma-market/SKILL.mdFAQ
Téléchargez .agents/skills/oma-market/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/first-fluke/oh-my-agent.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.