Passive Income Claw

Binance passive income AI assistant. Automatically scans Binance earn opportunities, pushes matching opportunities based on user preferences, and executes su...

This skill appears to implement what it claims, but take the following steps before installing or enabling auto execution: - Review and run the code in a safe environment first (do a dry run / read-only checks). The scripts are TypeScript (.ts) files — ensure your runtime can execute them (node alone may not run .ts without ts-node or a transpilation step). The skill's metadata incorrectly omits 'node' as a required binary. - Limit API key permissions: create an API key that only enables the exact permissions you need (read balances/positions and Earn operations; add Margin only if you intend to use borrow-to-earn). Do NOT enable withdrawal on any key you give to this skill. - Prefer confirm-first mode initially. Do not enable confirmation_mode: auto until you have tested scans and executions and are comfortable with the logic and limits. - Use IP whitelisting on your Binance API key (bind to OpenClaw's running IP) and rotate keys if you change configuration. The README recommends this — follow it. - Inspect the user-profile.md defaults the skill will write (single_amount_limit, daily_amount_limit, allowed_operations, asset_whitelist) and set conservative limits before allowing any execution. - Because the skill can borrow on margin, be aware of liquidation and interest risk; test margin flows with small amounts or not at all if you lack experience. - If you want additional assurance, ask the publisher for clarification about runtime requirements (how to run .ts files), why 'node' is not declared as a required binary, and request a signed release or provenance information (source/homepage is unknown).

Type: OpenClaw Skill Name: passive-income-claw Version: 0.7.0 The 'passive-income-claw' skill is a well-structured Binance Earn automation tool that aligns with its stated purpose. It implements a robust multi-step safety architecture, including a dedicated authorization script (bin/auth-check.ts) that enforces user-defined daily limits, single-operation caps, and asset whitelists stored in a local profile. The code uses standard HMAC SHA256 signing for Binance API requests (lib.ts) and includes detailed logic for risk assessment and error handling, such as automatic rollbacks for failed borrow-to-earn operations (execute.md). No evidence of data exfiltration, credential theft, or unauthorized network activity was found.