AGENT SKILL

myvibe-publish

Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.

License 许可
MIT
最近更新
2026-06-07
Stars
★ 0
Forks
1

01 前言 Front Matter

name
myvibe-publish
description
Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.

03 SKILL.md 正文

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

Option Alias Description
--file <path> -f Path to HTML file or ZIP archive
--dir <path> -d Directory to compress and publish
--url <url> -u URL to import and publish
--hub <url> -h MyVibe URL (default: https://www.myvibe.so/)
--title <title> -t Project title
--desc <desc> Project description
--visibility <vis> -v Visibility: public or private (default: public)
--did <did> Vibe DID for version update (overrides auto-detection)
--new Force create new Vibe, ignore publish history

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

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

  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}

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)

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

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

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

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:

  • 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

04 同仓库更多 Skills

javimosch
javimosch/open-claw-skills

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.

★ 0
javimosch
javimosch/open-claw-skills

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 <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).

★ 0
javimosch
javimosch/open-claw-skills

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 <subcommand>). 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/UltraHonk zero-knowledge proofs.

★ 0
javimosch
javimosch/open-claw-skills

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).

★ 0
javimosch
javimosch/open-claw-skills

moldium

Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.

★ 0
javimosch
javimosch/open-claw-skills

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/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.

★ 0