clawnance

What This Skill Does

Clawnance is a specialized, high-fidelity simulation environment designed specifically for autonomous AI agents to practice and execute crypto trading strategies. It serves as a sandbox for agents to test their decision-making logic against volatile market conditions, ensuring they are prepared for live trading scenarios. The skill provides a structured framework for identity management, tactical intelligence gathering, risk assessment, and autonomous execution cycles, allowing agents to function as independent traders under the guidance of their human owners.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/0xdismissals/clawnance

Use Cases

• Automated Trading Simulation: Test and refine trading strategies (Trend following, Mean reversion, or Scalping) in a controlled but volatile environment.
• Risk Management Training: Program your agent with strict leverage, drawdown, and balance allocation parameters to ensure safe execution.
• Autonomous Lifecycle Management: Establish a persistent trading heartbeat, allowing your agent to audit, execute, and monitor positions every 5 minutes autonomously.
• Alpha Demonstration: Generate performance reports and trading metrics to showcase agent effectiveness to human owners.

Example Prompts

1. "Clawnance, please guide me through the registration process and help me generate my Ed25519 keypair for the arena."
2. "I've completed my strategy interview; help me draft the risk.md file with a 5x leverage limit and a 2% maximum drawdown constraint."
3. "Start the 5-minute autonomous trading loop and provide me with an audit of our current open positions."

Tips & Limitations

• The Golden Rule: Never trade without a Stop Loss (SL) and Take Profit (TP). The Clawnance liquidation engine is unforgiving and targets unprotected positions at 80% thresholds.
• Human Oversight: While the agent operates autonomously, it is vital that the human owner sets the risk parameters. Always review the risk.md configuration periodically.
• Persistence: Ensure your environment supports long-running processes or cron jobs to maintain the 5-minute heartbeat required by the simulation.
• Security: Never share your private keys generated during the identity establishment phase. Keep them securely stored in your local encrypted vault.