Skill

kraken-subaccount-ops

Creates and manages Kraken subaccounts via CLI, transfers funds between accounts, and controls futures trading status for strategy isolation and risk management.

Bash

automation

cli-tools

npx claudepluginhub krakenfx/kraken-cli

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this skill for:

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 6, 2026

Actions

View Source View Plugin View on GitHub View README

kraken-subaccount-ops

Use this skill for:

creating subaccounts for strategy isolation
transferring funds between main and subaccounts
managing futures subaccount trading status
isolating risk across multiple strategies

Why Subaccounts

Subaccounts isolate balances and positions. Use them to:

Run different strategies with separate capital pools.
Limit risk exposure per strategy.
Track P&L per strategy independently.
Give different agents access to different subaccounts with restricted API keys.

Create a Subaccount

kraken subaccount create "dca-bot" "dca-bot@example.com" -o json 2>/dev/null

Transfer Between Accounts

Move funds from main account to subaccount (requires human approval):

kraken subaccount transfer USD 5000 --from <MAIN_IIBAN> --to <SUB_IIBAN> -o json 2>/dev/null

Move funds back:

kraken subaccount transfer USD 5000 --from <SUB_IIBAN> --to <MAIN_IIBAN> -o json 2>/dev/null

Futures Subaccounts

List futures subaccounts:

kraken futures subaccounts -o json 2>/dev/null

Check subaccount trading status:

kraken futures subaccount-status <UID> -o json 2>/dev/null

Enable or disable trading for a subaccount:

kraken futures set-subaccount-status <UID> true -o json 2>/dev/null
kraken futures set-subaccount-status <UID> false -o json 2>/dev/null

Transfer between futures wallets:

kraken futures wallet-transfer <FROM_WALLET> <TO_WALLET> USD 1000 -o json 2>/dev/null

Strategy Isolation Pattern

Create a subaccount per strategy (e.g., "grid-btc", "dca-eth").
Allocate capital to each subaccount.
Configure separate API keys per subaccount with minimum required permissions.
Each agent operates only within its assigned subaccount.
The main account retains reserve capital not allocated to any strategy.

Monitoring

Check all balances from the main account to see aggregate state. Individual subaccount balances are visible through their respective API keys.

For centralized monitoring, use the main account's credentials with query permissions across subaccounts.

Hard Rules

Subaccount transfers are flagged as dangerous. Never execute without explicit human approval.
Never share API keys across subaccounts; create separate keys per subaccount.
Verify IIBAN values before initiating transfers; incorrect IIBANs will fail.
Disable futures trading on subaccounts that should not trade futures.