← Back to Skills Marketplace
mdann1992

Crypto Signals Automation

by RickySmolders · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
329
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install crypto-signals-automation
Description
Build and operate a crypto signal trading automation using RapidAPI cryptexAI Buy & Sell Signals as signal source and dYdX v4 for execution. Use when setting...
README (SKILL.md)

Crypto Signals Automation

Use this skill to create a full pipeline: RapidAPI signals -> normalized signal objects -> dYdX v4 order execution.

Workflow

  1. Collect setup inputs first:
    • RapidAPI plan + key (X-RapidAPI-Key)
    • dYdX wallet address + mnemonic file path + subaccount
    • risk settings (max leverage, margin per trade, max open positions, close-after-hours)
    • TP/SL mode (reduce-only conditional orders)
    • alert channels (Telegram chat IDs)
  2. Validate RapidAPI connectivity with scripts/rapidapi_fetch.py.
  3. Generate env template with scripts/bootstrap_env.py.
  4. Wire runtime script/cron that:
    • fetches symbols/signals,
    • filters fresh active signals,
    • opens positions with retries,
    • places TP/SL reduce-only conditional orders,
    • closes stale positions,
    • cleans orphan reduce-only orders,
    • sends Telegram notifications for open/close with PnL.
  5. Test with one symbol in controlled mode before enabling full symbol set.

RapidAPI source

  • API: cryptexAI - Buy & Sell Signals
  • Base host header: cryptexai-buy-sell-signals.p.rapidapi.com
  • Endpoints:
    • GET /getSymbols
    • GET /getSignalsForSymbol?symbol=...

Use the most recent active=true signal per symbol. Deduplicate by signal id.

dYdX execution rules

  • Use dYdX v4.
  • Open position with market semantics.
  • Set TP/SL immediately after open as reduce-only conditional orders:
    • TP type: take-profit-market
    • SL type: stop-market / stop-limit equivalent in client
  • Retry failed order submissions up to total 3 attempts.
  • Keep signal->order client_id mapping in state and only cancel matching reduce-only orders on cleanup.

Security

  • Never commit real API keys/secrets.
  • Store secrets in .env with strict file permissions (chmod 600).
  • Treat mnemonic/passphrase as secrets.
  • If a token was exposed in chat/history, rotate it.

References

  • API details: references/rapidapi-cryptexai.md
  • Setup checklist: references/setup-checklist.md
Usage Guidance
This package is internally inconsistent: the README and templates expect RapidAPI and dYdX credentials (including a mnemonic) but the manifest claims no required env vars and the code does not implement dYdX/trading execution. Before installing or providing secrets: (1) do not paste real mnemonics or API secrets into chat; (2) review all code that will run the trading/execution logic — it is not included here; (3) require the author to provide or sign the dYdX execution code and update the manifest to declare required env vars; (4) test with throwaway/testnet accounts and minimal permissions only; (5) keep secrets in a secure vault and rotate them if exposed. If you cannot perform a code review, avoid supplying any real credentials or mnemonic material to this skill.
Capability Analysis
Type: OpenClaw Skill Name: crypto-signals-automation Version: 1.0.0 The skill bundle provides a legitimate framework for automating crypto trading using RapidAPI signals and dYdX v4. It includes helper scripts (bootstrap_env.py, rapidapi_fetch.py) for environment configuration and API connectivity testing that use standard Python libraries and follow safe practices. While the workflow involves handling sensitive credentials like mnemonics and API keys, the provided logic is transparent, strictly aligned with the stated purpose, and lacks any indicators of malicious intent, vulnerabilities, or data exfiltration.
Capability Assessment
Purpose & Capability
The description and SKILL.md promise a complete pipeline (signal ingestion, dYdX v4 order execution, TP/SL, retries, Telegram notifications). The included code, however, only implements RapidAPI fetch and writes an .env template; there is no dYdX client, no execution logic, and no Telegram notifier. Additionally, the registry metadata declares no required env vars or primary credential despite the skill explicitly requiring RapidAPI keys and dYdX secrets — this mismatch indicates the package is incomplete or misleading.
Instruction Scope
Runtime instructions ask the agent/operator to collect and handle highly sensitive secrets (RapidAPI key, dYdX wallet/mnemonic/API secrets, Telegram bot token) and to 'wire runtime script/cron' that will autonomously open/close orders. The instructions are open-ended about implementation details and grant broad discretion (e.g., scheduling, retries, cleanup) but the shipped code does not implement these behaviors. This gap increases the risk that users will paste secrets into chat or install/adapt third-party code of unknown provenance.
Install Mechanism
There is no install spec (instruction-only + two small helper scripts). No external downloads or installers are used. The only file-writing behavior is the bootstrap script which creates a local .env template; that itself is low-risk but should be noted since it touches the filesystem.
Credentials
The skill requires multiple high-privilege secrets (RAPIDAPI_KEY, DYDX_API_KEY/SECRET/PASSPHRASE, DYDX mnemonic path, Telegram bot token) according to SKILL.md and bootstrap template, but the skill manifest lists none. Requesting wallet mnemonic and exchange API credentials is reasonable for trading automation, but the lack of declared required env vars and the package's incomplete implementation means users may be asked to provide sensitive credentials without clear, auditable code that will use them — disproportionate and potentially hazardous.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide persistence or modify other skills. It writes a local .env template if run, which is expected and scoped to the project directory.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install crypto-signals-automation
  3. After installation, invoke the skill by name or use /crypto-signals-automation
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Crypto Signals Automation v1.0.0 - Initial release of a full pipeline to automate crypto trading signals using RapidAPI cryptexAI signals and dYdX v4 execution. - Supports setup of API keys, dYdX credentials, risk management, and alert channels. - Automates signal fetching, filtering, order execution with TP/SL, retries, cleanup, and Telegram notifications. - Includes scripts for connectivity validation and environment setup. - Provides detailed security guidance and references for setup and API use.
Metadata
Slug crypto-signals-automation
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Crypto Signals Automation?

Build and operate a crypto signal trading automation using RapidAPI cryptexAI Buy & Sell Signals as signal source and dYdX v4 for execution. Use when setting... It is an AI Agent Skill for Claude Code / OpenClaw, with 329 downloads so far.

How do I install Crypto Signals Automation?

Run "/install crypto-signals-automation" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Crypto Signals Automation free?

Yes, Crypto Signals Automation is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Crypto Signals Automation support?

Crypto Signals Automation is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Crypto Signals Automation?

It is built and maintained by RickySmolders (@mdann1992); the current version is v1.0.0.

💬 Comments