Crypto Price Monitor
v1.0.0Monitor cryptocurrency prices and trigger alerts when thresholds are hit. Supports BTC, ETH, SOL, and 100+ other coins via CoinGecko API. Configure price cei...
⭐ 0· 73·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (monitor crypto prices, trigger alerts, optional Telegram delivery) matches the included instructions and Python script: it polls CoinGecko, compares thresholds, prints alerts, and can POST to Telegram. No unrelated credentials or platform access are requested.
Instruction Scope
Instructions and code stay within the stated purpose (fetch prices from CoinGecko, evaluate alerts, deliver to console/Telegram). Minor inconsistency: the SKILL.md's embedded script writes triggered alerts to /tmp/crypto_alerts_triggered.json, whereas the included crypto_alert.py file in the manifest (the delivered code) does not include that /tmp write — verify which version you run. Both versions only reference local config and make outbound network calls to CoinGecko and Telegram.
Install Mechanism
No install spec (instruction-only + included script) — lowest install risk. The script requires the Python 'requests' library but the skill does not declare dependencies; user must ensure Python+requests are available.
Credentials
No required environment variables or unrelated credentials are requested. Telegram bot token and chat ID are optional fields in the local JSON config (expected and proportionate). The skill does not request additional secrets or system credentials.
Persistence & Privilege
Skill is not always-enabled and does not request elevated or persistent platform privileges. It runs as a local script and (per SKILL.md) may be scheduled via cron — expected for this use case.
Assessment
This appears to be a straightforward CoinGecko-based alert script. Before installing/running: 1) Inspect which crypto_alert.py you will execute (manifest vs SKILL.md differ — confirm whether the script writes to /tmp and that this behavior is acceptable). 2) Do not commit your Telegram bot token/chat_id into public repos; store the config file with restrictive permissions or supply tokens at runtime. 3) Ensure Python and the 'requests' package are installed (the skill does not declare dependencies). 4) Be aware the script makes outbound HTTP requests to api.coingecko.com and api.telegram.org; run it in an environment where that network activity is acceptable. 5) If running on a schedule (cron), redirect logs to a path you control and monitor disk usage of any files the script writes. If you want stricter secret handling, modify the script to read the Telegram token from a protected environment variable rather than a plain JSON file.Like a lobster shell, security has layers — review code before you run it.
latestvk975ekq6539geeddtyd7kv45qh83qzd3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.