agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/risk-management/risk-reward-ratio/SKILL.md

risk-reward-ratio

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Calculate long/short planned R-multiples and net expectancy. Use when evaluating executable entry, stop, target, win/loss distribution, costs, gaps, and uncertainty without treating R:R as trade quality by itself.

3 other projects use 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

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    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
  1. Very specific:

    Use realized net payoff distributions: E = p × average_win - (1-p) × average_loss - average_costs.

    line 31
  2. Distinctive:

    Define Stop: use thesis invalidation plus a validated tick/volatility buffer, then size from the resulting risk.

    line 37
  3. Distinctive:

    Define Target: use observable structure, time exit, or a tested rule.

    line 39
  4. Distinctive:

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

    line 53
  5. Distinctive:

    Use executable, predeclared targets and stops rather than decorative ratios.

    line 62
  6. Distinctive:

    Avoid selection bias from waiting only for entries that make the displayed ratio attractive.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Risk-Reward Ratio (R:R)

R:R compares potential profit to potential loss, helping filter high-quality trades.

Calculation

For a long: R:R = (Target - Entry) / (Entry - Stop). For a short: R:R = (Entry - Target) / (Stop - Entry). Require positive denominators and use executable prices plus expected slippage/fees.

Example: Entry $100, Stop $95, Target $115 => R:R = $15 / $5 = 3:1.

The zero-cost binary breakeven R:R is (1 - Win Rate) / Win Rate. Actual breakeven is higher after costs, gaps, partial fills, and non-binary exits.

Win RateMinimum R:RBreakeven R:R
40%1.5:11.5:1
50%1:11:1
60%0.7:10.67:1
70%0.5:10.43:1

Expectancy

Use realized net payoff distributions: E = p × average_win - (1-p) × average_loss - average_costs. Report uncertainty, tail loss, sample period, and regime stability. Planned R:R alone does not establish win probability or trade quality.

Optimizing R:R

Improve Entry: Enter at better levels (OTE, pullbacks), wait for confirmation at S/R, use limit orders at key levels.

Define Stop: use thesis invalidation plus a validated tick/volatility buffer, then size from the resulting risk.

Define Target: use observable structure, time exit, or a tested rule; moving a target farther away improves displayed R:R but can reduce hit probability.

Filter on conservative net expectancy, tail risk, liquidity, and mandate fit. Do not label a trade good or excellent from its planned R:R.

Workflow

  1. Identify entry from technical analysis
  2. Set stop loss based on structure or ATR (see stop-loss-strategies)
  3. Calculate R:R using the formula above
  4. Filter -- require positive conservative net expectancy and mandate compliance
  5. Set targets at R:R milestones (1R, 2R, 3R) for partial exits

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: R-multiples describe a planned payoff but do not establish expectancy. Include win probability, costs, gaps, and partial fills; FINRA notes that trading costs persist even with zero commissions.

Key Rules

  • Evaluate win probability and payoff jointly; neither high R:R nor high win rate is sufficient.
  • Use executable, predeclared targets and stops rather than decorative ratios.
  • Avoid selection bias from waiting only for entries that make the displayed ratio attractive.
  • Return no trade when net expectancy, uncertainty, liquidity, or risk limits fail.

Related Skills

  • position-sizing -- R:R determines trade quality; position sizing determines trade quantity
  • stop-loss-strategies -- stop placement defines the risk side of the R:R equation

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.