# Send MyVibe Skills to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - 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. ## Suggested prompts ### New install ```text 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 ```text 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. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "myvibe-skills", "name": "MyVibe Skills", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/zhuzhuyule/myvibe-skills", "canonicalUrl": "https://clawhub.ai/zhuzhuyule/myvibe-skills", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/myvibe-skills", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=myvibe-skills", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "scripts/publish.mjs", "scripts/package-lock.json", "scripts/package.json", "scripts/utils/upload.mjs", "scripts/utils/upload-image.mjs" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/myvibe-skills" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/myvibe-skills", "downloadUrl": "https://openagent3.xyz/downloads/myvibe-skills", "agentUrl": "https://openagent3.xyz/skills/myvibe-skills/agent", "manifestUrl": "https://openagent3.xyz/skills/myvibe-skills/agent.json", "briefUrl": "https://openagent3.xyz/skills/myvibe-skills/agent.md" } } ``` ## 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 -fPath to HTML file or ZIP archive--dir -dDirectory to compress and publish--url -uURL to import and publish--hub -hMyVibe URL (default: https://www.myvibe.so/)--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 ## Trust - Source: tencent - Verification: Indexed source record - Publisher: zhuzhuyule - Version: 1.0.0 ## Source health - Status: healthy - Source download looks usable. - Yavira can redirect you to the upstream package for this source. - Health scope: source - Reason: direct_download_ok - Checked at: 2026-04-23T16:43:11.935Z - Expires at: 2026-04-30T16:43:11.935Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/myvibe-skills) - [Send to Agent page](https://openagent3.xyz/skills/myvibe-skills/agent) - [JSON manifest](https://openagent3.xyz/skills/myvibe-skills/agent.json) - [Markdown brief](https://openagent3.xyz/skills/myvibe-skills/agent.md) - [Download page](https://openagent3.xyz/downloads/myvibe-skills)