katbot-trading
Enables live crypto trading on Hyperliquid with AI-driven market analysis, token selection, and trade execution via Katbot.ai.
Install this skill
Security score
The katbot-trading skill was audited on May 15, 2026 and we found 18 security issues across 2 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Access to hidden dotfiles in home directory
| 65 | The `bmi_alert.py` script reads `~/.openclaw/workspace/portfolio_tokens.json` to include specific token performance in the alert message. |
Access to hidden dotfiles in home directory
| 80 | | `KATBOT_IDENTITY_DIR` | Optional override | Path to identity files directory. Default: `~/.openclaw/workspace/katbot-identity` | |
Access to hidden dotfiles in home directory
| 102 | All persistent credentials are stored in `KATBOT_IDENTITY_DIR` (default: `~/.openclaw/workspace/katbot-identity/`). This directory is **outside the project tree** deliberately — its contents are never |
Access to hidden dotfiles in home directory
| 115 | - If `~/.openclaw/workspace/katbot-identity/` is compromised, an attacker gains the agent trading key and session tokens but **not** the MetaMask wallet key, limiting the blast radius to funds accessi |
Access to hidden dotfiles in home directory
| 379 | 4. Save `KATBOT_HL_AGENT_PRIVATE_KEY`, `katbot_config.json`, and `katbot_token.json` to `~/.openclaw/workspace/katbot-identity/`. |
Access to hidden dotfiles in home directory
| 393 | No re-onboarding is needed for upgrades. The identity files in `~/.openclaw/workspace/katbot-identity/` are preserved across upgrades. If a tool fails after upgrade, run `ensure_env.sh` first. |
Access to .env file
| 85 | ### `.env` File Loader — CLI/Development Use Only |
Access to .env file
| 87 | `katbot_client.py` contains a `.env` file loader for CLI use outside OpenClaw (`tubman-bobtail-py` mode). At import time it searches these paths for a `katbot_client.env` file: |
Access to .env file
| 89 | 1. `{projectRoot}/env/local/katbot_client.env` |
Access to .env file
| 90 | 2. `{baseDir}/../env/local/katbot_client.env` |
Access to .env file
| 91 | 3. `{baseDir}/tools/katbot_client.env` |
Access to .env file
| 93 | If a file is found, it loads **only non-secret config** from it: `KATBOT_BASE_URL`, `KATBOT_IDENTITY_DIR`, and `CHAIN_ID`. Private keys (`WALLET_PRIVATE_KEY` and `KATBOT_HL_AGENT_PRIVATE_KEY`) are exp |
Access to .env file
| 96 | - **NEVER** create or suggest creating a `katbot_client.env` containing private keys. |
Access to .env file
| 97 | - **NEVER** place `WALLET_PRIVATE_KEY` or `KATBOT_HL_AGENT_PRIVATE_KEY` in any `.env` file. |
Access to .env file
| 98 | - A `katbot_client.env` is acceptable only for non-secret config (`KATBOT_BASE_URL`, `CHAIN_ID`, `KATBOT_IDENTITY_DIR`, `PORTFOLIO_ID`, `WALLET_ADDRESS`). |
Access to .env file
| 311 | `katbot_client.py` can be run as a standalone script (reads `PORTFOLIO_ID` from `.env` or environment): |
Access to .env file
| 345 | - **NEVER** create a `katbot_client.env` file containing `WALLET_PRIVATE_KEY` or `KATBOT_HL_AGENT_PRIVATE_KEY`. The `.env` loader will not inject private keys into the process, but placing them in suc |
External URL reference
| 79 | | `KATBOT_BASE_URL` | Optional override | API base URL. Default: `https://api.katbot.ai` | |