openmm-exchange-setup

What This Skill Does

The openmm-exchange-setup skill provides a secure, structured, and interactive framework for configuring API connectivity between OpenMM and various centralized cryptocurrency exchanges, including MEXC, Gate.io, Bitget, and Kraken. This skill automates the validation of environmental variables and serves as an onboarding bridge, ensuring users correctly provision their API credentials, establish minimal necessary permissions, and confirm real-time connectivity to exchange market data endpoints. It abstracts the technical complexity of setting up secure authentication layers, ensuring that all credentials remain local to the user's environment via secure .env configuration.

Installation

To integrate this functionality into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/adacapo21/openmm-exchange-setup Once installed, ensure your project directory contains a .env file where your sensitive API keys can be stored securely. Do not commit your .env file to version control systems like GitHub.

Use Cases

• Initial Onboarding: Rapidly configuring the exchange connection during the first-time deployment of OpenMM.
• Expanding Market Coverage: Adding support for an additional exchange, such as migrating from MEXC to Bitget for specific liquidity pairs.
• Troubleshooting: Validating that connectivity issues are due to expired keys or incorrect permission scopes by running the built-in balance and ticker verification checks.
• Audit Compliance: Ensuring that only 'Read' and 'Trade' permissions are active, strictly prohibiting withdrawal capabilities for security.

Example Prompts

1. "OpenClaw, guide me through the step-by-step setup for adding my new Bitget API keys to OpenMM."
2. "I'm having trouble fetching market data; can you help me verify if my Kraken API permissions are configured correctly?"
3. "List all supported exchanges in OpenMM and explain which permissions I need to enable for Gate.io."

Tips & Limitations

• Safety First: Always disable 'Withdraw' permissions on your API keys. This prevents potential financial loss if a key is compromised.
• IP Whitelisting: Whenever possible, enable IP whitelisting on your exchange's security settings to restrict API access to your server's static IP.
• Passphrase Handling: Remember that Bitget requires a 'Passphrase' specifically defined during the API key creation process, which must be mirrored in your local environment file.
• Network Latency: Be aware that verification steps are dependent on the exchange's public API rate limits; excessive testing may lead to temporary connection throttling.