moltrade
Operate the Moltrade trading bot (config, backtest, test-mode runs, Nostr signal broadcast, exchange adapters, strategy integration) in OpenClaw.
What this skill does
# Moltrade Bot Skill Paths are repo-root relative. Keep actions deterministic and redact secrets. ## Install & Init - Clone the repo and install Python deps locally (code is required for strategies, nostr, and CLI): - `git clone https://github.com/hetu-project/moltrade.git` - `cd moltrade/trader && pip install -r requirements.txt` - Initialize a fresh config with the built-in wizard (no trading): - Prefer the human user to run `python main.py --init` (prompts for relayer URL, wallet, nostr, copy-trade follower defaults, and bot registration), so you can approve prompts, handle the wallet private key entry yourself, and capture the relayer’s returned `relayer_nostr_pubkey` when registering the bot. - If you delegate to an agent, do so only if you trust it with the wallet key and ensure it completes the entire wizard—including the final bot registration step—so the `relayer_nostr_pubkey` gets written back to the config. - For CI/agents, keep using the repo checkout; there is no separate pip package/CLI yet. ## Update Config Safely - Backup or show planned diff before edits. - Change only requested fields (e.g., `trading.exchange`, `trading.default_strategy`, `nostr.relays`). - Validate JSON; keep types intact. Remind user to provide real secrets themselves. ## Run Backtest (local) - Install deps: `pip install -r trader/requirements.txt`. - Command: `python trader/backtest.py --config trader/config.example.json --strategy <name> --symbol <symbol> --interval 1h --limit 500`. - Report PnL/win rate/trade count/drawdown if available. Use redacted config (no real keys). ## Start Bot (test mode) - Ensure `config.json` exists (run `python main.py --init` if not) and `trading.exchange` set (default hyperliquid). - Command: `python trader/main.py --config config.json --test --strategy <name> --symbol <symbol> --interval 300`. - Watch `trading_bot.log`; never switch to live without explicit user approval. ## Run Bot (live) - Only after validation on test mode; remove `--test` to hit mainnet. - Command: `python trader/main.py --config config.json --strategy <name> --symbol <symbol>`. - Double-check keys, risk limits, and symbol before starting; live mode will place real orders. ## Broadcast Signals to Nostr - Check `nostr` block: `nsec`, `relayer_nostr_pubkey`, `relays`, `sid`. - `SignalBroadcaster` is wired in `main.py`. In test mode, verify `send_trade_signal` / `send_execution_report` run without errors. ## Add Exchange Adapter - Implement adapter in `trader/exchanges/` matching `HyperliquidClient` interface (`get_candles`, `get_balance`, `get_positions`, `place_order`, etc.). - Register in `trader/exchanges/factory.py` keyed by `trading.exchange`. - Update config `trading.exchange` and rerun backtest/test-mode. ## Integrate New Strategy - Follow `trader/strategies/INTEGRATION.md` to subclass `BaseStrategy` and register in `get_strategy`. - Add config under `strategies.<name>`; backtest, then test-mode before live. ## Safety / Secrets - Never print or commit private keys, mnemonics, nsec, or shared keys. - Default to test mode; require explicit consent for live trading.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.