strategy-breakout-confirm
Skill3 starsChanged 4 months agoMITView on GitHub
L3 momentum strategy. Enters confirmed breakouts with volume and squeeze confirmation. Composes breakout, volume, and squeeze.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- beadsSkill
- backtest-engineSkill
- backtest-pipelineSkill
- backtest-trend-minerSkill
- bug-scanSkill
- daily-trade-pickSkill
- execution-kraken-perpsSkill
- execution-kraken-spotSkill
- l3-conviction-scanSkill
- market-accumulationSkill
- market-basisSkill
- market-breadthSkill
- market-breakoutSkill
- market-emaSkill
- market-exhaustionSkill
- market-fibonacciSkill
- market-liquidity-sweepSkill
- market-macdSkill
- market-macroSkill
- market-moversSkill
- market-notesSkill
- market-overviewSkill
- market-rsiSkill
- market-snapshotSkill
- market-squeezeSkill
- market-s-rSkill
- market-stateSkill
- market-trend-qualitySkill
- market-trendSkill
- market-valuationSkill
- market-volatilitySkill
- market-volumeSkill
- market-watchlistSkill
- portfolio-mgmtSkill
- position-watchdogSkill
- risk-engineSkill
- run-all-l2Skill
- run-all-l3Skill
- run-watchlistSkill
- strategy-accumulation-swingSkill
- strategy-exhaustion-fadeSkill
- strategy-fitness-heatmapSkill
- strategy-funding-carrySkill
- strategy-liquidity-sweepSkill
- strategy-mean-reversionSkill
- strategy-trend-followSkill
The file
Files
strategy-breakout-confirm
L3 momentum strategy that only enters breakouts when volume confirms and squeeze is firing. Filters out fakeouts.
When NOT to use
- Without a mandatory
risk-enginevet before execution — this skill emits ideas, not orders. Always vet the Intent and get explicit user approval. - In low-volume or choppy tape — even with its volume/squeeze filter, breakouts fake out often; do not over-trust a single confirmed breakout without trend context.
- For a single-indicator read — it composes
market-breakout+market-volume+market-squeeze; call those directly if you only want the pattern.
Quick Start
uv run skills/strategy-breakout-confirm/scripts/run.py SPY
uv run skills/strategy-breakout-confirm/scripts/run.py SPY --jsonFlags
| Flag | Default | Notes |
TICKER (positional) | — | Required. Supports provider:ticker (e.g. hl:LIT, yf:AAPL). |
--json | human | Emit JSON to stdout. |
--source=PROVIDER | auto-detect | Force a data provider (see README). |
--interval=INTERVAL | 1d | 1m/2m/5m/15m/30m/1h/2h/4h/8h/12h/1d/3d/1wk/1M. |
--period=PERIOD | 1y | 1d/5d/1mo/3mo/6mo/1y/2y/5y/10y/ytd/max. |
Both timeframe flags are validated — bad values exit 2 with a friendly error. For intraday (--interval=1h), bump --period to 6mo or 1y; yfinance caps hourly at ~2y and anything sub-hour at ~60d.
Composes
| L2 Skill | Purpose |
| market-breakout | Detect breakout with type + confirmation |
| market-volume | Volume confirmation and OBV trend |
| market-squeeze | Squeeze momentum direction |
Entry Logic
- Long: breakout confirmed + volume_ratio > 1.2 + squeeze bullish
- Short: breakdown confirmed + volume_ratio > 1.2 + squeeze bearish
- Stop: below breakout level (long) / above (short) — ~1.5 ATR
- Targets: next S/R level, 2x ATR
Output
ideas[]— trade ideas with direction, conviction, entry/stop/target, reasoning- Each idea carries
version: "v1".."v5"derived fromconvictionviaanalysis.contracts.conviction_version() - Each idea carries
take_profit_ideal(unrounded construction) andrr_to_tp: [rr_to_tp1, rr_to_tp2, rr_to_tp3](precomputed R:R to each TP viaanalysis.contracts.compute_rr_to_tp()) so consumers can read a canonical R:R without reimplementing the direction-asymmetric formula - Each idea is validated against
validate_l3_tp_ladder()(TP3 ≥ entry × 1.05 long, or ≤ entry × 0.95 short)
- Each idea carries
narrative— summary for user briefing
Output envelope (AXI)
--json output follows the canonical AXI envelope — {data, count, errors, help[]}. Default schema is the per-skill minimal fields (3-6 essentials); pass --fields=<csv> to project or --full for the full payload. count is the item count, help[] is contextual next-step command templates. Lib.py return shapes (L1Result / L2Result / L3Result / L3Idea / RegimeSignal) are unchanged — the envelope wraps them at the scripts/run.py boundary.
Home view (no-arg mode)
No-arg mode prints the home view from $XDG_DATA_HOME/market-skills/<skill>_last.json (last successful run). Errors are not cached.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

