Freqtrade Tools

v1.0.3

Shell aliases and helper commands for Freqtrade (cryptocurrency trading bot) that speed up common tasks. Use when setting up Freqtrade shortcuts, downloading...

0· 148·0 current·0 all-time
byDeonte Cooper@djc00p
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Freqtrade helper aliases) align with the required binaries (docker, docker-compose) and the provided shell/PowerShell/cmd functions, which call docker-compose to run freqtrade tasks like download-data and backtesting.
Instruction Scope
SKILL.md and the reference files only instruct users to copy functions into shell startup files or run the functions; the functions execute docker-compose, open a localhost URL, list local data directories, and validate inputs. They do not read or exfiltrate unrelated files, ask for environment secrets, or contact external endpoints beyond the exchange parameter passed to the freqtrade command (the code uses the --exchange kraken flag but does not reach out itself).
Install Mechanism
No install spec or remote downloads are present; this is instruction-only. Nothing is written to disk by the skill itself—users manually copy definitions into their shell profiles.
Credentials
The skill requests no environment variables or credentials. The use of docker/docker-compose is proportionate to running Freqtrade containerized tasks. No unrelated secrets or config paths are requested.
Persistence & Privilege
Persistence is achieved only if the user copies the functions into their shell/profile; the skill does not auto-install or set always:true. Users should be aware that adding functions to rc/profile is a persistent change to their shell environment.
Assessment
This skill appears coherent and implements exactly what it claims: convenient shell/PowerShell/cmd helpers that invoke docker-compose for Freqtrade. Before installing, copy the functions manually (or review them line-by-line) and back up your ~/.bashrc, ~/.zshrc, $PROFILE, or any startup files you edit. Confirm you have the docker and docker-compose binaries you expect (some systems use the Docker CLI 'docker compose' plugin instead of a separate docker-compose binary). Inspect the project’s docker-compose.yml and the Freqtrade Docker image you run—those determine network access, mounted volumes, and what code actually runs inside containers. Test commands with safe parameters first (e.g., short date ranges, non-destructive flags) and avoid running them with elevated privileges. If you rely on an exchange API key in your Freqtrade setup, keep those credentials out of these helper functions; the skill does not request or store secrets itself.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b9yhgatj6qfhgccs6eaa6mh83vdes

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

Clawdis
OSLinux · macOS · Windows
Binsdocker, docker-compose

Comments