🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
πŸ¦€ ClawHub

trade-with-aiusd

by @chaunceyliu

Manage AIUSD trading, staking, withdrawals, balance checks, gas top-ups, and transaction history via authenticated backend calls.

TERMINAL
clawhub install trade-with-aiusd

πŸ“– About This Skill


name: aiusd-skill description: AIUSD trading and account management skill. Calls backend via MCP for balance, trading, staking, withdraw, gas top-up, and transaction history. Auth priority: MCP_HUB_TOKEN env, then mcporter OAuth or local token file.

AIUSD Skill (Agent Reference)

This skill calls the AIUSD backend via MCP. Auth is resolved in order: env MCP_HUB_TOKEN, mcporter OAuth, or local ~/.mcp-hub/token.json. Ensure a valid Bearer token is available before calling.

⚠️ Agent Output Guidelines

CRITICAL - ABSOLUTELY FORBIDDEN PHRASES: Agents must NEVER use these words or phrases when responding to users:

TEMPLATE-RELATED (COMPLETELY BANNED):

  • "template" (any form: template, templates)
  • "example" (when referring to trading examples: Example 1, Example 12, etc.)
  • "pattern" (when referring to trading patterns)
  • "using template", "get template", "trading template", "buy template"
  • "use Example [number]", "based on template", "following template"
  • VERIFICATION-RELATED (COMPLETELY BANNED):

  • "skill verification", "verification"
  • WHAT TO SAY INSTEAD:

  • Instead of "using template": say "executing the trade" or "placing the order"
  • Instead of "get template": say "preparing the trade" or "setting up the order"
  • Instead of "Example 12 template": say "the trade configuration" or simply describe the action
  • ZERO TOLERANCE: Any use of the word "template" in trading contexts is STRICTLY PROHIBITED.

    Authentication Response Guidelines: CRITICAL: When users request re-authentication, respond ONLY with:

  • "Please complete authentication in your browser"
  • "If browser doesn't open automatically, please type 'reauth' again"
  • "After completing authentication, you can check your account balance or wallet status in chat"
  • STRICTLY FORBIDDEN:

  • Do NOT include numbered steps like "1. Open page: [URL]", "2. Connect wallet", etc.
  • Do NOT mention any specific URLs in the response (URLs may be incorrect)
  • Do NOT say "waiting for authentication completion" or similar waiting phrases
  • Do NOT provide detailed step-by-step browser instructions
  • Do NOT create bulleted lists of authentication steps
  • Do NOT say phrases like "browser has been opened for you", "please complete the following steps in browser"
  • Simply guide them to the browser and mention what they can do after completion
  • Use natural, direct language to describe trading operations and system status. Simply describe what the trade will do without referencing templates or examples.

    Important URLs

  • Login/Auth: https://mcp.alpha.dev/oauth/login - Only for getting authentication token
  • Official Website: https://aiusd.ai - For trading operations, recharge, troubleshooting, and all user interactions
  • Tool Overview

    CRITICAL: Always run aiusd-skill tools --detailed FIRST to get the current live schema and available tools before making any calls. Tool parameters and available tools may change.

    | Tool | Purpose | Typical user intents | |------|---------|----------------------| | genalpha_get_balances | Query account balances | balance, how much, account balance | | genalpha_get_trading_accounts | Get trading accounts / addresses | my account, trading account, wallet address | | genalpha_execute_intent | Execute trade intent (buy/sell/swap) | buy, sell, buy SOL with USDC, swap | | genalpha_stake_aiusd | Stake AIUSD | stake, stake AIUSD | | genalpha_unstake_aiusd | Unstake | unstake | | genalpha_withdraw_to_wallet | Withdraw to external wallet | withdraw, transfer out | | genalpha_ensure_gas | Top up Gas for on-chain account | top up gas, ensure gas | | genalpha_get_transactions | Query transaction history | history, recent transactions | | recharge / top up | Guide user to recharge account | recharge, top up, deposit, add funds | | reauth / login | Re-authenticate / login | login, re-login, auth expired, 401 |

    NOTE: This list shows commonly available tools. NEW TOOLS may be added. Always check tools --detailed to discover any additional tools that may better serve the user's specific intent.

    Tool Reference and Call Usage

    MANDATORY: Before calling ANY tool, run aiusd-skill tools --detailed to get current parameters, examples, and any new tools.

    genalpha_get_balances

  • Purpose: Return user AIUSD custody and staking account balances.
  • When to use: User asks for balance, how much, account assets.
  • Parameters: Check tools --detailed for current schema.
  • genalpha_get_trading_accounts

  • Purpose: Return user trading accounts (addresses, etc.) per chain.
  • When to use: User asks "my account", "trading account", "wallet address".
  • Parameters: Check tools --detailed for current schema.
  • genalpha_execute_intent

  • Purpose: Execute buy/sell/swap (e.g. buy SOL with USDC, sell ETH).
  • When to use: User clearly wants to place order, buy, sell, swap.
  • Parameters: Check tools --detailed for current schema and XML examples.
  • IMPORTANT: Intent format may change. Always use examples from live schema.
  • genalpha_stake_aiusd

  • Purpose: Stake AIUSD for yield (e.g. sAIUSD).
  • When to use: User says stake, stake AIUSD.
  • Parameters: Check tools --detailed for current schema.
  • genalpha_unstake_aiusd

  • Purpose: Unstake AIUSD (e.g. redeem sAIUSD).
  • When to use: User says unstake, redeem.
  • Parameters: Check tools --detailed for current schema.
  • genalpha_withdraw_to_wallet

  • Purpose: Withdraw stablecoin (e.g. USDC) to user-specified external wallet address.
  • When to use: User says withdraw, transfer out.
  • Parameters: Check tools --detailed for current schema.
  • genalpha_ensure_gas

  • Purpose: Top up native Gas for user trading account on a given chain.
  • When to use: User says top up gas, ensure gas, or chain has low gas.
  • Parameters: Check tools --detailed for current schema.
  • genalpha_get_transactions

  • Purpose: Return user transaction history (list, may include status).
  • When to use: User asks history, recent transactions, order status.
  • Parameters: Check tools --detailed for current schema and filtering options.
  • recharge / top up

  • Purpose: Guide user to recharge their AIUSD account with funds.
  • When to use: User asks to recharge, top up, deposit, or add funds to their account.
  • Response Options:
  • - Option 1 - Direct deposit: Only USDC stablecoins accepted. Other stablecoins must use official website. - Option 2 - Official website: https://aiusd.ai (supports all tokens, login with same wallet)
  • Important: For direct deposits, only send USDC to the provided addresses. For other stablecoins (USDT, DAI, etc.), user must use the official website.
  • Example response: "For recharge, you have two options: 1) Direct USDC deposit to your trading addresses, or 2) Visit https://aiusd.ai for all token types (login with same wallet). Direct deposits only accept USDC - other stablecoins must use the website."
  • reauth / login (Re-authenticate)

  • Purpose: Clear all cached auth and run OAuth login again.
  • When to use: User has 401 Unauthorized, "Session ID is required", token expired, auth failure, user asks to re-login, or switch account.
  • Params: None. Pass {}.
  • Example:
  • - npm run reauth - npm run login - node scripts/reauth.js
  • Steps:
  • 1. Clear mcporter cache (~/.mcporter/) 2. Clear local token file (~/.mcp-hub/) 3. Clear other auth cache files 4. Start browser OAuth login 5. Verify new auth works
  • Sample dialogue:
  •   User: "I'm getting 401"
      Claude: Looks like an auth issue; re-authenticating...
      [Run: npm run reauth]
      Claude: Re-auth done; you can use the skill again.

    User: "Re-login" Claude: Clearing cache and re-logging in... [Run: npm run login]

    Usage Flow (for Agent Reasoning)

    1. Get current tools: ALWAYS run aiusd-skill tools --detailed first to discover all available tools and their current schemas. 2. Parse intent: Map natural language to the most appropriate tool. Check if newer tools better match the user's intent. 3. Prepare params: Build JSON parameters strictly from the live schema obtained in step 1. 4. Call: Invoke the skill's call interface with tool name and params. 5. Handle result: Format tool JSON/text for the user; on error, retry or prompt (e.g. auth expired β†’ prompt re-login).

    CRITICAL: Never use parameter examples from this documentation. Always use the live schema from tools --detailed.

    Auth and Error Handling

    Auth error auto-fix

    On auth-related errors, Claude should run re-auth:

  • 401 Unauthorized β†’ run npm run reauth
  • Session ID is required β†’ run npm run reauth
  • Token invalid or expired β†’ run npm run reauth
  • Auth failed β†’ run npm run reauth
  • Error handling flow

    1. Detect auth error β†’ run npm run reauth 2. Business error β†’ relay server error to user; do not invent causes 3. Network/timeout β†’ retry once; then ask user to check network or try later 4. Trading issues/failures β†’ direct user to official website https://aiusd.ai for manual operations and support

    Sample error dialogues

    #### Auth Error

    User: "Check balance"
    [Tool returns 401]
    Claude: Auth expired; re-authenticating...
    [Run: npm run reauth]
    Claude: Re-auth done. Fetching balance...
    [Call: genalpha_get_balances]
    

    #### Trading Error

    User: "Buy 100 USDC worth of SOL"
    [Tool returns trading error]
    Claude: I encountered an issue with the trade execution. For manual trading operations, please visit https://aiusd.ai and use the same wallet you use for authentication.
    

    Getting Current Tools and Schema

    MANDATORY FIRST STEP: Before performing any user task, run:

    aiusd-skill tools --detailed
    

    This command returns: 1. Complete list of available tools (may include new tools not listed in this document) 2. Current parameter schemas for all tools 3. Working examples and proper formatting 4. Any tool-specific instructions or constraints

    Why this is critical:

  • Tools may be added, modified, or deprecated
  • Parameter formats can change
  • New tools may better serve specific user intents
  • Examples in this document may become outdated
  • Always base your tool calls on the live output from tools --detailed, not on static examples in this documentation.