myvibe-skillsPublish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.
Install via ClawdBot CLI:
clawdbot install zhuzhuyule/myvibe-skillsPublish web content (HTML file, ZIP archive, or directory) to MyVibe.
sandbox_permissions=require_escalated to ensure network permissions are enabled./myvibe:myvibe-publish --file ./dist.zip # Publish ZIP
/myvibe:myvibe-publish --file ./index.html # Publish HTML
/myvibe:myvibe-publish --dir ./dist # Publish directory
/myvibe:myvibe-publish --url https://example.com/app # Import from URL
/myvibe:myvibe-publish --dir ./dist --new # Force new Vibe
/myvibe:myvibe-publish --dir ./dist --did z2qaXXX # Update specific Vibe
| Option | Alias | Description |
|--------|-------|-------------|
| --file | -f | Path to HTML file or ZIP archive |
| --dir | -d | Directory to compress and publish |
| --url | -u | URL to import and publish |
| --hub | -h | MyVibe URL (default: https://www.myvibe.so/) |
| --title | -t | Project title |
| --desc | | Project description |
| --visibility | -v | Visibility: public or private (default: public) |
| --did | | Vibe DID for version update (overrides auto-detection) |
| --new | | Force create new Vibe, ignore publish history |
First tool call - execute in parallel:
Read: source file or main files in directoryBash: git remote get-url origin 2>/dev/null || echo "Not a git repo"Bash: node {skill_path}/scripts/utils/fetch-tags.mjs --hub {hub}| Check | Project Type | Next Step |
|-------|-------------|-----------|
| --file with HTML/ZIP | Single File | β Start screenshot, then Step 3 |
| Has dist/, build/, or out/ with index.html | Pre-built | β Step 2 (confirm rebuild) |
| Has package.json with build script, no output | Buildable | β Step 2 (build first) |
| Multiple package.json or workspace config | Monorepo | β Step 2 (select app) |
| Has index.html at root, no package.json | Static | β Start screenshot, then Step 3 |
Start screenshot for non-build projects (run_in_background: true):
For directory source (--dir):
node {skill_path}/scripts/utils/generate-screenshot.mjs --dir {publish_target} --hub {hub}
For single file source (--file):
node {skill_path}/scripts/utils/generate-screenshot.mjs --file {publish_target} --hub {hub}
IMPORTANT: 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.
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":
npm install -g agent-browser && agent-browser installTaskOutput (block: false) to confirm it's runningThis ensures the screenshot can complete successfully in the background while you continue with metadata analysis.
Detect package manager from lock files, build command from package.json scripts.
Use AskUserQuestion to confirm:
After 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.
Priority: β og:title β package.json name β first
Cover: Why (motivation) β What (functionality) β Journey (optional)
Sources: conversation history, README.md, source code, package.json, git log
Guidelines:
From git remote or package.json repository field. Convert SSH to HTTPS format.
Fetch tags: node {skill_path}/scripts/utils/fetch-tags.mjs --hub {hub}
| Tag Type | Match Method |
|----------|--------------|
| techStackTags | Match package.json dependencies against tag slug |
| platformTags | From conversation context (Claude Code, Cursor, etc.) |
| modelTags | From conversation context (Claude 3.5 Sonnet, GPT-4, etc.) |
| categoryTags | Infer from project (game libs β game, charts β viz) |
Display metadata and use AskUserQuestion:
Publishing to MyVibe:
ββββββββββββββββββββββ
Title: [value]
Description:
[50-150 word story]
GitHub: [URL or "Not detected"]
Cover Image: [Will be included if ready]
Tags: Tech Stack: [...] | Platform: [...] | Category: [...] | Model: [...]
Options: "Publish" / "Edit details"
Check dependencies: If scripts/node_modules missing, run npm install first.
The publish script automatically reads the screenshot result file. Execute publish directly:
Pass config via stdin:
node {skill_path}/scripts/publish.mjs --config-stdin <<'EOF'
{
"source": { "type": "dir", "path": "./dist", "did": "z2qaXXXX" },
"hub": "https://www.myvibe.so",
"metadata": {
"title": "My App",
"description": "Story description here",
"visibility": "public",
"githubRepo": "https://github.com/user/repo",
"platformTags": [1, 2],
"techStackTags": [3, 4],
"categoryTags": [5],
"modelTags": [6]
}
}
EOF
did optional - for explicit version updatescoverImage auto-read from /tmp/myvibe-screenshot-{hash}.jsonAfter publish script completes, check the script output for these messages:
Always include the Vibe URL in your response:
Published successfully!
π [URL]
The script prints an upgrade prompt when updating an existing Vibe without version history enabled:
π¦ Previous version overwritten. Want to keep version history?
Upgrade to Creator β {hub}/pricing
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.
| Error | Action |
|-------|--------|
| Dependencies missing | Run npm install in scripts directory |
| 401/403 Auth error | Token auto-cleared, re-run to authorize |
| Build failed | Analyze error, offer fix, or publish source as-is |
| Screenshot failed | Skip coverImage, proceed without it |
| agent-browser missing | Run npm install -g agent-browser && agent-browser install |
| Script execution failed (network/sandbox) | Check if network permissions are enabled. Add sandbox_permissions=require_escalated and retry |
| Private mode is only available for Creator and Studio users | See "Private Mode Error Handling" below |
When publishing with visibility: private fails with "Private mode is only available for Creator and Studio users", use AskUserQuestion to let the user choose:
Question: "Private publishing requires a Creator or Studio subscription. How would you like to proceed?"
| Option | Label | Description |
|--------|-------|-------------|
| 1 | Publish as Public | Your Vibe will be visible to everyone. You can change this later after upgrading. |
| 2 | View Upgrade Options | Open the pricing page to explore subscription plans with private publishing. |
Actions based on selection:
visibility: "public", inform user the Vibe is now public{hub}/pricing and stop the publish flow~/.myvibe/published.yaml for auto version updates--new to force new Vibe instead of updatingAI Usage Analysis
Analysis is being generated⦠refresh in a few seconds.
Advanced filesystem operations - listing, searching, batch processing, and directory analysis for Clawdbot
Perform advanced filesystem tasks including listing, recursive searching by name or content, batch copying/moving/deleting files, and analyzing directory siz...
Essential SSH commands for secure remote access, key management, tunneling, and file transfers.
Extract text from PDF files for LLM processing
The directory for AI agent services. Discover tools, platforms, and infrastructure built for agents.
Advanced filesystem operations - listing, searching, batch processing, and directory analysis for Clawdbot