agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/chart-patterns/wedge-patterns/SKILL.md

wedge-patterns

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Define and test rising or falling wedge resolutions. Use when fitting same-direction converging boundaries and evaluating breakout, retest, invalidation, and measured-move rules.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

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
  1. Distinctive:

    Treat downside resolution as a hypothesis and wait for confirmation

    line 19
  2. Distinctive:

    Treat upside resolution as a hypothesis and wait for confirmation

    line 24
  3. Distinctive:

    Preferred: Wait for breakout + retest of broken trendline.

    line 69
  4. Distinctive:

    Treat the setup as a testable hypothesis, not a prediction.

    line 74

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wedge Pattern Trading

Converging boundaries sloping in the same direction. Reversal versus continuation behavior depends on the specification, context, market, and sample.

Pattern Structure

Rising Wedge (Conventionally Bearish)

  • Both lines slope upward, HH + HL but compressing
  • In uptrend = reversal; in downtrend = continuation
  • Treat downside resolution as a hypothesis and wait for confirmation

Falling Wedge (Conventionally Bullish)

  • Both lines slope downward, LH + LL but compressing
  • In downtrend = reversal; in uptrend = continuation
  • Treat upside resolution as a hypothesis and wait for confirmation
FeatureWedgeTriangle
SlopesBoth lines slope same directionLines converge from opposite directions

Workflow

1. Get Swing Point Data

get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval=<interval>, date=<swing_date>)

2. Draw Wedge Boundaries (2 parallel calls)

Both trendlines slope in the same direction (this is what distinguishes a wedge from a triangle):

# Upper boundary (connecting highs — both slope upward for rising wedge)
draw_chart_analysis(action="create", drawing={
    "type": "trend",
    "points": [
        {"time": <high1_time>, "price": <high1_price>},
        {"time": <high2_time>, "price": <high2_price>}
    ],
    "options": {"text": "Wedge R"}
})

# Lower boundary (connecting lows — also slopes upward for rising wedge)
draw_chart_analysis(action="create", drawing={
    "type": "trend",
    "points": [
        {"time": <low1_time>, "price": <low1_price>},
        {"time": <low2_time>, "price": <low2_price>}
    ],
    "options": {"text": "Wedge S"}
})

3. Confirm and Enter

Confirm declining volume with get_indicators(indicator_code="mfi", symbol=<symbol>, exchange=<exchange>, interval=<interval>).

Standard: Rising wedge → short on downside break. Falling wedge → long on upside break. Volume spike confirms. Stop beyond opposite boundary. Preferred: Wait for breakout + retest of broken trendline. Enter on rejection. Target: Height at widest part of wedge, projected from breakout.

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 making visual patterns algorithmic and testing them conditionally; it does not support a fixed breakout probability.

Key Rules

  • Minimum 4 touch points (2 per line) to validate
  • Both trendlines MUST slope in the same direction — otherwise it's a triangle
  • Record preceding direction and test reversal/continuation outcomes separately; context does not determine the result.
  • Define “extended trend” and volume contraction quantitatively if they are used as filters

Related Skills

  • triangle-patterns — Similar converging lines but different slope behavior
  • multi-timeframe-analysis — HTF wedges signal major reversals

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.