[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FTB1K31FG11ASAT9Z0DBAE":3,"skill-same:01M6FTB1K31FG11ASAT9Z0DBAE":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6FTB1K31FG11ASAT9Z0DBAE","share_usecase",null,"Share your OpenClaw use case to clawusecase.com. Analyzes your recent work and creates a submission for the community.","kbarbel640-del\u002Fskills","kbarbel640-del","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255315490?v=4","01M6CJPPQGCCESXMG3K7BBGQ5J","01M6CJPPX2PB2BCZERFVM2C2B3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002FSKILL.md",[],[18,19,20,21,22,23,24,25],"share","share usecase","openclaw","rex","work","use","community","case","2026-11-10 10:12:30",false,"---\nname: share_usecase\ndescription: \"Share your OpenClaw use case to clawusecase.com. Analyzes your recent work and creates a submission for the community.\"\nauthor: \"Rex ?\"\nversion: \"2.0.1\"\n---\n\n# Share Use Case Skill\n\nThis skill helps you share your OpenClaw use cases to [clawusecase.com](https:\u002F\u002Fclawusecase.com).\n\n## When to Use\n\nTrigger this skill when the user wants to share a use case they've built with OpenClaw. They might say:\n- \"\u002Fshare_usecase\"\n- \"I want to share this use case\"\n- \"Let me submit this to clawusecase\"\n- \"Share what I just built\"\n\n**Important:** When users choose to get credit via OAuth, automatically poll for their connection completion. Don't make them tell you they've connected - detect it automatically and proceed with submission.\n\n**Implementation requirement:** You MUST actively monitor the polling loop and send an immediate message when connection is detected. Do not run polling silently in the background - check results frequently and respond the moment you see a successful credential. The user should see \"✅ Connected as @username!\" within seconds of completing OAuth, without having to ask.\n\n## How It Works\n\n### 1. Greet and Explain\n\nWhen the user triggers `\u002Fshare_usecase`, start with a friendly greeting:\n\n```\n? Share Your Use Case\n\nHey! clawusecase.com is a community showcase where OpenClaw users share what they've built to inspire others.\n\nLet me look at what you've been working on and draft a use case for you...\n```\n\n### 2. Analyze Recent Context\n\nLook back at the conversation history (last 50-100 messages or past few hours) to understand what the user built. Look for:\n- What problem they were trying to solve\n- What tools\u002Fintegrations they used (GitHub, Stripe, Resend, etc.)\n- How they solved it\n- Any requirements or setup needed\n\n### 3. Generate Use Case Structure\n\nCreate a well-structured use case with these fields:\n\n**Required:**\n- `title` (50-100 chars) - Clear, descriptive title of what was built\n- `hook` (100-200 chars) - One-sentence summary that grabs attention\n- `problem` (200-500 chars) - What problem this solves\n- `solution` (300-800 chars) - How it works, what was built\n- `category` - One of: \"Productivity\", \"Development\", \"Business\u002FSaaS\", \"Home Automation\", \"Social\u002FContent\", \"Data & Analytics\", \"Fun\"\n- `skills` (array) - Tools\u002Ftechnologies used (e.g., [\"GitHub\", \"Stripe\", \"Resend\"])\n\n**Optional:**\n- `requirements` - What you need to use this (API keys, accounts, etc.)\n\n### 4. Normalize Tools\u002FSkills\n\nBefore finalizing, normalize tool names using `normalize-tools.js`:\n\n```bash\nnode normalize-tools.js \"github,stripe api,resend email\"\n```\n\nThis ensures consistent naming (e.g., \"github\" → \"GitHub\", \"stripe api\" → \"Stripe\").\n\n### 5. Show Preview and Get Approval\n\nPresent the generated use case to the user in a clean format:\n\n```\n? Use Case Draft\n\nTitle: Email notifications for Pro subscriptions\nHook: Sends welcome emails automatically when users upgrade\n\nProblem: No email notifications when users subscribe to Pro plan\nSolution: Built Resend integration with React Email templates, hooked into Stripe webhooks for subscription events\n\nCategory: Business\u002FSaaS\nTools: GitHub, Stripe, Resend\nRequirements: Resend account, Stripe webhooks configured\n\nWould you like to:\n- Submit as-is\n- Edit any fields\n- Cancel\n```\n\nIf they want to edit, iterate until they're happy.\n\n### 6. Ask About Attribution\n\nOnce they approve the content, ask about attribution:\n\n```\nWould you like to be credited for this submission?\n\nOptions:\n1. ✅ Yes, credit me (connect Twitter or GitHub)\n2. ? No, submit anonymously\n\nIf you choose credit, you'll get a link on the live use case and build your profile in the community!\n```\n\n**If they choose credit:**\n\nGenerate OAuth links and send them:\n\n```\nGreat! Connect your account to get credit:\n\n? X (Twitter): [init Twitter OAuth and get URL]\n? GitHub: [init GitHub OAuth and get URL]\n\nClick one of the links above to authenticate. I'll detect when you're connected and submit automatically!\n```\n\n**Auto-detect connection:**\n\n**⚠️ CRITICAL: You MUST actively monitor and respond to polling results in real-time. Do NOT run polling in the background and wait for system messages. Check the process output directly and respond immediately.**\n\nImmediately after sending OAuth links, start polling and watch for completion:\n\n**Recommended approach:**\n```bash\ncd \u002Fpath\u002Fto\u002Fskill\nfor i in {1..24}; do\n  # Try to get credential\n  RESULT=$(node get-credential.js --token [oauth_token] 2>&1)\n  \n  if echo \"$RESULT\" | grep -q '\"username\"'; then\n    # SUCCESS! Parse the credential\n    USERNAME=$(echo \"$RESULT\" | grep -o '\"username\":\"[^\"]*\"' | cut -d'\"' -f4)\n    PLATFORM=$(echo \"$RESULT\" | grep -o '\"platform\":\"[^\"]*\"' | cut -d'\"' -f4)\n    \n    # IMMEDIATELY notify user (don't wait for background processes!)\n    # Send this message RIGHT NOW before continuing\n    echo \"User should see: ✅ Connected as @$USERNAME!\"\n    \n    # Store the full credential for submission\n    CREDENTIAL=\"$RESULT\"\n    break\n  fi\n  \n  # Not ready yet, wait 5 seconds\n  if [ $i -lt 24 ]; then\n    sleep 5\n  fi\ndone\n\n# After loop, check if we got a credential\nif [ -z \"$CREDENTIAL\" ]; then\n  echo \"Timeout - credential not received within 2 minutes\"\nfi\n```\n\n**Critical implementation notes:**\n\n1. **DO NOT** use `exec(..., background: true)` for polling - you won't see results in time\n2. **DO** run polling synchronously or check process output immediately\n3. **IMMEDIATELY** send \"✅ Connected as @username!\" message when detected\n4. **DO NOT** wait for system messages or background process completion\n5. Parse the credential JSON directly from the command output\n\n**Example flow:**\n1. Send OAuth links to user\n2. **Immediately start polling** (synchronous checks every 5 seconds)\n3. **Each iteration:** Check if credential exists\n4. **The INSTANT it's found:** Send message \"✅ Connected as @username! Submitting your use case now...\"\n5. Extract username\u002Fplatform from credential JSON\n6. Proceed with submission\n\n**If timeout (2 minutes):**\n```\n⏰ Still waiting for your connection. Take your time - I'll keep checking for another 2 minutes!\n```\n\nThen continue polling for another 24 attempts.\n\n**If they choose anonymous:**\n\nProceed with anonymous submission (no author info).\n\n### 7. Submit to API\n\nUse `submit.js` to POST to the API:\n\n**With attribution:**\n```bash\nnode submit.js \\\n  --title \"Email notifications for Pro subscriptions\" \\\n  --hook \"Sends welcome emails automatically when users upgrade\" \\\n  --problem \"No email notifications when users subscribe to Pro plan\" \\\n  --solution \"Built Resend integration with React Email templates...\" \\\n  --category \"Business\u002FSaaS\" \\\n  --skills \"GitHub,Stripe,Resend\" \\\n  --requirements \"Resend account, Stripe webhooks configured\" \\\n  --author-username \"josephliow\" \\\n  --author-handle \"josephliow\" \\\n  --author-platform \"twitter\" \\\n  --author-link \"https:\u002F\u002Ftwitter.com\u002Fjosephliow\"\n```\n\n**Anonymous:**\n```bash\nnode submit.js \\\n  --title \"Email notifications for Pro subscriptions\" \\\n  --hook \"Sends welcome emails automatically when users upgrade\" \\\n  --problem \"No email notifications when users subscribe to Pro plan\" \\\n  --solution \"Built Resend integration with React Email templates...\" \\\n  --category \"Business\u002FSaaS\" \\\n  --skills \"GitHub,Stripe,Resend\" \\\n  --requirements \"Resend account, Stripe webhooks configured\" \\\n  --anonymous\n```\n\n### 8. Confirm Submission\n\nIf successful, share the link with the user:\n```\n✅ Use case submitted successfully!\n\nView it here: https:\u002F\u002Fclawusecase.com\u002Fcases\u002Femail-notifications-for-pro-subscriptions\n\nThanks for sharing with the community! ?\n```\n\n## Error Handling\n\n### Rate Limiting\nIf you get a 429 error:\n```\n⏰ You've hit the submission limit (10 per day).\nTry again tomorrow or contact support if you need to submit more.\n```\n\n### Validation Errors\nIf fields are invalid (title too short, solution too brief):\n```\n❌ Submission failed: Title must be at least 20 characters\n\nLet's fix that. What would you like the title to be?\n```\n\n### API Errors\nFor other errors, show the error message and offer to retry.\n\n## Tips for Good Use Cases\n\nHelp users create high-quality submissions:\n\n**Good Title:**\n- ✅ \"Email notifications for Pro subscriptions\"\n- ❌ \"Email thing I built\"\n\n**Good Hook:**\n- ✅ \"Sends welcome emails automatically when users upgrade\"\n- ❌ \"Sends emails\"\n\n**Good Problem:**\n- ✅ \"Users who upgraded to Pro weren't getting confirmation emails, causing confusion and support tickets\"\n- ❌ \"No emails\"\n\n**Good Solution:**\n- ✅ \"Built a Resend integration with React Email templates. Set up Stripe webhooks to trigger on subscription.created events. Template includes upgrade details and next steps.\"\n- ❌ \"Made it send emails with Stripe\"\n\n## Category Guidelines\n\nHelp users pick the right category:\n\n- **Productivity** - Task management, scheduling, reminders, automation\n- **Development** - CI\u002FCD, code review, deployment, testing\n- **Business\u002FSaaS** - Customer management, billing, analytics, marketing\n- **Home Automation** - Smart home, IoT, cameras, sensors\n- **Social\u002FContent** - Social media, content creation, publishing\n- **Data & Analytics** - Reports, dashboards, data processing\n- **Fun** - Games, experiments, creative projects, humor\n\n## Rate Limiting\n\nUsers can submit up to **10 use cases per day**. The API tracks by `authorUsername` (or IP for anonymous).\n\nIf they hit the limit, suggest:\n- Wait until tomorrow\n- Make sure each submission is unique and valuable\n- Contact support if they need a higher limit\n\n## Quality Guidelines\n\nThe API has automatic quality filtering. Submissions must:\n- Title: 20-200 characters\n- Hook: 50-500 characters  \n- Problem: 100-2000 characters\n- Solution: 200-5000 characters\n- At least 1 skill\u002Ftool\n- Valid category\n\nHelp users meet these requirements before submitting.\n\n## Example Interaction\n\n```\nUser: I just built email notifications for when users subscribe\nYou: ? Share Your Use Case\n\nHey! clawusecase.com is a community showcase where OpenClaw users share what they've built to inspire others.\n\nLet me look at what you've been working on and draft a use case for you...\n\n[analyzes recent conversation]\n\n? Use Case Draft\n\nTitle: Email notifications for Pro subscriptions\nHook: Automatically sends welcome emails when users upgrade to Pro\n\nProblem: Users upgrading to Pro weren't receiving confirmation emails, leading to confusion and support tickets about whether their payment went through.\n\nSolution: Built a Resend email integration with custom React Email templates. Connected to Stripe webhooks to listen for subscription.created events. The welcome email includes upgrade confirmation, receipt, and next steps for accessing Pro features.\n\nCategory: Business\u002FSaaS\nTools: Stripe, Resend, React, GitHub\nRequirements: Resend account, Stripe webhooks configured\n\nWould you like to:\n- Submit as-is\n- Edit any fields\n- Cancel\n\nUser: Looks perfect!\nYou: Great! Would you like to be credited for this submission?\n\nOptions:\n1. ✅ Yes, credit me (connect Twitter or GitHub)\n2. ? No, submit anonymously\n\nUser: Yes, credit me\nYou: Awesome! Connect your account to get credit:\n\n? X (Twitter): https:\u002F\u002Fclawusecase.com\u002Fauth\u002Fconnect?token=abc123&platform=twitter\n? GitHub: https:\u002F\u002Fclawusecase.com\u002Fauth\u002Fconnect?token=def456&platform=github\n\nClick one of the links above. I'll detect when you're connected and submit automatically!\n\n[User clicks link and completes OAuth]\n\nYou: ✅ Connected as @josephliow!\n\nSubmitting your use case now...\n\n[retrieves credential, submits]\n\n✅ Use case submitted successfully!\n\nView it here: https:\u002F\u002Fclawusecase.com\u002Fcases\u002Femail-notifications-for-pro-subscriptions\n\nYour use case is now live for the community to see. Thanks for sharing! ?\n```\n\n## Files in This Skill\n\n- `SKILL.md` - This file (instructions)\n- `submit.js` - Submits use case to clawusecase.com API\n- `get-credential.js` - Retrieves OAuth credential from Convex after auth\n- `poll-credential.sh` - Helper script that polls for credential completion\n- `normalize-tools.js` - Normalizes tool\u002Fskill names\n- `README.md` - User documentation\n- `config.json` - Skill configuration\n\n## Troubleshooting\n\n**\"Command not found: node\"**\nNode.js is required. Install it: `brew install node` (macOS) or from nodejs.org\n\n**\"Failed to connect to API\"**\nCheck internet connection and that clawusecase.com is accessible.\n\n**\"OAuth token not found\"**\nThe token might have expired (10 min timeout). Generate a fresh OAuth link.\n","# Share Use Case Skill\n\nThis skill helps you share your OpenClaw use cases to [clawusecase.com](https:\u002F\u002Fclawusecase.com).\n\n## When to Use\n\nTrigger this skill when the user wants to share a use case they've built with OpenClaw. They might say:\n- \"\u002Fshare_usecase\"\n- \"I want to share this use case\"\n- \"Let me submit this to clawusecase\"\n- \"Share what I just built\"\n\n**Important:** When users choose to get credit via OAuth, automatically poll for their connection completion. Don't make them tell you they've connected - detect it automatically and proceed with submission.\n\n**Implementation requirement:** You MUST actively monitor the polling loop and send an immediate message when connection is detected. Do not run polling silently in the background - check results frequently and respond the moment you see a successful credential. The user should see \"✅ Connected as @username!\" within seconds of completing OAuth, without having to ask.\n\n## How It Works\n\n### 1. Greet and Explain\n\nWhen the user triggers `\u002Fshare_usecase`, start with a friendly greeting:\n\n```\n? Share Your Use Case\n\nHey! clawusecase.com is a community showcase where OpenClaw users share what they've built to inspire others.\n\nLet me look at what you've been working on and draft a use case for you...\n```\n\n### 2. Analyze Recent Context\n\nLook back at the conversation history (last 50-100 messages or past few hours) to understand what the user built. Look for:\n- What problem they were trying to solve\n- What tools\u002Fintegrations they used (GitHub, Stripe, Resend, etc.)\n- How they solved it\n- Any requirements or setup needed\n\n### 3. Generate Use Case Structure\n\nCreate a well-structured use case with these fields:\n\n**Required:**\n- `title` (50-100 chars) - Clear, descriptive title of what was built\n- `hook` (100-200 chars) - One-sentence summary that grabs attention\n- `problem` (200-500 chars) - What problem this solves\n- `solution` (300-800 chars) - How it works, what was built\n- `category` - One of: \"Productivity\", \"Development\", \"Business\u002FSaaS\", \"Home Automation\", \"Social\u002FContent\", \"Data & Analytics\", \"Fun\"\n- `skills` (array) - Tools\u002Ftechnologies used (e.g., [\"GitHub\", \"Stripe\", \"Resend\"])\n\n**Optional:**\n- `requirements` - What you need to use this (API keys, accounts, etc.)\n\n### 4. Normalize Tools\u002FSkills\n\nBefore finalizing, normalize tool names using `normalize-tools.js`:\n\n```bash\nnode normalize-tools.js \"github,stripe api,resend email\"\n```\n\nThis ensures consistent naming (e.g., \"github\" → \"GitHub\", \"stripe api\" → \"Stripe\").\n\n### 5. Show Preview and Get Approval\n\nPresent the generated use case to the user in a clean format:\n\n```\n? Use Case Draft\n\nTitle: Email notifications for Pro subscriptions\nHook: Sends welcome emails automatically when users upgrade\n\nProblem: No email notifications when users subscribe to Pro plan\nSolution: Built Resend integration with React Email templates, hooked into Stripe webhooks for subscription events\n\nCategory: Business\u002FSaaS\nTools: GitHub, Stripe, Resend\nRequirements: Resend account, Stripe webhooks configured\n\nWould you like to:\n- Submit as-is\n- Edit any fields\n- Cancel\n```\n\nIf they want to edit, iterate until they're happy.\n\n### 6. Ask About Attribution\n\nOnce they approve the content, ask about attribution:\n\n```\nWould you like to be credited for this submission?\n\nOptions:\n1. ✅ Yes, credit me (connect Twitter or GitHub)\n2. ? No, submit anonymously\n\nIf you choose credit, you'll get a link on the live use case and build your profile in the community!\n```\n\n**If they choose credit:**\n\nGenerate OAuth links and send them:\n\n```\nGreat! Connect your account to get credit:\n\n? X (Twitter): [init Twitter OAuth and get URL]\n? GitHub: [init GitHub OAuth and get URL]\n\nClick one of the links above to authenticate. I'll detect when you're connected and submit automatically!\n```\n\n**Auto-detect connection:**\n\n**⚠️ CRITICAL: You MUST actively monitor and respond to polling results in real-time. Do NOT run polling in the background and wait for system messages. Check the process output directly and respond immediately.**\n\nImmediately after sending OAuth links, start polling and watch for completion:\n\n**Recommended approach:**\n```bash\ncd \u002Fpath\u002Fto\u002Fskill\nfor i in {1..24}; do\n  # Try to get credential\n  RESULT=$(node get-credential.js --token [oauth_token] 2>&1)\n  \n  if echo \"$RESULT\" | grep -q '\"username\"'; then\n    # SUCCESS! Parse the credential\n    USERNAME=$(echo \"$RESULT\" | grep -o '\"username\":\"[^\"]*\"' | cut -d'\"' -f4)\n    PLATFORM=$(echo \"$RESULT\" | grep -o '\"platform\":\"[^\"]*\"' | cut -d'\"' -f4)\n    \n    # IMMEDIATELY notify user (don't wait for background processes!)\n    # Send this message RIGHT NOW before continuing\n    echo \"User should see: ✅ Connected as @$USERNAME!\"\n    \n    # Store the full credential for submission\n    CREDENTIAL=\"$RESULT\"\n    break\n  fi\n  \n  # Not ready yet, wait 5 seconds\n  if [ $i -lt 24 ]; then\n    sleep 5\n  fi\ndone\n\n# After loop, check if we got a credential\nif [ -z \"$CREDENTIAL\" ]; then\n  echo \"Timeout - credential not received within 2 minutes\"\nfi\n```\n\n**Critical implementation notes:**\n\n1. **DO NOT** use `exec(..., background: true)` for polling - you won't see results in time\n2. **DO** run polling synchronously or check process output immediately\n3. **IMMEDIATELY** send \"✅ Connected as @username!\" message when detected\n4. **DO NOT** wait for system messages or background process completion\n5. Parse the credential JSON directly from the command output\n\n**Example flow:**\n1. Send OAuth links to user\n2. **Immediately start polling** (synchronous checks every 5 seconds)\n3. **Each iteration:** Check if credential exists\n4. **The INSTANT it's found:** Send message \"✅ Connected as @username! Submitting your use case now...\"\n5. Extract username\u002Fplatform from credential JSON\n6. Proceed with submission\n\n**If timeout (2 minutes):**\n```\n⏰ Still waiting for your connection. Take your time - I'll keep checking for another 2 minutes!\n```\n\nThen continue polling for another 24 attempts.\n\n**If they choose anonymous:**\n\nProceed with anonymous submission (no author info).\n\n### 7. Submit to API\n\nUse `submit.js` to POST to the API:\n\n**With attribution:**\n```bash\nnode submit.js \\\n  --title \"Email notifications for Pro subscriptions\" \\\n  --hook \"Sends welcome emails automatically when users upgrade\" \\\n  --problem \"No email notifications when users subscribe to Pro plan\" \\\n  --solution \"Built Resend integration with React Email templates...\" \\\n  --category \"Business\u002FSaaS\" \\\n  --skills \"GitHub,Stripe,Resend\" \\\n  --requirements \"Resend account, Stripe webhooks configured\" \\\n  --author-username \"josephliow\" \\\n  --author-handle \"josephliow\" \\\n  --author-platform \"twitter\" \\\n  --author-link \"https:\u002F\u002Ftwitter.com\u002Fjosephliow\"\n```\n\n**Anonymous:**\n```bash\nnode submit.js \\\n  --title \"Email notifications for Pro subscriptions\" \\\n  --hook \"Sends welcome emails automatically when users upgrade\" \\\n  --problem \"No email notifications when users subscribe to Pro plan\" \\\n  --solution \"Built Resend integration with React Email templates...\" \\\n  --category \"Business\u002FSaaS\" \\\n  --skills \"GitHub,Stripe,Resend\" \\\n  --requirements \"Resend account, Stripe webhooks configured\" \\\n  --anonymous\n```\n\n### 8. Confirm Submission\n\nIf successful, share the link with the user:\n```\n✅ Use case submitted successfully!\n\nView it here: https:\u002F\u002Fclawusecase.com\u002Fcases\u002Femail-notifications-for-pro-subscriptions\n\nThanks for sharing with the community! ?\n```\n\n## Error Handling\n\n### Rate Limiting\nIf you get a 429 error:\n```\n⏰ You've hit the submission limit (10 per day).\nTry again tomorrow or contact support if you need to submit more.\n```\n\n### Validation Errors\nIf fields are invalid (title too short, solution too brief):\n```\n❌ Submission failed: Title must be at least 20 characters\n\nLet's fix that. What would you like the title to be?\n```\n\n### API Errors\nFor other errors, show the error message and offer to retry.\n\n## Tips for Good Use Cases\n\nHelp users create high-quality submissions:\n\n**Good Title:**\n- ✅ \"Email notifications for Pro subscriptions\"\n- ❌ \"Email thing I built\"\n\n**Good Hook:**\n- ✅ \"Sends welcome emails automatically when users upgrade\"\n- ❌ \"Sends emails\"\n\n**Good Problem:**\n- ✅ \"Users who upgraded to Pro weren't getting confirmation emails, causing confusion and support tickets\"\n- ❌ \"No emails\"\n\n**Good Solution:**\n- ✅ \"Built a Resend integration with React Email templates. Set up Stripe webhooks to trigger on subscription.created events. Template includes upgrade details and next steps.\"\n- ❌ \"Made it send emails with Stripe\"\n\n## Category Guidelines\n\nHelp users pick the right category:\n\n- **Productivity** - Task management, scheduling, reminders, automation\n- **Development** - CI\u002FCD, code review, deployment, testing\n- **Business\u002FSaaS** - Customer management, billing, analytics, marketing\n- **Home Automation** - Smart home, IoT, cameras, sensors\n- **Social\u002FContent** - Social media, content creation, publishing\n- **Data & Analytics** - Reports, dashboards, data processing\n- **Fun** - Games, experiments, creative projects, humor\n\n## Rate Limiting\n\nUsers can submit up to **10 use cases per day**. The API tracks by `authorUsername` (or IP for anonymous).\n\nIf they hit the limit, suggest:\n- Wait until tomorrow\n- Make sure each submission is unique and valuable\n- Contact support if they need a higher limit\n\n## Quality Guidelines\n\nThe API has automatic quality filtering. Submissions must:\n- Title: 20-200 characters\n- Hook: 50-500 characters  \n- Problem: 100-2000 characters\n- Solution: 200-5000 characters\n- At least 1 skill\u002Ftool\n- Valid category\n\nHelp users meet these requirements before submitting.\n\n## Example Interaction\n\n```\nUser: I just built email notifications for when users subscribe\nYou: ? Share Your Use Case\n\nHey! clawusecase.com is a community showcase where OpenClaw users share what they've built to inspire others.\n\nLet me look at what you've been working on and draft a use case for you...\n\n[analyzes recent conversation]\n\n? Use Case Draft\n\nTitle: Email notifications for Pro subscriptions\nHook: Automatically sends welcome emails when users upgrade to Pro\n\nProblem: Users upgrading to Pro weren't receiving confirmation emails, leading to confusion and support tickets about whether their payment went through.\n\nSolution: Built a Resend email integration with custom React Email templates. Connected to Stripe webhooks to listen for subscription.created events. The welcome email includes upgrade confirmation, receipt, and next steps for accessing Pro features.\n\nCategory: Business\u002FSaaS\nTools: Stripe, Resend, React, GitHub\nRequirements: Resend account, Stripe webhooks configured\n\nWould you like to:\n- Submit as-is\n- Edit any fields\n- Cancel\n\nUser: Looks perfect!\nYou: Great! Would you like to be credited for this submission?\n\nOptions:\n1. ✅ Yes, credit me (connect Twitter or GitHub)\n2. ? No, submit anonymously\n\nUser: Yes, credit me\nYou: Awesome! Connect your account to get credit:\n\n? X (Twitter): https:\u002F\u002Fclawusecase.com\u002Fauth\u002Fconnect?token=abc123&platform=twitter\n? GitHub: https:\u002F\u002Fclawusecase.com\u002Fauth\u002Fconnect?token=def456&platform=github\n\nClick one of the links above. I'll detect when you're connected and submit automatically!\n\n[User clicks link and completes OAuth]\n\nYou: ✅ Connected as @josephliow!\n\nSubmitting your use case now...\n\n[retrieves credential, submits]\n\n✅ Use case submitted successfully!\n\nView it here: https:\u002F\u002Fclawusecase.com\u002Fcases\u002Femail-notifications-for-pro-subscriptions\n\nYour use case is now live for the community to see. Thanks for sharing! ?\n```\n\n## Files in This Skill\n\n- `SKILL.md` - This file (instructions)\n- `submit.js` - Submits use case to clawusecase.com API\n- `get-credential.js` - Retrieves OAuth credential from Convex after auth\n- `poll-credential.sh` - Helper script that polls for credential completion\n- `normalize-tools.js` - Normalizes tool\u002Fskill names\n- `README.md` - User documentation\n- `config.json` - Skill configuration\n\n## Troubleshooting\n\n**\"Command not found: node\"**\nNode.js is required. Install it: `brew install node` (macOS) or from nodejs.org\n\n**\"Failed to connect to API\"**\nCheck internet connection and that clawusecase.com is accessible.\n\n**\"OAuth token not found\"**\nThe token might have expired (10 min timeout). Generate a fresh OAuth link.\n",{"name":5,"author":31,"version":32,"description":7},"Rex ?","2.0.1","main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fjosephl37\u002Fshare-usecase",0,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del","2026-08-23 22:39:37",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add kbarbel640-del\u002Fskills --skill share_usecase",{"tool":46,"command":47},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill share_usecase",{"tool":49,"command":50},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill share_usecase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002FSKILL.md",true,[54,60,64,70,74,78,82,86],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"_meta.json","REFERENCE","参考文档",460,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002F_meta.json",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"config.json",122,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002Fconfig.json",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"get-credential.js","SCRIPT","脚本",2988,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002Fget-credential.js",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"normalize-tools.js",4832,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002Fnormalize-tools.js",{"path":75,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":76,"sourceHtmlUrl":77},"package.json",521,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002Fpackage.json",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"poll-credential.sh",866,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002Fpoll-credential.sh",{"path":83,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":84,"sourceHtmlUrl":85},"README.md",4287,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002FREADME.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"submit.js",5586,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjosephl37\u002Fshare-usecase\u002Fsubmit.js",[91,122,149,170,176,196],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":26},"01M6G8J55967D6281ACMKAKTEQ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"crowd prompting","prompting","api","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":133,"publishedAt":26},"01M6G8J0PKPAYVET6BWE8W4C26","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[134,105,135,136,137,138,139,140,141,142,20,143,144,145,146,147,148,110,23],"dilemm ai","arena","analyze","browser","openclaw agent","create","automation","browser automation","bot","design","strategy","headless","compete","submit","matchmaking",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":26},"01M6G8HWAF3K9SW7NP3Z83CPJ6","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, and submit comments. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, or submitting paper reviews via API at http:\u002F\u002F150.158.152.82:8000.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Fweak-accept\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000021","资料检索与研究",[159,160,161,162,163,164,165,106,166,147,23,167,105,168,169],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http","via",{"skillNo":171,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":26},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[174],{"categoryNo":156,"categoryName":157,"taxonomyType":131,"taxonomyTypeDesc":132},[162,161,160,159,169,164,165,106,163,147,23,166,167,105,168],{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":26},"01M6G8HM95Y64JNVFC2HN4E2BG","git-summary","Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzweack\u002Fgit-summary\u002FSKILL.md",[],[183,184,185,186,187,188,189,190,191,192,193,194,195],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":206,"publishedAt":26},"01M6G8HGEGF05CNEJCGVYFSC4R","agent-constitution","Interact with AgentConstitution governance contracts on Base Sepolia. Check compliance, read rules, log actions, query governance state.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fztsalexey\u002Fagent-constitution\u002FSKILL.md",[202,203],{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},{"categoryNo":204,"categoryName":205,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000037","律师与法务",[207,208,209,210,106,211,212,33,213,167,214,215,216,217,218,119,219,220,221],"agent constitution","constitution","contracts","tree","query","base","log","check","Rules","projects","compliance","actions","state","governance","github"]