From dee65726e094e55ab780c065d721119c5760ef2d Mon Sep 17 00:00:00 2001
From: Miao Yang <miao.yang@heygen.com>
Date: Wed, 1 Jul 2026 23:02:42 +0800
Subject: [PATCH 1/2] ci: sync changed skills to ClawHub on push to main

Add a GitHub Actions workflow that runs `clawhub sync` whenever skills/**
changes on main, publishing only changed skills to ClawHub
(https://clawhub.ai/heygen-com) under the heygen-com publisher and
auto-bumping the patch version. Unchanged skills are a no-op, so it is
safe to run on every push. Requires the CLAWHUB_TOKEN repo secret.
---
 .github/workflows/sync-skills-to-clawhub.yml | 66 ++++++++++++++++++++
 1 file changed, 66 insertions(+)
 create mode 100644 .github/workflows/sync-skills-to-clawhub.yml

diff --git a/.github/workflows/sync-skills-to-clawhub.yml b/.github/workflows/sync-skills-to-clawhub.yml
new file mode 100644
index 000000000..b292740c8
--- /dev/null
+++ b/.github/workflows/sync-skills-to-clawhub.yml
@@ -0,0 +1,66 @@
+name: Sync skills to ClawHub
+
+# Publishes changed skills under skills/ to ClawHub (https://clawhub.ai/heygen-com)
+# whenever they land on main. `clawhub sync` only publishes skills whose content
+# changed vs. the registry, auto-bumping the patch version — unchanged skills are
+# a no-op, so this is safe to run on every push.
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - "skills/**"
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: "Preview what would publish without publishing"
+        type: boolean
+        default: false
+
+# Serialize runs so two pushes don't race on the same skill version.
+concurrency:
+  group: clawhub-sync
+  cancel-in-progress: false
+
+permissions:
+  contents: read
+
+jobs:
+  sync:
+    name: Publish changed skills
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    env:
+      CLAWHUB_DISABLE_TELEMETRY: "1"
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+
+      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
+        with:
+          node-version: 24
+
+      - name: Install ClawHub CLI
+        run: npm i -g clawhub@0.23.1
+
+      - name: Authenticate
+        env:
+          CLAWHUB_TOKEN: ${{ secrets.CLAWHUB_TOKEN }}
+        run: clawhub login --token "$CLAWHUB_TOKEN" --no-input --label "hyperframes CI"
+
+      - name: Sync skills
+        env:
+          DRY_RUN: ${{ github.event.inputs.dry_run }}
+        run: |
+          FLAGS=(
+            --all
+            --owner heygen-com
+            --bump patch
+            --changelog "Synced from ${GITHUB_SHA:0:7} (${GITHUB_REF_NAME})"
+            --source-repo "$GITHUB_REPOSITORY"
+            --source-commit "$GITHUB_SHA"
+            --source-ref "$GITHUB_REF"
+          )
+          if [ "$DRY_RUN" = "true" ]; then
+            FLAGS+=(--dry-run)
+          fi
+          clawhub sync "${FLAGS[@]}"

From 7ddb8a33157dc444593b5e14cfb939680d49def9 Mon Sep 17 00:00:00 2001
From: Miao Yang <miao.yang@heygen.com>
Date: Thu, 2 Jul 2026 01:17:45 +0800
Subject: [PATCH 2/2] ci: use Node 22 to match the CI fleet's LTS

Address review on #1835 (Miga): the rest of the CI fleet (ci.yml,
windows-render, player-perf, preview-regression, docs, catalog-previews)
pins setup-node to Node 22 LTS. Node 24 is current, not LTS, and could
introduce subtle differences. Align this workflow to 22.
---
 .github/workflows/sync-skills-to-clawhub.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/sync-skills-to-clawhub.yml b/.github/workflows/sync-skills-to-clawhub.yml
index b292740c8..33bb87cae 100644
--- a/.github/workflows/sync-skills-to-clawhub.yml
+++ b/.github/workflows/sync-skills-to-clawhub.yml
@@ -37,7 +37,7 @@ jobs:
 
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
         with:
-          node-version: 24
+          node-version: 22
 
       - name: Install ClawHub CLI
         run: npm i -g clawhub@0.23.1