triangle-patterns
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Trade ascending, descending, and symmetrical triangle patterns. Use when anticipating breakouts from consolidation, measuring potential move targets, or timing entries on compression 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★ 073% 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
- double-top-bottomSkill
- flag-pennantSkill
- head-and-shouldersSkill
- 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
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 63
Check volume declining during formation via get_indicators(indicator_code="mfi", symbol=<symbol>, exchange=<exchange>, interval=<interval>).
- Distinctive: line 66
Preferred: Wait for breakout, then retest of broken trendline.
- Distinctive: line 77
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 85
NEVER enter on a wick breakout alone — wait for candle close outside
- Distinctive: line 86
If using trend direction or apex timing as filters, freeze their definitions and verify their incremental net expectancy
≈ “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
Triangle Pattern Trading
Triangles describe converging swing boundaries. Treat breakout direction as unknown until price closes beyond a boundary.
Pattern Structure
Ascending Triangle (Bullish Bias)
- Flat horizontal resistance + rising lows — bullish bias is a hypothesis
Descending Triangle (Bearish Bias)
- Flat horizontal support + lower highs — bearish bias is a hypothesis
Symmetrical Triangle (Neutral)
- Lower highs + higher lows, converging — condition results on trend rather than assuming direction
Workflow
1. Get Swing Point Data
Identify at least 2 swing highs and 2 swing lows (4+ total touch points):
get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval=<interval>, date=<swing_date>)2. Draw Converging Trendlines (2 parallel calls)
# Upper trendline (connecting swing highs)
draw_chart_analysis(action="create", drawing={
"type": "trend",
"points": [
{"time": <high1_time>, "price": <high1_price>},
{"time": <high2_time>, "price": <high2_price>}
],
"options": {"text": "Triangle R"}
})
# Lower trendline (connecting swing lows)
draw_chart_analysis(action="create", drawing={
"type": "trend",
"points": [
{"time": <low1_time>, "price": <low1_price>},
{"time": <low2_time>, "price": <low2_price>}
],
"options": {"text": "Triangle S"}
})For ascending: upper line is flat (resistance type instead of trend). For descending: lower line is flat (support type).
3. Confirm and Enter
Check volume declining during formation via get_indicators(indicator_code="mfi", symbol=<symbol>, exchange=<exchange>, interval=<interval>).
Standard: Enter on break + candle close outside triangle with volume spike. Stop inside triangle on opposite side. Preferred: Wait for breakout, then retest of broken trendline. Enter on rejection. Target: Triangle height at widest point, projected from breakout.
| Phase | Expected Volume |
| Formation | Declining |
| Breakout | Spike |
| Continuation | Sustained |
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 supports systematic pattern recognition; direction, breakout buffer, and target rules still require out-of-sample calibration.
Key Rules
- Minimum 4 touch points (2 per trendline) to validate
- NEVER enter on a wick breakout alone — wait for candle close outside
- If using trend direction or apex timing as filters, freeze their definitions and verify their incremental net expectancy
- Report width in ATR units and breakout location as a fraction of time-to-apex; do not infer strength from width alone
Related Skills
- wedge-patterns — Similar converging lines, both slope same direction
- flag-pennant — Pennants are small symmetrical triangles
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.

