gotchi-pocket

What This Skill Does

The gotchi-pocket skill provides a robust interface for interacting with Aavegotchi escrow pockets on the Base network. By leveraging the Bankr protocol, this skill allows users to seamlessly deposit and withdraw ERC20 tokens into and out of their Gotchi pockets. It serves as a bridge between the agent and on-chain assets, providing capabilities to resolve ownership, query specific token balances, and execute complex transfers via simple natural-language commands. The skill enforces security by checking owner-control permissions against the active Bankr wallet by default, ensuring that only authorized users can perform sensitive operations. Additionally, it features a sophisticated natural-language processing layer that parses intent and dispatches tasks to the appropriate execution scripts, while implementing a multi-step approval workflow for withdrawals to protect assets.

Installation

To integrate this skill into your environment, use the OpenClaw hub CLI by running: clawhub install openclaw/skills/skills/aaigotchi/gotchi-pocket. Ensure your local environment is configured with access to the Base network and that your Bankr wallet is properly authenticated for the signing process.

Use Cases

This skill is ideal for Gotchi owners who want to automate the management of their on-chain assets without manually constructing raw contract transactions. Common use cases include: rebalancing liquidity held across multiple Gotchi pockets, moving GHST or other ecosystem tokens (FUD, FOMO, KEK) into specific Pockets for gameplay utility, and auditing the contents of multiple pockets efficiently. It is particularly useful for automated asset management workflows or for users who prefer using natural language to orchestrate complex DeFi interactions on Base.

Example Prompts

1. "Send 50 GHST from my wallet to the pocket of gotchi 9638."
2. "Check the current WETH balance for gotchi 9638 and tell me if it's enough to cover the pocket fees."
3. "Withdraw 100 FUD from gotchi 9638 to my address 0x123...456 and confirm the transaction once approved."

Tips & Limitations

• Safety First: Always use the --dry-run flag with the command interface to preview your transaction before final submission.
• Token Aliases: Save time by using provided aliases like GHST, USDC, or WETH instead of long contract addresses.
• Approval Workflow: Withdrawals are blocked by default. You must run the command once to trigger the requirement, then re-run with --approve-withdraw to authorize the transfer.
• Raw Units: Only use the --raw flag if you are providing amounts in the token's smallest base unit (e.g., wei); otherwise, standard decimal amounts are expected.