Crypto Trading Bot

v1.0.1

加密貨幣交易機器人開發 - 幫你整自動交易Bot,支持Pine Script、Python、CCXT API對接。適用於:(1)整TradingView信號Bot (2)CEX/DEX API自動化 (3)套利機器人 (4)止盈止損策略

0· 183·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill describes developing trading bots (TradingView, CEX/DEX, Pine Script, CCXT). As delivered it's a consultancy/instruction document (pricing, workflow, tech stack) rather than an autonomous trading executor. That is coherent, but if you expected an agent that will execute live trades, note the skill does not request or manage exchange API keys or binaries needed to run bots — so it cannot itself perform trades without additional components.
Instruction Scope
SKILL.md only contains service description, pricing, capabilities, and a short user interaction flow (ask target exchange, pair, strategy, budget). It does not instruct the agent to read files, access environment variables, call external endpoints, or exfiltrate data.
Install Mechanism
No install spec and no code files are included. Nothing will be written to disk or installed by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. While real trading bot development typically requires exchange API keys, the lack of requested credentials here is consistent with this being a consulting/instructional offer rather than an executor.
Persistence & Privilege
The skill does not request persistent presence (always is false) and does not attempt to modify system or other skills' configuration. Model invocation is enabled by default which is normal and not by itself concerning.
Assessment
This skill is essentially a service description and developer offer, not an executable trading bot. Important considerations before engaging or sharing secrets: (1) The skill does not request API keys now — do not share exchange API keys, especially ones with withdrawal rights, over chat or social channels. Provide only restricted (IP-limited / read-only or trade-only) keys for testing if absolutely necessary. (2) Verify the developer’s identity and request code samples, audit reports, and references before handing over credentials or funds. (3) If you want autonomous trading, require a security review of any code (no hidden endpoints, no obfuscated logic) and prefer running bot code in your own controlled environment. (4) Use testnets and small amounts for initial trials, and implement rate limits and kill-switches. (5) Be cautious when contacting via informal channels (WeChat/Telegram); prefer verifiable, professional communication and contracts.

Like a lobster shell, security has layers — review code before you run it.

latestvk971nx4r8t7ffz8nb5ws56m5tn83gjx0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments