double-top-bottom
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Trade double and triple top/bottom reversal patterns. Use when identifying trend exhaustion, finding reversal entries at key resistance/support, or confirming failed breakouts.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilledited, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- IngAs8/ClaudeSkill★ 074% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- candlestick-patternsSkill
- channel-tradingSkill
- cup-and-handleSkill
- flag-pennantSkill
- head-and-shouldersSkill
- triangle-patternsSkill
- wedge-patternsSkill
- altcoin-rotationSkill
- arbitrage-tradingSkill
- dca-strategySkill
- funding-rate-tradingSkill
- on-chain-analysisSkill
- breakout-tradingSkill
- gap-tradingSkill
- momentum-tradingSkill
- news-tradingSkill
- pullback-tradingSkill
- range-tradingSkill
- scalping-strategySkill
- earnings-tradingSkill
- economic-calendar-tradingSkill
- insider-activity-tradingSkill
- market-correlation-tradingSkill
- sector-rotationSkill
- sentiment-analysisSkill
- breaker-blocksSkill
- fair-value-gapsSkill
- kill-zonesSkill
- liquidity-zonesSkill
- market-structure-shiftSkill
- optimal-trade-entrySkill
- order-blocksSkill
- premium-discountSkill
- correlation-riskSkill
- drawdown-managementSkill
- leverage-managementSkill
- partial-profit-takingSkill
- position-sizingSkill
- risk-reward-ratioSkill
- stop-loss-strategiesSkill
- trailing-stopSkill
- bollinger-bandsSkill
- divergence-tradingSkill
- fibonacci-tradingSkill
- ichimoku-cloudSkill
- macd-tradingSkill
- market-regime-detectionSkill
- mean-reversionSkill
- moving-average-crossoverSkill
- multi-timeframe-analysisSkill
- rsi-divergenceSkill
- stochastic-tradingSkill
- supply-demand-zonesSkill
- volume-profile-tradingSkill
- vwap-tradingSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 70
Preferred: Wait for break + neckline retest.
- Distinctive: line 76
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 83
NEVER trade before neckline confirmation — pattern incomplete until it breaks
- Distinctive: line 84
Treat declining activity on the second test as context, not validation by itself
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Double Top & Bottom Patterns
Reversal patterns that form when price fails to break a level twice.
Pattern Structure
Double Top (Bearish)
- Rally to resistance (Peak 1) → pullback to neckline → retest the resistance within a predeclared price or ATR tolerance → failure
Double Bottom (Bullish)
- Drop to support (Trough 1) → bounce to neckline → retest the support within the same frozen tolerance → failure
| Factor | Strong | Weak |
| Time between tests | Within a predeclared bar window | Selected after seeing outcome |
| Volume | Declining on 2nd test | Higher on 2nd test |
| Peak/trough alignment | Within a volatility-normalized tolerance | Arbitrary visual match |
Workflow
1. Get Exact Data
get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval=<interval>, date=<peak_date>)2. Mark Peaks/Troughs (2 parallel highlight calls)
draw_chart_analysis(action="create", drawing={
"type": "highlight",
"points": [{"time": <peak1_time>, "price": <peak1_price>}],
"options": {"text": "Peak 1"}
})
draw_chart_analysis(action="create", drawing={
"type": "highlight",
"points": [{"time": <peak2_time>, "price": <peak2_price>}],
"options": {"text": "Peak 2"}
})3. Draw Neckline
draw_chart_analysis(action="create", drawing={
"type": "support",
"points": [
{"time": <neckline_start>, "price": <neckline_price>},
{"time": <neckline_end>, "price": <neckline_price>}
],
"options": {"text": "Neckline"}
})For double top use "support" (neckline is below). For double bottom use "resistance" (neckline is above).
4. Enter
Standard: Enter on neckline break + close with volume. Stop beyond peaks/troughs. Preferred: Wait for break + neckline retest. Enter on rejection. Aggressive: Enter at second peak/trough with LTF reversal confirmation. Target: Neckline ± (Peak - Neckline). Example: Peak $100, Neckline $90 → Target $80.
Evidence and Validation
- Treat the setup as a testable hypothesis, not a prediction. Define thresholds, entry, invalidation, and exit before evaluating outcomes.
- Calibrate on the same instrument, venue, session, and timeframe. Use closed candles and a held-out or walk-forward sample; record every variant tried.
- Include spread, fees, slippage, borrow or funding, partial fills, and latency. Reject the setup when net expectancy is not positive or depends on one narrow parameter.
- Return observed inputs, missing data, cost assumptions, entry, invalidation, exit, and a valid, watch, or no-trade status.
- Research basis: Lo, Mamaysky & Wang found incremental information in some algorithmically defined patterns, including double bottoms, but did not establish universal thresholds or profits.
Key Rules
- NEVER trade before neckline confirmation — pattern incomplete until it breaks
- Treat declining activity on the second test as context, not validation by itself
- Freeze the peak/trough tolerance and bar window before evaluating returns
- Failed double tops/bottoms lead to strong continuation moves
Related Skills
- head-and-shoulders — Similar reversal family
- cup-and-handle — Failed double bottoms can morph into cup patterns
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.

