kraken-stop-take-profit
Manage stop-loss and take-profit orders for risk-bounded positions.
Best use case
kraken-stop-take-profit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage stop-loss and take-profit orders for risk-bounded positions.
Teams using kraken-stop-take-profit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/kraken-official-stop-take-profit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How kraken-stop-take-profit Compares
| Feature / Agent | kraken-stop-take-profit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage stop-loss and take-profit orders for risk-bounded positions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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: ```bash # 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: ```bash # 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: ```bash # 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: ```bash 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: ```bash 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: ```bash # 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 ```bash 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: ```bash kraken open-orders -o json 2>/dev/null ``` Stream execution updates to detect when a stop triggers: ```bash 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-only` on futures exits to prevent accidental position flips. - Validate all orders before submission with `--validate`.
Related Skills
Kraken Crypto Skill
Use the kraken_cli.py wrapper to query your Kraken account.
openclaw_kraken
Use a Bash CLI to query Kraken Spot and Futures APIs, inspect account state, run guarded trading and funding actions, and work with Kraken websocket payloads using OpenClaw-managed secrets.
kraken-ws-streaming
Real-time data streaming via WebSocket for spot and futures.
kraken-twap-execution
Execute large orders as time-weighted slices to reduce market impact.
kraken-tax-export
Export trade history, ledgers, and cost basis data for tax reporting.
kraken-subaccount-ops
Create and manage subaccounts with inter-account transfers.
kraken-spot-execution
Execute spot orders with validation, confirmation gates, and post-trade checks.
kraken-shared
Shared runtime contract for kraken-cli: auth, invocation, parsing, and safety.
kraken-risk-operations
Operational risk controls for live agent trading sessions.
recipe-trailing-stop-runner
Ride a trend with a trailing stop that locks in profits on reversal.
kraken-rebalancing
Portfolio rebalancing to maintain target allocations across assets.
kraken-rate-limits
Understand Kraken API rate limits and adapt agent behavior when limits are hit.