market-accumulation
Skill3 starsChanged 4 months agoMITView on GitHub
Detects whether smart money is positioning by composing L1 indicators: spring/shakeout, absorption, sign of strength, reaccumulation, and low volatility after distribution. Classifications: SPRING, REACCUMULATION, DISTRIBUTION, UTAD.
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-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-breakout-confirmSkill
- strategy-exhaustion-fadeSkill
- strategy-fitness-heatmapSkill
- strategy-funding-carrySkill
- strategy-liquidity-sweepSkill
- strategy-mean-reversionSkill
- strategy-trend-followSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Do not trade a SPRING/REACCUMULATION signal as a standalone entry — confirm trend quality via market-trend-quality so you are not catching …
- Very specific: line 71
When the primary trigger isn't met (specifically: fewer than 2 sub-signals present, or weighted_sum <= 0.30) but a known combination of …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
market-accumulation
L2 pattern detection skill that composes L1 indicators to determine whether smart money is accumulating a position.
When NOT to use
- This is pattern detection, not a trade idea — feed a fired pattern into an L3 strategy (
strategy-accumulation-swing) orrun-all-l3before acting. - Do not trade a
SPRING/REACCUMULATIONsignal as a standalone entry — confirm trend quality viamarket-trend-qualityso you are not catching a falling knife. - Pattern is unreliable on choppy/low-volume tape where sub-signals fire sporadically; require a clean trend context (see
market-trend) before treating it as actionable.
Quick Start
uv run skills/market-accumulation/scripts/run.py SPY
uv run skills/market-accumulation/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.
Sub-Signals
| Sub-signal | Weight | Source L1 |
| Spring/shakeout (dip below support + reclaim) | 0.30 | market-s-r + market-volume |
| Absorption (high volume, flat price) | 0.20 | market-volume + market-volatility |
| Sign of strength (high vol up after basing) | 0.20 | market-volume + market-trend |
| Reaccumulation (after initial markup) | 0.15 | market-trend |
| Low volatility after distribution | 0.15 | market-volatility |
Classifications
- SPRING: Spring/shakeout + absorption — price faked below support then reclaimed with volume
- REACCUMULATION: Reaccumulation + sign of strength — pullback in uptrend with institutional buying
- DISTRIBUTION: Sign of strength + absorption with bearish trend — smart money distributing
- UTAD: Low volatility after prior high volatility — upthrust after distribution
Trigger
pattern.present is True when at least 2 sub-signals are present AND their
combined weight exceeds 0.30. The previous weighted_sum / total_weight >= 0.4
threshold silently dropped 2-sub combinations at weighted_sum in
(0.30, 0.40) — e.g. absorption + reaccumulation, sign_of_strength +
low_vol_after_distribution, absorption + low_vol_after_distribution
(each wsum 0.35) — into present=False while the sub-signals were populated.
confidence is round(weighted_sum * 5), clamped to [1, 5].
Recognized sub-shapes
When the primary trigger isn't met (specifically: fewer than 2 sub-signals
present, or weighted_sum <= 0.30) but a known combination of sub-signals is
firing, the classifier falls back to a recognized sub-shape. This catches
2-sub combos at the weighted_sum = 0.30 boundary — e.g.
reaccumulation + low_vol_after_distribution (wsum 0.30) where two
corroborating L1s are meaningful.
| Sub-shape | Sub-signals required | Classification |
| Reaccumulation + low vol after distribution | reaccumulation + low_vol_after_distribution | REACCUMULATION |
Output
Returns pattern presence, confidence (1-5), classification, sub-signal states, input scores from each L1, and a one-sentence narrative.
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.

