**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}`

**First tool call - check dependencies and gather info in parallel:**
-`Bash`: `test -d {skill_path}/scripts/node_modules || npm install --prefix {skill_path}/scripts`
-`Read`: source file or main files in directory
-`Bash`: `git remote get-url origin 2>/dev/null || echo "Not a git repo"`
 
After dependencies are confirmed, fetch tags:
-`Bash`: `node {skill_path}/scripts/utils/fetch-tags.mjs --hub {hub}`

**Check dependencies**: If `scripts/node_modules` missing, run `npm install` first.
The publish script automatically reads the screenshot result file. Execute publish directly:

The publish script automatically reads the screenshot result file. Execute publish directly:

git add skills/myvibe-publish/SKILL.md
git commit -m "fix(publish): move dependency check before any script execution
 
Previously dependencies were checked only at Step 5, causing fetch-tags
and generate-screenshot to fail first, then retry after install.
Now dependencies are checked as the very first action."

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

### Generate title
 
MyVibe generates page URLs from the title (e.g. "Interactive Solar System" → `interactive-solar-system`), so the title must be meaningful and descriptive.
 
**Step 1 - Extract raw title candidates:**
-`<title>` tag content
-`og:title` meta content
-`package.json` name field
-First `<h1>` content
 
**Step 2 - Evaluate and generate:**
If the extracted title is generic or meaningless (e.g. "Document", "Untitled", "index", "app", "React App", "Vite App", single characters, or package-name-style like "my-app"), generate a better title based on:
-What the project actually does (from source code, README, conversation context)
-The visual content and purpose of the page
 
**Title requirements:**
-2-6 words, concise and descriptive
-Describes the content/purpose, not the technology (e.g. "Interactive Solar System" not "Three.js Demo")
-No filler words like "app", "demo", "project", "page" unless essential to meaning
-English words, proper capitalization (Title Case)
-If `--title` was explicitly provided by user, always use it as-is

git add skills/myvibe-publish/SKILL.md
git commit -m "feat(publish): generate meaningful URL-friendly titles instead of raw extraction
 
MyVibe generates page URLs from titles. Simple extraction often produces
generic titles like 'Document' or 'React App'. Now the AI evaluates
extracted candidates and generates descriptive titles when needed."

      case "--skip-upload":
        options.skipUpload = true;
        break;

    if (config.source.skipUpload) {
      options.skipUpload = true;
    }

    skipUpload = false,

    if (skipUpload) {
      // Skip upload mode: use existing DID directly
      if (!explicitDid) {
        throw new Error("--skip-upload requires --did <DID> to specify the existing upload");
      }
      did = explicitDid;
      needsConversion = false; // Already uploaded and converted
      console.log(chalk.cyan(`Skipping upload, using existing DID: ${did}`));
    } else if (url) {
      // URL import mode
      const result = await createVibeFromUrl(url, hub, accessToken, {
        title,
        description: desc,
        visibility,
      });
      did = result.did;
      needsConversion = false;
    } else {
      // File or directory upload mode
      let filePath;
      if (dir) {
        const dirPath = resolve(dir);
        if (!existsSync(dirPath)) {
          throw new Error(`Directory not found: ${dirPath}`);
        }
        const dirStat = await stat(dirPath);
        if (!dirStat.isDirectory()) {
          throw new Error(`Not a directory: ${dirPath}`);
        }
        const zipResult = await zipDirectory(dirPath);
        filePath = zipResult.zipPath;
        cleanup = zipResult.cleanup;
      } else {
        filePath = resolve(file);
        if (!existsSync(filePath)) {
          throw new Error(`File not found: ${filePath}`);
        }
        const fileInfo = await getFileInfo(filePath);
        if (fileInfo.type !== "application/zip" && fileInfo.type !== "text/html") {
          throw new Error(`Unsupported file type: ${fileInfo.type}. Only ZIP and HTML files are supported.`);
        }
      }
      const uploadResult = await uploadFile(filePath, hub, accessToken, { did: existingDid });
      did = uploadResult.did;
      needsConversion = uploadResult.status === "PENDING";
      versionHistoryEnabled = uploadResult.versionHistoryEnabled;
    }

    const actionResult = await apiPatch(actionUrl, actionData, accessToken, hub);
    if (actionResult.success) {

    let actionResult;
    try {
      actionResult = await apiPatch(actionUrl, actionData, accessToken, hub);
    } catch (actionError) {
      console.error(chalk.red(`\n❌ Publish action failed: ${actionError.message}`));
      console.error(chalk.yellow(`\n📌 Upload was successful. DID: ${did}`));
      console.error(chalk.yellow(`To retry the publish action without re-uploading:`));
      console.error(chalk.cyan(`  node ${process.argv[1]} --skip-upload --did ${did} --title "..." --desc "..." --visibility ${visibility}\n`));
      return {
        success: false,
        error: actionError.message,
        did,
        retryHint: "skip-upload",
      };
    }
    if (actionResult.success) {

  --skip-upload            Skip file upload, retry publish action only (requires --did)

git add skills/myvibe-publish/scripts/publish.mjs
git commit -m "feat(publish): add --skip-upload flag to prevent duplicate records on retry
 
When publish action fails after a successful upload, the script now
outputs the DID and a retry command using --skip-upload. This prevents
creating duplicate upload records when retrying with adjusted parameters."

### Retry after action failure
 
If the publish script output contains `retryHint: skip-upload` or shows "Upload was successful. DID: ...", do NOT re-run the full publish command. Instead, use `--skip-upload` with the DID from the output:
 

 
This reuses the already-uploaded content and only retries the publish action, avoiding duplicate records.

| Publish action failed (upload succeeded) | Use `--skip-upload` with DID from error output to retry action only |

git add skills/myvibe-publish/SKILL.md
git commit -m "docs(publish): add retry guidance for failed publish actions in SKILL.md
 
Instructs the AI to use --skip-upload with the existing DID when
retrying a failed publish action, preventing duplicate upload records."

node skills/myvibe-publish/scripts/publish.mjs --help

node skills/myvibe-publish/scripts/publish.mjs --skip-upload