Crypto Market Analyzer
v1.0.0Cryptocurrency market analysis for Bitcoin and Ethereum. Fetches 4h (24h) and 1d (30-day) data from Binance API, calculates technical indicators (RSI, SMAs, support/resistance), and provides bullish/bearish sentiment analysis with reasoning. Use when user asks for crypto market reports, BTC/ETH analysis, or daily market summaries.
⭐ 2· 1.3k·3 current·5 all-time
by@hmzo
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included code and SKILL.md. The Python script fetches public Binance klines and computes RSI, SMAs, EMA/MACD, Bollinger Bands, support/resistance and volume metrics — all expected for a crypto market analyzer.
Instruction Scope
Runtime instructions are limited to running the included script, parsing the JSON, formatting a report, and scheduling daily execution. The SKILL.md's instruction to "send the report to the user via messaging channel" is vague about which channel/mechanism or credentials to use; scheduling instructions assume the ability to create cron jobs (platform-specific) but do not instruct reading unrelated files or secrets.
Install Mechanism
No install spec is provided (instruction-only + included script). No downloads or external install steps — lowest-risk install model.
Credentials
The skill declares no required environment variables, no credentials, and the code only uses public Binance endpoints. No secret or unrelated credential access is requested.
Persistence & Privilege
always:false (normal). SKILL.md suggests creating a daily cron job which would give persistent scheduled runs if the operator configures it; this is a benign capability but requires user action/consent — the skill does not request platform-level always-on privileges.
Assessment
This skill appears to do what it claims: query Binance public market data and compute technical indicators locally without needing credentials. Before installing or scheduling it: (1) review the full script yourself (or run it in a sandbox) to confirm there are no hidden network endpoints or logging of data you don't expect; (2) be cautious about enabling automated cron jobs — only schedule it if you want regular reports; (3) consider how reports will be delivered (the SKILL.md is vague about messaging channels), and avoid providing credentials to unknown channels; and (4) remember analysis is informational, not financial advice.Like a lobster shell, security has layers — review code before you run it.
latestvk973rydvkjmywmstermr7ycjz980y7gg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.