Real Skill packageSource verifiedClawHub registry

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, choosing a US-compatible exchange, configuring API keys securely, or troubleshooting US-specific exchange issues. Covers Kraken setup, Docker configuration, API key security, and dry-run testing. Trigger phrases: freqtrade US, US exchanges freqtrade, freqtrade legal US, freqtrade Kraken setup, freqtrade docker config.

Identity and source

Publisher attributionDeonte Cooperregistry owner unverified by skillvetai
Functional categorySoftware Developmentautomatically inferred · 64% rule confidence
Package forminstruction bundle5 recorded files
Canonical sourceClawHub registryclawhub:djc00p:freqtrade-us-setup
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 11/5/2026.claude/skills/freqtrade-us-setup

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 11/5/2026.agents/skills/freqtrade-us-setup

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 11/5/2026skills/freqtrade-us-setup

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @djc00p/freqtrade-us-setup
clawhub inspect @djc00p/freqtrade-us-setup --version 1.0.5

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
5 / 5 inspected as text
Checked
11/5/2026, 6:40:25 AM
Scanner
0.1.3
Policy
1.0.3
2 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
5 dependency and API indicators
  • api: clawhub.ai
  • api: docs.kraken.com
  • api: github.com
  • api: support.kraken.com
  • api: www.freqtrade.io
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
11/5/2026, 4:36:07 AM
Release binding
Matches this record
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:7f40238d19bce818ccaa7c03449d53709a698340504bea8053f9dd9f6b0423f8
Show up to 5 recorded paths
  • _meta.json
  • references/exchange-comparison.md
  • references/security-checklist.md
  • skill-card.md
  • SKILL.md

Source changelog

Fix: resolve contradictory install and credential guidance. The Quick Start now clones a pinned release tag instead of the unpinned default branch, matching the safety section. docker-compose.yml now references exchange keys via ${...} instead of hardcoded values, and the security checklist no longer presents hardcoded keys as the recommended pattern. Adds an explicit note that a withdrawal-disabled key still permits trading losses, plus a link to Kraken's API key security guidance.

Release security diff

mediumCompared fixed releases 1.0.4 and 1.0.5; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • dependency surface changed
  • file surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.0.411/4/2026sha256:2cf1551f39635a2f7865391f834796409eca959cf2709f45b96f516550443816