Skill

kraken-risk-operations

Enforces operational risk controls for live Kraken trading sessions with dead-man switches, mass cancels, position checks, and failure handling. Use before automating live trades.

Bash

security

automation

npx claudepluginhub krakenfx/kraken-cli

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this skill to reduce live-trading risk during automation.

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Stars489

Forks51

Last CommitMar 10, 2026

Actions

View Source View Plugin View on GitHub View README

kraken-risk-operations

Use this skill to reduce live-trading risk during automation.

Pre-Flight Checklist

Confirm intended environment (paper vs live).
Confirm pair, side, volume, and order type.
Validate payload with --validate.
Enable a dead-man switch for unattended sessions.

Live Session Safety Commands

Dead-man switch:

kraken order cancel-after 60 -o json 2>/dev/null

Mass cancel:

kraken order cancel-all -o json 2>/dev/null
kraken futures cancel-all -o json 2>/dev/null

Position visibility:

kraken open-orders -o json 2>/dev/null
kraken positions -o json 2>/dev/null
kraken futures positions -o json 2>/dev/null

Failure Handling

network: exponential backoff retry
rate_limit: read suggestion and docs_url fields, reduce call frequency or switch to WebSocket
auth: stop and refresh credentials
validation or api: stop, fix request, do not blind retry

Hard Rules

All cancel and cancel-all operations are dangerous. Require explicit human approval before executing.
Dead-man switch (cancel-after) is also dangerous; confirm the timeout value with the user.
Never execute mass-cancel without verifying which orders and positions are open first.