universal-trading

What This Skill Does

The universal-trading skill provides an automated interface for the Particle Network Universal Account SDK. It enables users to execute cross-chain token trades across EVM and Solana chains seamlessly. By managing the underlying configuration of the universal-account-example project, it allows users to perform buys, sells, swaps, and asset transfers without manual orchestration. The skill includes built-in hooks for real-time monitoring via WebSocket and provides robust transaction status verification, ensuring that users always receive finality feedback on their trading activity.

Installation

To integrate this skill, use the ClawHub command: clawhub install openclaw/skills/skills/0xmomo-ngclubs/universal-trading

Upon initial execution, the skill automatically initializes the repository environment, creates the necessary .env files, and applies mandatory patches to ensure optimal trade execution, such as removing primary token restrictions. Users may optionally provide a private key during initialization to import existing wallets or use the --target flag to specify a directory for the local environment.

Use Cases

This skill is designed for high-frequency or complex cross-chain activities, including:

• Portfolio management across EVM and Solana.
• Automated swap executions with slippage control.
• Real-time asset tracking and transaction status monitoring via WebSocket subscriptions.
• Interaction with custom transactions that require signing and submission via Particle Network's infrastructure.

Example Prompts

1. "Buy 0.5 SOL worth of USDC on Solana with 0.5% slippage."
2. "Check the current balance of my universal account and show me the last 5 transactions."
3. "Swap my existing USDT for ETH on Arbitrum and monitor the transaction status until it is confirmed."

Tips & Limitations

Always ensure that your .env file is properly configured with your private key if you prefer not to use the automated creation flow. For volatile tokens, always utilize the slippage controls provided in the scripts to avoid failed transactions. Remember that transaction monitoring is mandatory; do not assume a transaction is complete until the tool reports a 'SUCCESS' status. The skill defaults to auto-binding an invite code, which can be disabled via the DISABLE_AUTO_INVITE_BIND environment variable if desired. Use the provided WebSocket tools for live tracking rather than constant manual polling to save system resources.