BacktestBot
PassAudited by ClawScan on May 1, 2026.
Overview
BacktestBot appears to be a coherent instruction-only backtesting helper; the main things to notice are its required API key, limited provider provenance, and optional local data cache.
This skill looks safe to install from the provided artifacts, but verify the BacktestBot provider before supplying an API key, use a scoped key if possible, and be aware that historical data may be cached locally.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may use the BacktestBot key to make authenticated backtesting and data requests, which could consume quota or expose submitted strategy inputs to that service.
The skill requires a service API key, which is sensitive account authority, but its use is disclosed and aligned with the backtesting purpose.
`BACKTESTBOT_API_KEY` — API key for BacktestBot. Used to authenticate requests for historical OHLCV data, strategy simulations, and performance metrics.
Use a dedicated or scoped BacktestBot key if available, monitor usage, and avoid providing live brokerage or unrelated financial credentials.
Before trusting the service with an API key or strategy details, the user has less information to verify who operates it.
The artifacts do not provide a source repository or homepage to verify the BacktestBot service provenance, although there is no code or install step present.
Source: unknown; Homepage: none
Verify the BacktestBot provider through trusted channels before entering credentials or submitting proprietary strategies.
Cached data may take local disk space and could affect later backtests if it becomes stale or incorrect.
The skill may persist cached historical market data locally for reuse, which is disclosed and scoped but worth noticing.
`BACKTESTBOT_DATA_DIR` — (optional) local directory for cached historical data. Defaults to `~/.backtestbot/data`.
Set the cache directory intentionally, clear it when needed, and be cautious when relying on cached data for financial analysis.