Binance Alpha Explorer
PassAudited by ClawScan on May 1, 2026.
Overview
This skill appears to do what it claims: monitor public Binance market data for new trading pairs, while keeping local alert state.
This skill looks reasonable for public Binance listing monitoring. Before installing, be comfortable with running a long-lived network monitor, installing the websocket-client dependency, and keeping local alert/state files under ~/.config/alpha.
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.
Installing an unpinned package means the exact dependency version may vary over time.
The setup instructions ask the user to install a Python package without a pinned version; this is central to the WebSocket monitor but is still a dependency/provenance point users should notice.
pip3 install websocket-client --user
Install from a trusted Python package index and consider pinning or reviewing the websocket-client version in controlled environments.
Once started, the monitor is designed to keep running and reconnecting until stopped.
The monitor automatically reconnects after a WebSocket close while it is running; this is disclosed and purpose-aligned for continuous market monitoring.
if running: ... time.sleep(5) ... start_monitoring()
Run it only when you want continuous monitoring, and stop it with the documented interrupt/stop behavior when finished.
Local alert history and known-pair state will remain on disk until reset or deleted.
The skill stores local state and alert history for reuse across runs; the stored data appears limited to public trading-pair and alert information.
State files are stored at: ~/.config/alpha/ ... known_symbols.json ... alerts_history.json
Use the reset command or remove ~/.config/alpha if you no longer want the local monitoring history retained.