MyVibe Publish

Publish web content (HTML file, ZIP archive, or directory) to MyVibe.

Prerequisites

• Node.js 18 or later
• All script executions in this skill require network access. Always run Bash commands with sandbox_permissions=require_escalated to ensure network permissions are enabled.
• The deployment and screenshot generation may take a few minutes. Use a 10-minute (600000ms) timeout for publish commands.

Usage

/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

Options

Workflow Overview

1. Detect Project Type → if no build needed, start screenshot in background
2. Build (if needed) → then start screenshot in background
3. Metadata Analysis → extract title, description, tags
4. Confirm Publish → show metadata, get user confirmation
5. Execute Publish → script auto-reads screenshot result
6. Return Result → show publish URL

First tool call - execute in parallel:

• Read: source file or main files in directory
• Bash: git remote get-url origin 2>/dev/null || echo "Not a git repo"
• Bash: node {skill_path}/scripts/utils/fetch-tags.mjs --hub {hub}

---

Step 1: Detect Project Type

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":

1. Install agent-browser: npm install -g agent-browser && agent-browser install
2. Re-run the screenshot command (same command as above, run_in_background: true)
3. Check again with TaskOutput (block: false) to confirm it's running

This ensures the screenshot can complete successfully in the background while you continue with metadata analysis.

---

Step 2: Build (if needed)

Detect package manager from lock files, build command from package.json scripts.

Use AskUserQuestion to confirm:

• Pre-built: "Rebuild or use existing output?"
• Buildable: "Build before publishing?"
• Monorepo: "Which app to publish?"

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.

---

Step 3: Metadata Analysis

Extract title

Priority: <title> → og:title → package.json name → first <h1>

Generate description (50-150 words, story-style)

Cover: Why (motivation) → What (functionality) → Journey (optional)

Sources: conversation history, README.md, source code, package.json, git log

Guidelines:

• Natural, conversational tone
• Focus on value and story, not technical specs
• Avoid generic "A web app built with React"

Extract githubRepo

From git remote or package.json repository field. Convert SSH to HTTPS format.

Match tags

Fetch tags: node {skill_path}/scripts/utils/fetch-tags.mjs --hub {hub}

---

Step 4: Confirm Publish

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"

---

Step 5: Execute Publish

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 updates
• coverImage auto-read from /tmp/myvibe-screenshot-{hash}.json
• Screenshot result file cleaned up after publish

---

Step 6: Return Result

After publish script completes, check the script output for these messages:

Success Message

Always include the Vibe URL in your response:

Published successfully!
🔗 [URL]

Upgrade Prompt (Important)

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 Handling

Private Mode Error Handling

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?"

Actions based on selection:

• Option 1: Re-run publish with visibility: "public", inform user the Vibe is now public
• Option 2: Display the pricing URL {hub}/pricing and stop the publish flow

Notes

• Always analyze content for meaningful title/description - never use directory names
• Confirm with user before publishing
• Default hub: https://www.myvibe.so/
• Tags fetched fresh from API on each publish
• Publish history in ~/.myvibe/published.yaml for auto version updates
• Use --new to force new Vibe instead of updating