← Back to Skills Marketplace
djc00p

Freqtrade US Setup

by Deonte Cooper · GitHub ↗ · v1.0.3 · MIT-0
linuxdarwinwin32 ✓ Security Clean
220
Downloads
0
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install freqtrade-us-setup
Description
Complete setup guide for running Freqtrade (cryptocurrency trading bot) legally in the United States. Use when setting up Freqtrade for the first time, choos...
README (SKILL.md)

Freqtrade US Setup Guide

⚠️ Security First: This guide emphasizes legal, secure setup for US users. Never use VPNs to bypass exchange geo-restrictions — it violates ToS, risks fund freezes, and may be illegal.

1-Minute Intro

Freqtrade (the Python bot) is legal in the US. The catch: many exchanges block US traders. Use Kraken — it's stable, US-compliant, and officially supported.

Quick Start

Step 1: Generate Kraken API Keys

  1. Log into Kraken → Settings → API
  2. Create a new key with these permissions exactly:
    • Funds: Query
    • Orders: Query open orders & trades
    • Orders: Query closed orders & trades
    • Orders: Create & modify orders
    • Orders: Cancel & close orders
    • NEVER enable Withdraw (critical security risk)

Step 2: Docker Setup

# Clone Freqtrade
git clone https://github.com/freqtrade/freqtrade.git
cd freqtrade

# Create config (interactive wizard)
docker-compose run --rm freqtrade new-config --config /freqtrade/user_data/config.json

# When prompted:
# - Exchange: kraken
# - Stake currency: USDT (or USD)
# - Dry-run: yes (always start paper trading!)

Step 3: Secure Your Keys

Freqtrade uses a specific double-underscore env var pattern (FREQTRADE__SECTION__KEY) that overrides config values at runtime. Create a .env file in your Freqtrade directory:

# Kraken API (required)
FREQTRADE__EXCHANGE__KEY=your-kraken-api-key
FREQTRADE__EXCHANGE__SECRET=your-kraken-secret

# Web UI (optional)
FREQTRADE__API_SERVER__USERNAME=your-username
FREQTRADE__API_SERVER__PASSWORD=your-password
FREQTRADE__API_SERVER__JWT__SECRET__KEY=your-jwt-secret
FREQTRADE__API_SERVER__WS__TOKEN=your-ws-token

# Telegram (optional — leave empty if not using)
# Note: Multi-bot Telegram setup via env vars is unverified.
# If you hit issues, consult Freqtrade docs for your specific setup.
# Never hardcode sensitive tokens in files that could be committed to git.
FREQTRADE__TELEGRAM__TOKEN=
FREQTRADE__TELEGRAM__CHAT_ID=

Add to .gitignore immediately:

echo ".env" >> .gitignore

In user_data/config.json, leave the exchange key and secret as empty strings — Freqtrade will populate them from the env vars automatically:

{
  "exchange": {
    "name": "kraken",
    "key": "",
    "secret": "",
    "ccxt_config": {},
    "ccxt_async_config": {}
  },
  "stake_currency": "USDT",
  "dry_run": true,
  "max_open_trades": 3
}

Step 4: Validate & Test

# Download historical data
docker-compose run --rm freqtrade download-data \
  --pairs BTC/USDT ETH/USDT \
  --timeframe 5m \
  --timerange 20240101-

# Run dry-run for 1-2 weeks before going live
docker-compose up

Before Going Live

  1. Dry-run minimum: 1-2 weeks of paper trading
  2. Backtest: Verify your strategy works historically
  3. Start small: Go live with a conservative stake amount
  4. Monitor: Watch closely for first 24-48 hours

When to Read References

  • exchange-comparison.md → Comparing Kraken, Binance.US, Coinbase
  • security-checklist.md → API key management, fund protection, common mistakes

Disclaimer: Freqtrade is open-source, experimental software. Trading involves financial risk. This guide is provided as-is with no guarantees. Use at your own risk.

Questions? See references/ or check Freqtrade's official docs at https://www.freqtrade.io

Usage Guidance
This is an instruction-only guide that appears coherent and focused on safe Freqtrade setup with Kraken. Before using it: (1) verify instructions against Freqtrade and Kraken official docs (links are provided in the guide); (2) ensure Docker is installed from a trusted source; (3) follow the guide's advice to never enable withdraw permissions and to keep .env out of git and rotate keys if leaked; (4) remember the skill author/source is unknown (no homepage), so treat the text as guidance you should cross-check rather than an automated installer; and (5) when running commands (git clone, docker-compose), inspect the upstream repo and docker-compose.yml before launching containers.
Capability Analysis
Type: OpenClaw Skill Name: freqtrade-us-setup Version: 1.0.3 The skill bundle provides a legitimate and security-conscious guide for setting up the Freqtrade trading bot for US users, specifically recommending Kraken. It emphasizes critical security practices such as using minimal API permissions (explicitly advising against enabling withdrawals), storing secrets in environment variables via a `.env` file, and ensuring sensitive files are excluded from version control using `.gitignore`. No malicious code, data exfiltration, or prompt injection attempts were found in SKILL.md or the reference documents.
Capability Tags
cryptorequires-wallet
Capability Assessment
Purpose & Capability
Name/description (Freqtrade US setup) match the content: guides Kraken, Docker, API keys, dry-run testing. Declared dependency (docker) is appropriate and nothing unrelated is requested.
Instruction Scope
SKILL.md stays on-topic: cloning Freqtrade, generating Kraken API keys, populating a local .env, using docker-compose, and testing in dry-run. It does not instruct reading unrelated system files, exfiltrating secrets, or posting keys to external endpoints. It includes sensible security guidance (never enable withdraw, add .env to .gitignore).
Install Mechanism
Instruction-only skill with no install spec and no code files; lowest-risk delivery method. It only references git clone of the official freqtrade repo (GitHub) which is expected for setup instructions.
Credentials
No required environment variables are declared by the registry, and the guide merely instructs the user to create local env vars for the exchange keys and optional UI tokens — appropriate and explained with warnings not to commit them. Nothing asks for unrelated credentials or broad system access.
Persistence & Privilege
always is false and the skill does not request persistent system changes or access to other skills' configs. Model invocation is enabled by default (normal); there are no combined red flags that would make autonomous invocation dangerous here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install freqtrade-us-setup
  3. After installation, invoke the skill by name or use /freqtrade-us-setup
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
Fix: replace bare code blocks with ```text for consistent rendering
v1.0.2
Fix: Clarified crypto-exclusive scope in description
v1.0.1
Fix: Removed false Kraken reversal guarantee, corrected Telegram multi-bot advice (no hardcoding), added experimental software disclaimer
v1.0.0
Initial release — complete guide for US-based Freqtrade users. Covers Kraken setup, correct FREQTRADE__ env var pattern, Docker config, API key security, and dry-run workflow.
Metadata
Slug freqtrade-us-setup
Version 1.0.3
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 4
Frequently Asked Questions

What is Freqtrade US Setup?

Complete setup guide for running Freqtrade (cryptocurrency trading bot) legally in the United States. Use when setting up Freqtrade for the first time, choos... It is an AI Agent Skill for Claude Code / OpenClaw, with 220 downloads so far.

How do I install Freqtrade US Setup?

Run "/install freqtrade-us-setup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Freqtrade US Setup free?

Yes, Freqtrade US Setup is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Freqtrade US Setup support?

Freqtrade US Setup is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).

Who created Freqtrade US Setup?

It is built and maintained by Deonte Cooper (@djc00p); the current version is v1.0.3.

💬 Comments