
from tradecat937
Operate and inspect the TradeCat public terminal project: run CLI/TUI flows, validate installers, inspect Google Sheets CSV caches, and maintain the cache-first
The TradeCat public skill equips an agent to operate and validate the bundled TradeCat consumer project. It provides commands and workflows for running the CLI/TUI, inspecting cache snapshots (Google Sheets CSV), validating installers, and enforcing the project's cache-first, no-database contract.
Trigger this skill when tasks mention installing, running, debugging, or validating TradeCat; when inspecting cache paths or latest.* snapshot files; or when auditing the Skill wrapper and project boundary. Avoid server-side or database write operations per the skill boundaries.
Best for agents that can run shell commands and inspect filesystem artifacts (Python-capable runners, Codex-style CLI agents, and maintenance automation bots).
TradeCat public skill provides a comprehensive paper-trading runtime for Binance public data with strong safety boundaries (no real orders, no API keys, no signed requests). It bundles 23 scripts covering validation, ops audit, monitoring, paper trading, and security scanning. The skill is deeply coupled to its parent Python project — scripts require the full monorepo to function and cannot run in isolation. Three scripts succeeded (clean-local-runtime, install-security-tools, ops-audit); the rest need project context. Security posture is excellent with checksum-verified binary downloads, credential stripping, and explicit safety boundary enforcement.
tradecat_autotradecat_sourcespython3-venvpytestruffgitpip-auditWell-engineered project with strong security practices. The skill is essentially the entire project's operational toolset bundled as a skill — more of a monorepo CI/ops toolkit than a typical agent skill. The safety boundary design (explicit real_orders=false, reads_api_keys=false, signed_requests=false) is exemplary. The checksum-verified gitleaks install and credential env stripping in the monitor server are notable security positives. Architecture score limited by deep coupling to parent repo and lack of standalone usability.