[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M778B2YWR63528VXVEKD09YF":3,"skill-same:01M778B2YWR63528VXVEKD09YF":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},"01M778B2YWR63528VXVEKD09YF","myvibe-publish",null,"Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.","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\u002Fzhuzhuyule\u002Fmyvibe-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: myvibe-publish\ndescription: Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.\n---\n\n# MyVibe Publish\n\nPublish web content (HTML file, ZIP archive, or directory) to MyVibe.\n\n## Prerequisites\n\n- Node.js 18 or later\n- All script executions in this skill require network access. Always run Bash commands with `sandbox_permissions=require_escalated` to ensure network permissions are enabled.\n- The deployment and screenshot generation may take a few minutes. Use a 10-minute (600000ms) timeout for publish commands.\n\n## Usage\n\n```bash\n\u002Fmyvibe:myvibe-publish --file .\u002Fdist.zip      # Publish ZIP\n\u002Fmyvibe:myvibe-publish --file .\u002Findex.html    # Publish HTML\n\u002Fmyvibe:myvibe-publish --dir .\u002Fdist           # Publish directory\n\u002Fmyvibe:myvibe-publish --url https:\u002F\u002Fexample.com\u002Fapp  # Import from URL\n\u002Fmyvibe:myvibe-publish --dir .\u002Fdist --new     # Force new Vibe\n\u002Fmyvibe:myvibe-publish --dir .\u002Fdist --did z2qaXXX    # Update specific Vibe\n```\n\n## Options\n\n| Option | Alias | Description |\n|--------|-------|-------------|\n| `--file \u003Cpath>` | `-f` | Path to HTML file or ZIP archive |\n| `--dir \u003Cpath>` | `-d` | Directory to compress and publish |\n| `--url \u003Curl>` | `-u` | URL to import and publish |\n| `--hub \u003Curl>` | `-h` | MyVibe URL (default: https:\u002F\u002Fwww.myvibe.so\u002F) |\n| `--title \u003Ctitle>` | `-t` | Project title |\n| `--desc \u003Cdesc>` | | Project description |\n| `--visibility \u003Cvis>` | `-v` | Visibility: public or private (default: public) |\n| `--did \u003Cdid>` | | Vibe DID for version update (overrides auto-detection) |\n| `--new` | | Force create new Vibe, ignore publish history |\n\n## Workflow Overview\n\n1. **Detect Project Type** → if no build needed, start screenshot in background\n2. **Build** (if needed) → then start screenshot in background\n3. **Metadata Analysis** → extract title, description, tags\n4. **Confirm Publish** → show metadata, get user confirmation\n5. **Execute Publish** → script auto-reads screenshot result\n6. **Return Result** → show publish URL\n\n**First tool call - execute in parallel:**\n- `Read`: source file or main files in directory\n- `Bash`: `git remote get-url origin 2>\u002Fdev\u002Fnull || echo \"Not a git repo\"`\n- `Bash`: `node {skill_path}\u002Fscripts\u002Futils\u002Ffetch-tags.mjs --hub {hub}`\n\n---\n\n## Step 1: Detect Project Type\n\n| Check | Project Type | Next Step |\n|-------|-------------|-----------|\n| `--file` with HTML\u002FZIP | **Single File** | → Start screenshot, then Step 3 |\n| Has `dist\u002F`, `build\u002F`, or `out\u002F` with index.html | **Pre-built** | → Step 2 (confirm rebuild) |\n| Has `package.json` with build script, no output | **Buildable** | → Step 2 (build first) |\n| Multiple `package.json` or workspace config | **Monorepo** | → Step 2 (select app) |\n| Has `index.html` at root, no `package.json` | **Static** | → Start screenshot, then Step 3 |\n\n**Start screenshot for non-build projects** (run_in_background: true):\n\nFor directory source (`--dir`):\n```bash\nnode {skill_path}\u002Fscripts\u002Futils\u002Fgenerate-screenshot.mjs --dir {publish_target} --hub {hub}\n```\n\nFor single file source (`--file`):\n```bash\nnode {skill_path}\u002Fscripts\u002Futils\u002Fgenerate-screenshot.mjs --file {publish_target} --hub {hub}\n```\n\nIMPORTANT: Use `--file` when the source is a single HTML file, and `--dir` when it is a directory. The flag must match the `source.type` in the publish config so that both scripts calculate the same hash for the screenshot result file.\n\n**After starting the screenshot background task**, use `TaskOutput` (with `block: false`) to check the task output before proceeding. If the output contains \"agent-browser is not installed\" or \"Chromium is not installed\":\n\n1. Install agent-browser: `npm install -g agent-browser && agent-browser install`\n2. Re-run the screenshot command (same command as above, run_in_background: true)\n3. Check again with `TaskOutput` (block: false) to confirm it's running\n\nThis ensures the screenshot can complete successfully in the background while you continue with metadata analysis.\n\n---\n\n## Step 2: Build (if needed)\n\nDetect package manager from lock files, build command from package.json scripts.\n\nUse `AskUserQuestion` to confirm:\n- **Pre-built**: \"Rebuild or use existing output?\"\n- **Buildable**: \"Build before publishing?\"\n- **Monorepo**: \"Which app to publish?\"\n\nAfter build completes, start screenshot in background (same check as Step 1: use `TaskOutput` block: false to verify agent-browser is available, install if needed, then retry), then proceed to Step 3.\n\n---\n\n## Step 3: Metadata Analysis\n\n### Extract title\nPriority: `\u003Ctitle>` → `og:title` → package.json name → first `\u003Ch1>`\n\n### Generate description (50-150 words, story-style)\n\nCover: **Why** (motivation) → **What** (functionality) → **Journey** (optional)\n\nSources: conversation history, README.md, source code, package.json, git log\n\nGuidelines:\n- Natural, conversational tone\n- Focus on value and story, not technical specs\n- Avoid generic \"A web app built with React\"\n\n### Extract githubRepo\nFrom git remote or package.json repository field. Convert SSH to HTTPS format.\n\n### Match tags\n\nFetch tags: `node {skill_path}\u002Fscripts\u002Futils\u002Ffetch-tags.mjs --hub {hub}`\n\n| Tag Type | Match Method |\n|----------|--------------|\n| **techStackTags** | Match package.json dependencies against tag slug |\n| **platformTags** | From conversation context (Claude Code, Cursor, etc.) |\n| **modelTags** | From conversation context (Claude 3.5 Sonnet, GPT-4, etc.) |\n| **categoryTags** | Infer from project (game libs → game, charts → viz) |\n\n---\n\n## Step 4: Confirm Publish\n\nDisplay metadata and use `AskUserQuestion`:\n\n```\nPublishing to MyVibe:\n──────────────────────\nTitle: [value]\n\nDescription:\n[50-150 word story]\n\nGitHub: [URL or \"Not detected\"]\nCover Image: [Will be included if ready]\n\nTags: Tech Stack: [...] | Platform: [...] | Category: [...] | Model: [...]\n```\n\nOptions: \"Publish\" \u002F \"Edit details\"\n\n---\n\n## Step 5: Execute Publish\n\n**Check dependencies**: If `scripts\u002Fnode_modules` missing, run `npm install` first.\nThe publish script automatically reads the screenshot result file. Execute publish directly:\n\nPass config via stdin:\n\n```bash\nnode {skill_path}\u002Fscripts\u002Fpublish.mjs --config-stdin \u003C\u003C'EOF'\n{\n  \"source\": { \"type\": \"dir\", \"path\": \".\u002Fdist\", \"did\": \"z2qaXXXX\" },\n  \"hub\": \"https:\u002F\u002Fwww.myvibe.so\",\n  \"metadata\": {\n    \"title\": \"My App\",\n    \"description\": \"Story description here\",\n    \"visibility\": \"public\",\n    \"githubRepo\": \"https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo\",\n    \"platformTags\": [1, 2],\n    \"techStackTags\": [3, 4],\n    \"categoryTags\": [5],\n    \"modelTags\": [6]\n  }\n}\nEOF\n```\n\n- `did` optional - for explicit version updates\n- `coverImage` auto-read from `\u002Ftmp\u002Fmyvibe-screenshot-{hash}.json`\n- Screenshot result file cleaned up after publish\n\n---\n\n## Step 6: Return Result\n\nAfter publish script completes, **check the script output** for these messages:\n\n### Success Message\nAlways include the Vibe URL in your response:\n```\nPublished successfully!\n🔗 [URL]\n```\n\n### Upgrade Prompt (Important)\nThe script prints an upgrade prompt when updating an existing Vibe without version history enabled:\n```\n📦 Previous version overwritten. Want to keep version history?\n   Upgrade to Creator → {hub}\u002Fpricing\n```\n\n**You MUST include this upgrade information in your response to the user if the script output contains it.** This helps free-tier users discover the version history feature.\n\n---\n\n## Error Handling\n\n| Error | Action |\n|-------|--------|\n| Dependencies missing | Run `npm install` in scripts directory |\n| 401\u002F403 Auth error | Token auto-cleared, re-run to authorize |\n| Build failed | Analyze error, offer fix, or publish source as-is |\n| Screenshot failed | Skip coverImage, proceed without it |\n| agent-browser missing | Run `npm install -g agent-browser && agent-browser install` |\n| Script execution failed (network\u002Fsandbox) | Check if network permissions are enabled. Add `sandbox_permissions=require_escalated` and retry |\n| Private mode is only available for Creator and Studio users | See \"Private Mode Error Handling\" below |\n\n### Private Mode Error Handling\n\nWhen publishing with `visibility: private` fails with \"Private mode is only available for Creator and Studio users\", use `AskUserQuestion` to let the user choose:\n\n**Question:** \"Private publishing requires a Creator or Studio subscription. How would you like to proceed?\"\n\n| Option | Label | Description |\n|--------|-------|-------------|\n| 1 | Publish as Public | Your Vibe will be visible to everyone. You can change this later after upgrading. |\n| 2 | View Upgrade Options | Open the pricing page to explore subscription plans with private publishing. |\n\n**Actions based on selection:**\n- **Option 1**: Re-run publish with `visibility: \"public\"`, inform user the Vibe is now public\n- **Option 2**: Display the pricing URL `{hub}\u002Fpricing` and stop the publish flow\n\n## Notes\n\n- Always analyze content for meaningful title\u002Fdescription - never use directory names\n- Confirm with user before publishing\n- Default hub: https:\u002F\u002Fwww.myvibe.so\u002F\n- Tags fetched fresh from API on each publish\n- Publish history in `~\u002F.myvibe\u002Fpublished.yaml` for auto version updates\n- Use `--new` to force new Vibe instead of updating\n","# MyVibe Publish\n\nPublish web content (HTML file, ZIP archive, or directory) to MyVibe.\n\n## Prerequisites\n\n- Node.js 18 or later\n- All script executions in this skill require network access. Always run Bash commands with `sandbox_permissions=require_escalated` to ensure network permissions are enabled.\n- The deployment and screenshot generation may take a few minutes. Use a 10-minute (600000ms) timeout for publish commands.\n\n## Usage\n\n```bash\n\u002Fmyvibe:myvibe-publish --file .\u002Fdist.zip      # Publish ZIP\n\u002Fmyvibe:myvibe-publish --file .\u002Findex.html    # Publish HTML\n\u002Fmyvibe:myvibe-publish --dir .\u002Fdist           # Publish directory\n\u002Fmyvibe:myvibe-publish --url https:\u002F\u002Fexample.com\u002Fapp  # Import from URL\n\u002Fmyvibe:myvibe-publish --dir .\u002Fdist --new     # Force new Vibe\n\u002Fmyvibe:myvibe-publish --dir .\u002Fdist --did z2qaXXX    # Update specific Vibe\n```\n\n## Options\n\n| Option | Alias | Description |\n|--------|-------|-------------|\n| `--file \u003Cpath>` | `-f` | Path to HTML file or ZIP archive |\n| `--dir \u003Cpath>` | `-d` | Directory to compress and publish |\n| `--url \u003Curl>` | `-u` | URL to import and publish |\n| `--hub \u003Curl>` | `-h` | MyVibe URL (default: https:\u002F\u002Fwww.myvibe.so\u002F) |\n| `--title \u003Ctitle>` | `-t` | Project title |\n| `--desc \u003Cdesc>` | | Project description |\n| `--visibility \u003Cvis>` | `-v` | Visibility: public or private (default: public) |\n| `--did \u003Cdid>` | | Vibe DID for version update (overrides auto-detection) |\n| `--new` | | Force create new Vibe, ignore publish history |\n\n## Workflow Overview\n\n1. **Detect Project Type** → if no build needed, start screenshot in background\n2. **Build** (if needed) → then start screenshot in background\n3. **Metadata Analysis** → extract title, description, tags\n4. **Confirm Publish** → show metadata, get user confirmation\n5. **Execute Publish** → script auto-reads screenshot result\n6. **Return Result** → show publish URL\n\n**First tool call - execute in parallel:**\n- `Read`: source file or main files in directory\n- `Bash`: `git remote get-url origin 2>\u002Fdev\u002Fnull || echo \"Not a git repo\"`\n- `Bash`: `node {skill_path}\u002Fscripts\u002Futils\u002Ffetch-tags.mjs --hub {hub}`\n\n---\n\n## Step 1: Detect Project Type\n\n| Check | Project Type | Next Step |\n|-------|-------------|-----------|\n| `--file` with HTML\u002FZIP | **Single File** | → Start screenshot, then Step 3 |\n| Has `dist\u002F`, `build\u002F`, or `out\u002F` with index.html | **Pre-built** | → Step 2 (confirm rebuild) |\n| Has `package.json` with build script, no output | **Buildable** | → Step 2 (build first) |\n| Multiple `package.json` or workspace config | **Monorepo** | → Step 2 (select app) |\n| Has `index.html` at root, no `package.json` | **Static** | → Start screenshot, then Step 3 |\n\n**Start screenshot for non-build projects** (run_in_background: true):\n\nFor directory source (`--dir`):\n```bash\nnode {skill_path}\u002Fscripts\u002Futils\u002Fgenerate-screenshot.mjs --dir {publish_target} --hub {hub}\n```\n\nFor single file source (`--file`):\n```bash\nnode {skill_path}\u002Fscripts\u002Futils\u002Fgenerate-screenshot.mjs --file {publish_target} --hub {hub}\n```\n\nIMPORTANT: Use `--file` when the source is a single HTML file, and `--dir` when it is a directory. The flag must match the `source.type` in the publish config so that both scripts calculate the same hash for the screenshot result file.\n\n**After starting the screenshot background task**, use `TaskOutput` (with `block: false`) to check the task output before proceeding. If the output contains \"agent-browser is not installed\" or \"Chromium is not installed\":\n\n1. Install agent-browser: `npm install -g agent-browser && agent-browser install`\n2. Re-run the screenshot command (same command as above, run_in_background: true)\n3. Check again with `TaskOutput` (block: false) to confirm it's running\n\nThis ensures the screenshot can complete successfully in the background while you continue with metadata analysis.\n\n---\n\n## Step 2: Build (if needed)\n\nDetect package manager from lock files, build command from package.json scripts.\n\nUse `AskUserQuestion` to confirm:\n- **Pre-built**: \"Rebuild or use existing output?\"\n- **Buildable**: \"Build before publishing?\"\n- **Monorepo**: \"Which app to publish?\"\n\nAfter build completes, start screenshot in background (same check as Step 1: use `TaskOutput` block: false to verify agent-browser is available, install if needed, then retry), then proceed to Step 3.\n\n---\n\n## Step 3: Metadata Analysis\n\n### Extract title\nPriority: `\u003Ctitle>` → `og:title` → package.json name → first `\u003Ch1>`\n\n### Generate description (50-150 words, story-style)\n\nCover: **Why** (motivation) → **What** (functionality) → **Journey** (optional)\n\nSources: conversation history, README.md, source code, package.json, git log\n\nGuidelines:\n- Natural, conversational tone\n- Focus on value and story, not technical specs\n- Avoid generic \"A web app built with React\"\n\n### Extract githubRepo\nFrom git remote or package.json repository field. Convert SSH to HTTPS format.\n\n### Match tags\n\nFetch tags: `node {skill_path}\u002Fscripts\u002Futils\u002Ffetch-tags.mjs --hub {hub}`\n\n| Tag Type | Match Method |\n|----------|--------------|\n| **techStackTags** | Match package.json dependencies against tag slug |\n| **platformTags** | From conversation context (Claude Code, Cursor, etc.) |\n| **modelTags** | From conversation context (Claude 3.5 Sonnet, GPT-4, etc.) |\n| **categoryTags** | Infer from project (game libs → game, charts → viz) |\n\n---\n\n## Step 4: Confirm Publish\n\nDisplay metadata and use `AskUserQuestion`:\n\n```\nPublishing to MyVibe:\n──────────────────────\nTitle: [value]\n\nDescription:\n[50-150 word story]\n\nGitHub: [URL or \"Not detected\"]\nCover Image: [Will be included if ready]\n\nTags: Tech Stack: [...] | Platform: [...] | Category: [...] | Model: [...]\n```\n\nOptions: \"Publish\" \u002F \"Edit details\"\n\n---\n\n## Step 5: Execute Publish\n\n**Check dependencies**: If `scripts\u002Fnode_modules` missing, run `npm install` first.\nThe publish script automatically reads the screenshot result file. Execute publish directly:\n\nPass config via stdin:\n\n```bash\nnode {skill_path}\u002Fscripts\u002Fpublish.mjs --config-stdin \u003C\u003C'EOF'\n{\n  \"source\": { \"type\": \"dir\", \"path\": \".\u002Fdist\", \"did\": \"z2qaXXXX\" },\n  \"hub\": \"https:\u002F\u002Fwww.myvibe.so\",\n  \"metadata\": {\n    \"title\": \"My App\",\n    \"description\": \"Story description here\",\n    \"visibility\": \"public\",\n    \"githubRepo\": \"https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo\",\n    \"platformTags\": [1, 2],\n    \"techStackTags\": [3, 4],\n    \"categoryTags\": [5],\n    \"modelTags\": [6]\n  }\n}\nEOF\n```\n\n- `did` optional - for explicit version updates\n- `coverImage` auto-read from `\u002Ftmp\u002Fmyvibe-screenshot-{hash}.json`\n- Screenshot result file cleaned up after publish\n\n---\n\n## Step 6: Return Result\n\nAfter publish script completes, **check the script output** for these messages:\n\n### Success Message\nAlways include the Vibe URL in your response:\n```\nPublished successfully!\n🔗 [URL]\n```\n\n### Upgrade Prompt (Important)\nThe script prints an upgrade prompt when updating an existing Vibe without version history enabled:\n```\n📦 Previous version overwritten. Want to keep version history?\n   Upgrade to Creator → {hub}\u002Fpricing\n```\n\n**You MUST include this upgrade information in your response to the user if the script output contains it.** This helps free-tier users discover the version history feature.\n\n---\n\n## Error Handling\n\n| Error | Action |\n|-------|--------|\n| Dependencies missing | Run `npm install` in scripts directory |\n| 401\u002F403 Auth error | Token auto-cleared, re-run to authorize |\n| Build failed | Analyze error, offer fix, or publish source as-is |\n| Screenshot failed | Skip coverImage, proceed without it |\n| agent-browser missing | Run `npm install -g agent-browser && agent-browser install` |\n| Script execution failed (network\u002Fsandbox) | Check if network permissions are enabled. Add `sandbox_permissions=require_escalated` and retry |\n| Private mode is only available for Creator and Studio users | See \"Private Mode Error Handling\" below |\n\n### Private Mode Error Handling\n\nWhen publishing with `visibility: private` fails with \"Private mode is only available for Creator and Studio users\", use `AskUserQuestion` to let the user choose:\n\n**Question:** \"Private publishing requires a Creator or Studio subscription. How would you like to proceed?\"\n\n| Option | Label | Description |\n|--------|-------|-------------|\n| 1 | Publish as Public | Your Vibe will be visible to everyone. You can change this later after upgrading. |\n| 2 | View Upgrade Options | Open the pricing page to explore subscription plans with private publishing. |\n\n**Actions based on selection:**\n- **Option 1**: Re-run publish with `visibility: \"public\"`, inform user the Vibe is now public\n- **Option 2**: Display the pricing URL `{hub}\u002Fpricing` and stop the publish flow\n\n## Notes\n\n- Always analyze content for meaningful title\u002Fdescription - never use directory names\n- Confirm with user before publishing\n- Default hub: https:\u002F\u002Fwww.myvibe.so\u002F\n- Tags fetched fresh from API on each publish\n- Publish history in `~\u002F.myvibe\u002Fpublished.yaml` for auto version updates\n- Use `--new` to force new Vibe instead of updating\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fzhuzhuyule\u002Fmyvibe-skills",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 myvibe-publish",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill myvibe-publish",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill myvibe-publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzhuzhuyule\u002Fmyvibe-skills\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"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":19},"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",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"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",[],[]]