Crypto Market Monitor
PassAudited by ClawScan on May 10, 2026.
Overview
The skill appears to do crypto and economic-data monitoring as advertised, with user-directed setup, external market-data API calls, and optional recurring cron jobs.
This looks safe to use for read-only market monitoring, but install it cautiously: use a virtual environment, review the scripts, fix workspace paths if needed, and only add the cron jobs if you want automatic recurring network calls and log files.
Findings (4)
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.
If the user adds the cron entry, the monitor will keep running on a schedule and making market-data requests until the cron entry is removed.
The install guide documents an optional cron job that would run the monitor every 30 minutes. This is disclosed and purpose-aligned, but it is persistent background behavior.
*/30 * * * * cd ~/.openclaw/workspace/crypto/scripts && /usr/bin/python3 crypto_monitor_telegram.py >> ~/.openclaw/workspace/crypto/logs/crypto_monitor.log 2>&1
Only add the cron jobs if you want recurring monitoring; remove them from crontab to stop automatic runs.
Installing unpinned packages can produce different code versions over time and depends on the trustworthiness of the Python package index and local environment.
The documented dependency install uses unpinned package names. These packages are normal for a Python monitoring script, but versions/provenance are not locked.
pip3 install requests pytz feedparser
Install dependencies in a virtual environment and consider pinning known-good versions before using scheduled execution.
Some documented commands or cron jobs may fail unless the missing script exists elsewhere.
The documentation references a daily_economic_report_v2.py script, but that file is not present in the supplied file manifest. This suggests incomplete or inconsistent packaging rather than malicious behavior.
cd economic python3 daily_economic_report_v2.py
Verify the installed files before relying on the daily report command or cron entry.
If a different or unexpected economic_analyzer.py exists in that workspace path, running the script could execute that local file instead of the packaged helper.
The script modifies Python's import path to load modules from a hard-coded workspace path. This is likely intended to find helper modules, but it can execute whatever matching module is found at that path.
sys.path.insert(0, '/root/.openclaw/workspace') from economic_analyzer import EconomicDataAnalyzer
Run the skill from an isolated workspace and adjust hard-coded paths to point only to the intended installed files.