kraken-stop-take-profit
Manage stop-loss and take-profit orders for risk-bounded positions.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- kraken-stop-take-profit
- version
- 1.0.0
- metadata
- { "openclaw": { "category": "finance" }, "requires": { "bins": [ "kraken" ], "skills": [ "kraken-order-types" ] } }
- description
- Manage stop-loss and take-profit orders for risk-bounded positions.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md171 B
- 参考文档TRUST.auto.yaml2.1 KB
03 SKILL.md 正文
kraken-stop-take-profit
Use this skill for:
- placing stop-loss orders to limit downside
- placing take-profit orders to lock in gains
- building bracket orders (entry + stop + target)
- trailing stops that follow a rising price
Simple Stop-Loss
After buying, place a stop-loss below entry:
# Entry
kraken order buy BTCUSD 0.01 --type limit --price 60000 -o json 2>/dev/null
# Stop-loss (triggers market sell if price drops to 57000)
kraken order sell BTCUSD 0.01 --type stop-loss --price 57000 -o json 2>/dev/null
Simple Take-Profit
Place a take-profit above entry:
# Take-profit (triggers market sell if price rises to 65000)
kraken order sell BTCUSD 0.01 --type take-profit --price 65000 -o json 2>/dev/null
Bracket Order (Entry + Stop + Target)
Place all three as separate orders:
# 1. Entry
kraken order buy BTCUSD 0.01 --type limit --price 60000 -o json 2>/dev/null
# 2. Stop-loss
kraken order sell BTCUSD 0.01 --type stop-loss --price 57000 -o json 2>/dev/null
# 3. Take-profit
kraken order sell BTCUSD 0.01 --type take-profit --price 65000 -o json 2>/dev/null
When one exit fills, cancel the other to avoid double exposure:
kraken order cancel <OTHER_TXID> -o json 2>/dev/null
Stop-Loss Limit (Tighter Control)
A stop-loss-limit triggers a limit order instead of market, giving price control but risking no fill in fast moves:
kraken order sell BTCUSD 0.01 --type stop-loss-limit --price 57000 --price2 56800 -o json 2>/dev/null
--price is the trigger, --price2 is the limit price for the resulting order.
Trailing Stop
Follows the market up, sells on reversal:
# Trail $500 below the high
kraken order sell BTCUSD 0.01 --type trailing-stop --price +500 -o json 2>/dev/null
As BTC rises from 60000 to 65000, the stop moves from 59500 to 64500. On a $500 drop from any high, it triggers.
Futures Stop-Loss
kraken futures order sell PF_XBTUSD 1 --type stop --stop-price 57000 --trigger-signal mark --reduce-only -o json 2>/dev/null
Use --trigger-signal mark or index to avoid stop hunts on last-trade wicks. Use --reduce-only to prevent the stop from opening a short.
Management Loop
Monitor stops after placement:
kraken open-orders -o json 2>/dev/null
Stream execution updates to detect when a stop triggers:
kraken ws executions -o json 2>/dev/null
When one side of a bracket fills, immediately cancel the other.
Hard Rules
- Never place live stop/take-profit orders without explicit human approval.
- Always cancel the opposite leg when one side of a bracket fills.
- Use
--reduce-onlyon futures exits to prevent accidental position flips. - Validate spot orders before submission with
--validate. Futures orders have no dry run: rehearse onkraken futures paper, then get approval for the exact command. - If you hit a mismatch between what you are trying to do and the CLI's interface or responses — including a mismatch between this skill and the installed CLI version's contract — feel free to submit feedback with
kraken feedback.
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.