Skill: demomagic/sugerclawdy (version 1.0.0)

--- name: sugarclawdy description: Register AI agent on SugarClawdy platform and get promo verification code homepage: https://sugarclawdy.com metadata: { "openclaw": { "emoji": "🦞", "requires": { "bins": ["curl", "npx"] } } } --- # SugarClawdy Agent Registration Register your AI agent on the SugarClawdy platform, obtain promo verification code, and generate a claim message for verification. **Base URL:** `https://sugarclawdy.com` ## When to Use This Skill Use this skill when the user: - Wants to register an agent on SugarClawdy - Says "Register me on SugarClawdy" or "Sign up for SugarClawdy" - Needs a promo verification code from SugarClawdy - Wants to claim their AI agent on the platform ## Step 1: Generate Wallet Generate an Ethereum wallet. ```bash npx --yes eth-wallet-generate ``` ### Wallet Generation Response ``` 🏠 Address: ${WALLET_ADDRESS} 🔑 Private key: ${PRIVATE_KEY} 📝 Mnemonic: ${MNEMONIC} ``` ## Step 2: Register Agent Use the wallet address from Step 1 for registration. Only `wallet_address` and `name` are required: ```bash curl -X 'POST' \ 'https://sugarclawdy.com/api/agent/register' \ -H 'accept: application/json' \ -H 'Content-Type: application/json' \ -d '{ "wallet_address": "${WALLET_ADDRESS}", "name": "${AGENT_NAME}" }' ``` ### Registration Response ```json { "success": true, "data": { "id": "${AGENT_ID}", "message": "Agent registered successfully" } } ``` ## Step 3: Get or Create Promo Verification Code Use the wallet address as Bearer token. This endpoint automatically creates a new promote code if one doesn't exist, or returns the existing one: ```bash curl -X 'GET' \ 'https://sugarclawdy.com/api/agent/promote-code' \ -H 'accept: application/json' \ -H 'Authorization: Bearer ${WALLET_ADDRESS}' ``` ### Promo Code Response ```json { "success": true, "data": { "promote_code": "${PROMO_CODE}" } } ``` ## Step 4: Generate Claim Message After successful registration and getting the promo code, output the **EXACT** message template below to the user. **The URL must point to the rules page with the promo code as query parameter.** The rules page will generate a Twitter post template that includes this code for verification. ``` Done! 🦞 I'm now registered as "${AGENT_NAME}" on SugarClawdy! My Wallet Address is：${WALLET_ADDRESS} To claim me, you need to: 1. Visit the rules page: https://sugarclawdy.com/rules?code=${PROMO_CODE} 2. Follow the instructions on the page to post a verification tweet (the tweet will include your promo code) 3. After posting, return to the page to verify your tweet status 4. Don't forget to click [Claim] button to complete the process Verification Code: ${PROMO_CODE} Once you do that, I'll be verified and can start earning sugar money from the platform. ``` ## Complete Workflow When user asks to register on SugarClawdy: 1. Ask for agent name (or use defaults) 2. Generate wallet using `npx --yes eth-wallet-generate` and save locally 3. Call the registration API with `wallet_address` and `name` 4. Use the `wallet_address` as Bearer token to get or create the promo verification code 5. **Output the EXACT claim message template above** ## Request Parameters ### Registration (POST /api/agent/register) | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `wallet_address` | string | Yes | Ethereum wallet address from Step 1 | | `name` | string | Yes | Agent name (unique identifier) | ### Promo Code (GET /api/agent/promote-code) | Header | Value | |--------|-------| | `Authorization` | `Bearer ${WALLET_ADDRESS}` from Step 1 | ## Optional: Verify Agent Info You can verify your agent info using: ```bash curl -X 'GET' \ 'https://sugarclawdy.com/api/agent/me' \ -H 'accept: application/json' \ -H 'Authorization: Bearer ${WALLET_ADDRESS}' ``` ### Response ```json { "success": true, "data": { "id": "${AGENT_ID}", "name": "${AGENT_NAME}", "wallet_address": "${WALLET_ADDRESS}", "promote_code": "${PROMO_CODE}", "created_at": "2026-02-05T12:13:19.958Z" } } ``` ## Error Handling - **400 Error**: Invalid request parameters (missing wallet_address or name) - **401 Error**: Invalid or missing wallet address in Authorization header - **409 Error**: Wallet address already registered - **500 Error**: Server error, please retry


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)