# Openmobius Skill

Provides multi-school trading Q&A, chart/OHLCV analysis, annotation, and fresh-market...

- Repository: https://github.com/MobiusQuant/OpenMobius-skill (718 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-09-04
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add MobiusQuant/OpenMobius-skill --skill openmobius-skill -g -a claude-code -y`
Codex: `npx skills add MobiusQuant/OpenMobius-skill --skill openmobius-skill -g -a codex -y`
Cursor: `npx skills add MobiusQuant/OpenMobius-skill --skill openmobius-skill -g -a cursor -y`
Gemini CLI: `npx skills add MobiusQuant/OpenMobius-skill --skill openmobius-skill -g -a gemini-cli -y`

## Description

Provides multi-school trading Q&A, chart/OHLCV analysis, annotation, and fresh-market workflows covering ICT/SMC, ChanLun, Wyckoff, Price Action, Order Flow, VSA, and Elliott Wave. Use for trading concepts; capability-discovery questions about available analysis lenses, Schools, models, modes, or data sources; attached charts; pasted OHLCV; chart annotation; or asset-plus-timeframe requests across crypto, stocks, or forex. Defaults unselected market analysis to strict ICT/SMC, honors explicit School/source selectors, and fails closed when no native analyzer exists. Phase 1 comparison is Q&A-only; fetch fresh Mobius Quant API data only after the capability gate.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# OpenMobius-skill, Multi-School Trading Knowledge Skill

A unified skill for four interaction intents with a curated multi-school knowledge base (726 concept cards + 1282 case cards) distilled from 300+ trading videos and live lessons across 12 curated source collections.

**Core principle**: every trading-analysis claim must be grounded in (a)
visible chart evidence or (b) a retrieved knowledge-base rule. Capability
claims must be grounded in the installed inventory and declared profile
contract. **No fabrication**, when uncertain, state so explicitly.

## Freshness mandate, NEVER answer market questions from memory

Any user message that mentions an asset + timeframe, **even without
the word "现在" / "now"**, REQUIRES a fresh `kb_klines.py indicators`
or `kb_klines.py chart` call **in the current turn**. Examples:

- "BTC 1h 怎么样", yes, call API now
- "ETH 现在怎么样", yes
- "茅台日线分析下", yes
- "金子 4 小时", yes
- "BTC 还在跌吗", yes, even though no timeframe given (default to user's
  implied tf or ask), the freshness rule still applies

This live-fetch mandate applies to current-market requests. If the user
explicitly asks to analyze OHLCV they supplied, preserve that snapshot instead
of replacing it with live data; use the parsed-data provenance footer from
`workflows/klines.md` and state that its freshness is not independently
verified.

**Control-plane exception**: a question about which analysis model/School/mode
the installed skill supports, or whether a named School *can* analyze a market,
is capability discovery rather than a request to analyze that market. Route it
to the Q&A capability-discovery branch before applying asset/timeframe rules;
do not fetch market data even when the question names an asset or timeframe.

The rest: https://github.com/MobiusQuant/OpenMobius-skill/blob/HEAD//SKILL.md