Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Content Creation
MyVibe Skills
Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.
skill openclawclawhub Free
Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, scripts/publish.mjs, scripts/package-lock.json, scripts/package.json, scripts/utils/upload.mjs, scripts/utils/upload-image.mjs
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- zhuzhuyule
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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
OptionAliasDescription--file <path>-fPath to HTML file or ZIP archive--dir <path>-dDirectory to compress and publish--url <url>-uURL to import and publish--hub <url>-hMyVibe URL (default: https://www.myvibe.so/)--title <title>-tProject title--desc <desc>Project description--visibility <vis>-vVisibility: public or private (default: public)--did <did>Vibe DID for version update (overrides auto-detection)--newForce create new Vibe, ignore publish history
Workflow Overview
Detect Project Type โ if no build needed, start screenshot in background Build (if needed) โ then start screenshot in background Metadata Analysis โ extract title, description, tags Confirm Publish โ show metadata, get user confirmation Execute Publish โ script auto-reads screenshot result 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
CheckProject TypeNext Step--file with HTML/ZIPSingle Fileโ Start screenshot, then Step 3Has dist/, build/, or out/ with index.htmlPre-builtโ Step 2 (confirm rebuild)Has package.json with build script, no outputBuildableโ Step 2 (build first)Multiple package.json or workspace configMonorepoโ Step 2 (select app)Has index.html at root, no package.jsonStaticโ 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": Install agent-browser: npm install -g agent-browser && agent-browser install Re-run the screenshot command (same command as above, run_in_background: true) 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.
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 TypeMatch MethodtechStackTagsMatch package.json dependencies against tag slugplatformTagsFrom conversation context (Claude Code, Cursor, etc.)modelTagsFrom conversation context (Claude 3.5 Sonnet, GPT-4, etc.)categoryTagsInfer 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
ErrorActionDependencies missingRun npm install in scripts directory401/403 Auth errorToken auto-cleared, re-run to authorizeBuild failedAnalyze error, offer fix, or publish source as-isScreenshot failedSkip coverImage, proceed without itagent-browser missingRun npm install -g agent-browser && agent-browser installScript execution failed (network/sandbox)Check if network permissions are enabled. Add sandbox_permissions=require_escalated and retryPrivate mode is only available for Creator and Studio usersSee "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?" OptionLabelDescription1Publish as PublicYour Vibe will be visible to everyone. You can change this later after upgrading.2View Upgrade OptionsOpen 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
Category context
Writing, remixing, publishing, visual generation, and marketing content production.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Scripts2 Config1 Docs
- SKILL.md
- scripts/publish.mjs
- scripts/utils/upload-image.mjs
- scripts/utils/upload.mjs
- scripts/package-lock.json
- scripts/package.json