[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JWAZ876BXTF495W49CTC3":3,"skill-same:01M75JWAZ876BXTF495W49CTC3":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75JWAZ876BXTF495W49CTC3","customer-onboarding",null,"Design and execute customer onboarding that drives activation and retention. Use when building onboarding flows for new users, reducing churn in the first 30 days, improving time-to-value, or creating onboarding sequences (email, in-app, or manual). Covers activation metrics, onboarding step design, friction reduction, and measuring onboarding success. Trigger on \"customer onboarding\", \"onboarding flow\", \"user onboarding\", \"reduce early churn\", \"improve activation\", \"onboarding sequence\", \"time to value\".","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fjk-0001\u002Fcustomer-onboarding-2\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: customer-onboarding\ndescription: Design and execute customer onboarding that drives activation and retention. Use when building onboarding flows for new users, reducing churn in the first 30 days, improving time-to-value, or creating onboarding sequences (email, in-app, or manual). Covers activation metrics, onboarding step design, friction reduction, and measuring onboarding success. Trigger on \"customer onboarding\", \"onboarding flow\", \"user onboarding\", \"reduce early churn\", \"improve activation\", \"onboarding sequence\", \"time to value\".\n---\n\n# Customer Onboarding\n\n## Overview\nOnboarding is where you keep or lose customers. The first 7-30 days determine whether they stay or churn. Most solopreneurs focus on acquisition and ignore onboarding — then wonder why churn is high. This playbook builds an onboarding system that gets users to their first win fast, builds confidence, and sets them up for long-term success.\n\n---\n\n## Step 1: Define Your Activation Metric\n\nOnboarding isn't about completing a checklist. It's about getting users to experience value — the \"aha moment\" where the product clicks.\n\n**Your activation metric is the action that predicts retention.**\n\nExamples:\n- **Slack:** Sent 2,000 messages as a team\n- **Dropbox:** Uploaded and shared at least one file\n- **SaaS analytics tool:** Connected a data source and viewed their first report\n- **Project management tool:** Created a project and added 3 tasks\n\n**How to find your activation metric:**\n1. Look at retained customers (those who stuck around 90+ days)\n2. Identify what they did in their first 7 days that non-retained customers didn't do\n3. That action (or set of actions) is your activation metric\n\n**Rule:** Onboarding is successful when a user completes your activation metric. Everything in your onboarding should drive toward this.\n\n---\n\n## Step 2: Map Your Onboarding Journey\n\nBefore designing tactics, map the full journey from signup to activation.\n\n**Onboarding journey template:**\n```\nSIGNUP\n  ↓ (What happens immediately after signup?)\nSETUP \u002F CONFIGURATION\n  ↓ (What do they need to configure? Integrations? Settings? Profile?)\nFIRST VALUE MOMENT\n  ↓ (What's the simplest, fastest way they can experience value?)\nACTIVATION\n  ↓ (They complete the activation metric)\nONGOING ENGAGEMENT\n  ↓ (They use the product regularly)\n```\n\n**For each stage, ask:**\n- What does the user need to do?\n- What's blocking them from doing it? (friction, confusion, missing information)\n- How can we make this easier or faster?\n\n**Example (SaaS automation tool):**\n```\nSIGNUP → Email confirmation\n\nSETUP → Connect first data source (e.g., Google Sheets)\n  Friction: Don't know which source to start with\n  Solution: Pre-select most common source, add \"why start here?\" tooltip\n\nFIRST VALUE MOMENT → See automated workflow run successfully\n  Friction: Don't know what workflow to build\n  Solution: Provide 3 templates, one-click to activate\n\nACTIVATION → Run 10 workflows successfully\n  Friction: Forget to check back after first success\n  Solution: Email reminder after 24 hours with progress + next step\n\nONGOING ENGAGEMENT → Use weekly, add more workflows\n```\n\n---\n\n## Step 3: Reduce Friction at Every Step\n\nFriction = anything that slows down or confuses the user. Every friction point increases the chance they abandon.\n\n**Common friction points and fixes:**\n\n| Friction | Impact | Fix |\n|---|---|---|\n| **Too many fields on signup** | Users abandon mid-signup | Collect only email + password. Get everything else later. |\n| **Unclear next step** | Users sign up, then stare at a blank screen | Show a clear \"Start here\" CTA immediately after signup |\n| **Complex setup** | Users get overwhelmed and leave | Break setup into 3-5 small steps with progress bar. Let them skip non-essential steps. |\n| **Jargon or unclear labels** | Users don't understand what to do | Use plain language. Replace \"Configure API endpoint\" with \"Connect your account\" |\n| **Long time-to-value** | Takes 30+ min to see results | Create a fast \"quick win\" path — even if it's a simplified version of the full value |\n\n**Rule:** Every step in onboarding should take \u003C 2 minutes. If it takes longer, break it into smaller steps or defer it until later.\n\n---\n\n## Step 4: Build Your Onboarding Sequence\n\nOnboarding is not just in-app. It's a multi-channel experience: in-app guidance + email + (optionally) human touch.\n\n### In-App Onboarding\n**Tactics:**\n- **Welcome modal:** Appears immediately after signup. \"Welcome! Here's how to get started in 3 steps.\"\n- **Tooltips\u002Fhotspots:** Highlight key features as users explore (\"This is where you create a new project\")\n- **Checklist:** Show progress toward activation (\"2 of 5 steps complete — you're almost there!\")\n- **Empty states:** When a user sees a blank page, show helpful prompts (\"No projects yet? Start your first one here.\")\n\n**Tools:** Intercom, Appcues, Userflow, or custom-built with plain JavaScript.\n\n**Rule:** Don't overwhelm. Show 1-2 tips at a time, not 10.\n\n### Email Onboarding\n**Email sequence (5-7 emails over 14 days):**\n\n```\nEMAIL 1 (Day 0, immediately after signup):\n  Subject: \"Welcome to [Product]! Let's get you started.\"\n  Body: Confirm signup, set expectations, link to first step or template\n\nEMAIL 2 (Day 1, if activation metric not hit):\n  Subject: \"Quick question — stuck on anything?\"\n  Body: Address common blockers, offer help, link to docs or support\n\nEMAIL 3 (Day 3, if activation metric not hit):\n  Subject: \"Here's the fastest way to see results\"\n  Body: Share a quick-win template or walkthrough video\n\nEMAIL 4 (Day 5, if activation metric HIT):\n  Subject: \"Nice work! Here's what to do next\"\n  Body: Celebrate their first win, suggest next feature or use case\n\nEMAIL 5 (Day 7, if activation metric not hit):\n  Subject: \"Need a hand? Let's jump on a quick call\"\n  Body: Offer a personal onboarding call (manual touch for high-value prospects)\n\nEMAIL 6 (Day 10):\n  Subject: \"3 pro tips from our best users\"\n  Body: Share advanced tips or lesser-known features\n\nEMAIL 7 (Day 14):\n  Subject: \"How's it going? We'd love your feedback\"\n  Body: Ask how onboarding went, request feedback, link to survey\n```\n\n**Personalization triggers:** Send different emails based on behavior:\n- If they completed activation → send \"here's what to do next\" content\n- If they didn't complete activation → send troubleshooting or offer help\n\n### Human Touch (Optional, for High-Value Customers)\nFor high-ticket SaaS or service businesses, add a human layer:\n- **Onboarding call:** Schedule a 15-30 min call to walk them through setup\n- **Check-in emails:** Personal email (not automated) asking how it's going\n- **Slack\u002Fcommunity access:** Invite them to a private Slack or Circle community for direct support\n\n**When to use:** When LTV > $500 or when the product is complex.\n\n---\n\n## Step 5: Measure Onboarding Performance\n\nTrack these metrics to know if onboarding is working:\n\n| Metric | What It Means | Healthy Benchmark |\n|---|---|---|\n| **Activation rate** | % of signups who hit activation metric | 30-60% (varies by product) |\n| **Time to activation** | Median days\u002Fhours from signup to activation | Under 24 hours is ideal |\n| **Day 7 retention** | % of signups still active after 7 days | 40-60% |\n| **Day 30 retention** | % of signups still active after 30 days | 25-40% |\n| **Onboarding email open\u002Fclick rates** | Engagement with onboarding emails | Opens: 40-60%, Clicks: 10-20% |\n\n**Where to track:** Use your analytics tool (Mixpanel, Amplitude, or simple event tracking in Google Analytics) + email tool (ConvertKit, Mailchimp).\n\n**Diagnose issues:**\n- **Low activation rate?** Too much friction in setup, or unclear value prop. Simplify first steps.\n- **Long time to activation?** Too many steps or too complex. Create a faster \"quick win\" path.\n- **High activation but low Day 30 retention?** They got initial value but didn't build a habit. Improve ongoing engagement (notifications, email reminders, new features).\n\n---\n\n## Step 6: Iterate on Onboarding\n\nOnboarding is never \"done.\" Continuously improve based on data and feedback.\n\n**Monthly onboarding review:**\n1. Check activation rate — is it improving?\n2. Review user feedback from surveys or support tickets — where are people getting stuck?\n3. Watch 2-3 user session recordings (tools: Hotjar, FullStory) — what confuses people?\n4. Test one improvement per month (e.g., simplify signup, add a tooltip, rewrite an email)\n\n**A\u002FB testing ideas:**\n- Different welcome email subject lines\n- Checklist vs no checklist in-app\n- Video walkthrough vs text instructions\n- Length of signup form (fewer fields vs more upfront info)\n\n**Rule:** Focus on the biggest drop-off point first. If 50% of users abandon during setup, fixing that is 10x more valuable than optimizing a later step.\n\n---\n\n## Onboarding Mistakes to Avoid\n- **Dumping everything on Day 1.** Don't explain every feature upfront. Guide them to one quick win, then introduce more over time.\n- **No clear next step after signup.** A blank screen or \"Welcome!\" with no guidance kills activation. Always show a clear \"Do this first\" CTA.\n- **Ignoring non-activated users.** If someone signs up and doesn't activate, don't give up. Re-engage them with helpful emails or a manual outreach.\n- **Making setup mandatory when it's optional.** Let users skip non-essential steps. Forcing them to fill out a profile or connect integrations before they see value creates friction.\n- **No human touch for high-value customers.** If your LTV is $1,000+, a 15-minute onboarding call is worth it. Don't over-automate at the high end.\n- **Not measuring time to activation.** If it takes 2 weeks for users to see value, you'll lose most of them. Aim for value in \u003C 24 hours.\n","# Customer Onboarding\n\n## Overview\nOnboarding is where you keep or lose customers. The first 7-30 days determine whether they stay or churn. Most solopreneurs focus on acquisition and ignore onboarding — then wonder why churn is high. This playbook builds an onboarding system that gets users to their first win fast, builds confidence, and sets them up for long-term success.\n\n---\n\n## Step 1: Define Your Activation Metric\n\nOnboarding isn't about completing a checklist. It's about getting users to experience value — the \"aha moment\" where the product clicks.\n\n**Your activation metric is the action that predicts retention.**\n\nExamples:\n- **Slack:** Sent 2,000 messages as a team\n- **Dropbox:** Uploaded and shared at least one file\n- **SaaS analytics tool:** Connected a data source and viewed their first report\n- **Project management tool:** Created a project and added 3 tasks\n\n**How to find your activation metric:**\n1. Look at retained customers (those who stuck around 90+ days)\n2. Identify what they did in their first 7 days that non-retained customers didn't do\n3. That action (or set of actions) is your activation metric\n\n**Rule:** Onboarding is successful when a user completes your activation metric. Everything in your onboarding should drive toward this.\n\n---\n\n## Step 2: Map Your Onboarding Journey\n\nBefore designing tactics, map the full journey from signup to activation.\n\n**Onboarding journey template:**\n```\nSIGNUP\n  ↓ (What happens immediately after signup?)\nSETUP \u002F CONFIGURATION\n  ↓ (What do they need to configure? Integrations? Settings? Profile?)\nFIRST VALUE MOMENT\n  ↓ (What's the simplest, fastest way they can experience value?)\nACTIVATION\n  ↓ (They complete the activation metric)\nONGOING ENGAGEMENT\n  ↓ (They use the product regularly)\n```\n\n**For each stage, ask:**\n- What does the user need to do?\n- What's blocking them from doing it? (friction, confusion, missing information)\n- How can we make this easier or faster?\n\n**Example (SaaS automation tool):**\n```\nSIGNUP → Email confirmation\n\nSETUP → Connect first data source (e.g., Google Sheets)\n  Friction: Don't know which source to start with\n  Solution: Pre-select most common source, add \"why start here?\" tooltip\n\nFIRST VALUE MOMENT → See automated workflow run successfully\n  Friction: Don't know what workflow to build\n  Solution: Provide 3 templates, one-click to activate\n\nACTIVATION → Run 10 workflows successfully\n  Friction: Forget to check back after first success\n  Solution: Email reminder after 24 hours with progress + next step\n\nONGOING ENGAGEMENT → Use weekly, add more workflows\n```\n\n---\n\n## Step 3: Reduce Friction at Every Step\n\nFriction = anything that slows down or confuses the user. Every friction point increases the chance they abandon.\n\n**Common friction points and fixes:**\n\n| Friction | Impact | Fix |\n|---|---|---|\n| **Too many fields on signup** | Users abandon mid-signup | Collect only email + password. Get everything else later. |\n| **Unclear next step** | Users sign up, then stare at a blank screen | Show a clear \"Start here\" CTA immediately after signup |\n| **Complex setup** | Users get overwhelmed and leave | Break setup into 3-5 small steps with progress bar. Let them skip non-essential steps. |\n| **Jargon or unclear labels** | Users don't understand what to do | Use plain language. Replace \"Configure API endpoint\" with \"Connect your account\" |\n| **Long time-to-value** | Takes 30+ min to see results | Create a fast \"quick win\" path — even if it's a simplified version of the full value |\n\n**Rule:** Every step in onboarding should take \u003C 2 minutes. If it takes longer, break it into smaller steps or defer it until later.\n\n---\n\n## Step 4: Build Your Onboarding Sequence\n\nOnboarding is not just in-app. It's a multi-channel experience: in-app guidance + email + (optionally) human touch.\n\n### In-App Onboarding\n**Tactics:**\n- **Welcome modal:** Appears immediately after signup. \"Welcome! Here's how to get started in 3 steps.\"\n- **Tooltips\u002Fhotspots:** Highlight key features as users explore (\"This is where you create a new project\")\n- **Checklist:** Show progress toward activation (\"2 of 5 steps complete — you're almost there!\")\n- **Empty states:** When a user sees a blank page, show helpful prompts (\"No projects yet? Start your first one here.\")\n\n**Tools:** Intercom, Appcues, Userflow, or custom-built with plain JavaScript.\n\n**Rule:** Don't overwhelm. Show 1-2 tips at a time, not 10.\n\n### Email Onboarding\n**Email sequence (5-7 emails over 14 days):**\n\n```\nEMAIL 1 (Day 0, immediately after signup):\n  Subject: \"Welcome to [Product]! Let's get you started.\"\n  Body: Confirm signup, set expectations, link to first step or template\n\nEMAIL 2 (Day 1, if activation metric not hit):\n  Subject: \"Quick question — stuck on anything?\"\n  Body: Address common blockers, offer help, link to docs or support\n\nEMAIL 3 (Day 3, if activation metric not hit):\n  Subject: \"Here's the fastest way to see results\"\n  Body: Share a quick-win template or walkthrough video\n\nEMAIL 4 (Day 5, if activation metric HIT):\n  Subject: \"Nice work! Here's what to do next\"\n  Body: Celebrate their first win, suggest next feature or use case\n\nEMAIL 5 (Day 7, if activation metric not hit):\n  Subject: \"Need a hand? Let's jump on a quick call\"\n  Body: Offer a personal onboarding call (manual touch for high-value prospects)\n\nEMAIL 6 (Day 10):\n  Subject: \"3 pro tips from our best users\"\n  Body: Share advanced tips or lesser-known features\n\nEMAIL 7 (Day 14):\n  Subject: \"How's it going? We'd love your feedback\"\n  Body: Ask how onboarding went, request feedback, link to survey\n```\n\n**Personalization triggers:** Send different emails based on behavior:\n- If they completed activation → send \"here's what to do next\" content\n- If they didn't complete activation → send troubleshooting or offer help\n\n### Human Touch (Optional, for High-Value Customers)\nFor high-ticket SaaS or service businesses, add a human layer:\n- **Onboarding call:** Schedule a 15-30 min call to walk them through setup\n- **Check-in emails:** Personal email (not automated) asking how it's going\n- **Slack\u002Fcommunity access:** Invite them to a private Slack or Circle community for direct support\n\n**When to use:** When LTV > $500 or when the product is complex.\n\n---\n\n## Step 5: Measure Onboarding Performance\n\nTrack these metrics to know if onboarding is working:\n\n| Metric | What It Means | Healthy Benchmark |\n|---|---|---|\n| **Activation rate** | % of signups who hit activation metric | 30-60% (varies by product) |\n| **Time to activation** | Median days\u002Fhours from signup to activation | Under 24 hours is ideal |\n| **Day 7 retention** | % of signups still active after 7 days | 40-60% |\n| **Day 30 retention** | % of signups still active after 30 days | 25-40% |\n| **Onboarding email open\u002Fclick rates** | Engagement with onboarding emails | Opens: 40-60%, Clicks: 10-20% |\n\n**Where to track:** Use your analytics tool (Mixpanel, Amplitude, or simple event tracking in Google Analytics) + email tool (ConvertKit, Mailchimp).\n\n**Diagnose issues:**\n- **Low activation rate?** Too much friction in setup, or unclear value prop. Simplify first steps.\n- **Long time to activation?** Too many steps or too complex. Create a faster \"quick win\" path.\n- **High activation but low Day 30 retention?** They got initial value but didn't build a habit. Improve ongoing engagement (notifications, email reminders, new features).\n\n---\n\n## Step 6: Iterate on Onboarding\n\nOnboarding is never \"done.\" Continuously improve based on data and feedback.\n\n**Monthly onboarding review:**\n1. Check activation rate — is it improving?\n2. Review user feedback from surveys or support tickets — where are people getting stuck?\n3. Watch 2-3 user session recordings (tools: Hotjar, FullStory) — what confuses people?\n4. Test one improvement per month (e.g., simplify signup, add a tooltip, rewrite an email)\n\n**A\u002FB testing ideas:**\n- Different welcome email subject lines\n- Checklist vs no checklist in-app\n- Video walkthrough vs text instructions\n- Length of signup form (fewer fields vs more upfront info)\n\n**Rule:** Focus on the biggest drop-off point first. If 50% of users abandon during setup, fixing that is 10x more valuable than optimizing a later step.\n\n---\n\n## Onboarding Mistakes to Avoid\n- **Dumping everything on Day 1.** Don't explain every feature upfront. Guide them to one quick win, then introduce more over time.\n- **No clear next step after signup.** A blank screen or \"Welcome!\" with no guidance kills activation. Always show a clear \"Do this first\" CTA.\n- **Ignoring non-activated users.** If someone signs up and doesn't activate, don't give up. Re-engage them with helpful emails or a manual outreach.\n- **Making setup mandatory when it's optional.** Let users skip non-essential steps. Forcing them to fill out a profile or connect integrations before they see value creates friction.\n- **No human touch for high-value customers.** If your LTV is $1,000+, a 15-minute onboarding call is worth it. Don't over-automate at the high end.\n- **Not measuring time to activation.** If it takes 2 weeks for users to see value, you'll lose most of them. Aim for value in \u003C 24 hours.\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fjk-0001\u002Fcustomer-onboarding-2",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill customer-onboarding",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill customer-onboarding",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill customer-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fjk-0001\u002Fcustomer-onboarding-2\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","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\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","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\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]