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.

23 stars

byjiayaoqijia

View on GitHub Installation ↓

Best use case

openclaw_kraken is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using openclaw_kraken 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

$curl -o ~/.claude/skills/kraken-spot/SKILL.md --create-dirs "https://raw.githubusercontent.com/jiayaoqijia/cryptoskill/main/skills/exchanges/kraken-spot/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/kraken-spot/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How openclaw_kraken Compares

Feature / Agent	openclaw_kraken	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?

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.

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

# OpenClaw Kraken

Use `{baseDir}/bin/openclaw-kraken` for Kraken Spot REST tasks.

## Use when

- The user wants Kraken market data.
- The user wants Kraken account state from private REST endpoints.
- The user wants guarded order placement, funding, earn, futures, subaccount, or websocket actions through a local Bash tool instead of ad hoc curl commands.

## Rules

- Never print API secrets, signatures, or raw auth headers.
- Read secrets from the environment only. In OpenClaw, inject them via secret refs rather than plaintext config.
- Refuse to run if required config is missing or malformed.
- Use configured base URLs only. Do not accept arbitrary destination URLs.
- Preserve stdout for API results; use `--jq` or `--compact` when structured formatting is needed.
- Prefer read-only endpoints unless the user clearly asked for a state-changing action.
- For state-changing aliases such as trading, withdrawal, earn allocation, or subaccount transfer operations, require `--confirm`.

## Commands

- `market time`
- `market ticker --pair XBTUSD`
- `account balance`
- `funding deposit-methods --asset ETH`
- `earn strategies --ascending true`
- `futures call market.tickers`
- `ws spot-public --message-json '{"method":"ping"}'`
- `orders add --pair XBTUSD --side buy --type limit --volume 0.01 --price 25000 --time-in-force GTC --post-only true --confirm`
- `call funding.withdraw-info --asset ETH --key MyWallet --amount 0.5`

## Configuration

- Non-secret config is read from environment or `OPENCLAW_KRAKEN_CONFIG`.
- Secrets must be provided via environment variables that OpenClaw resolves from secret refs.
- See `{baseDir}/README.md` for examples.