菜单
Manually POST Vercel cron endpoints (e.g. extract-pending) using VERCEL_CRON_SECRET from ~/.env. Use when Vercel scheduled cron is unavailable, after imports stuck in extracting, verifying Production/Preview before merge, or debugging async extraction — do not expose secrets in logs or chat.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the user asks to release the iOS app, upload a build, submit to App Store Connect review, or "在 App Store 上架/提交审核" for WordMagicGame.
Seed a lesson-import draft on a deployed Happyword API (Preview or prod) and optionally run the extract-pending cron so it reaches `pending` (待复核). Uses tools starting with `hw_`. Invoke when the user wants to upload a textbook photo for review against a specific Vercel URL, mirror E2E `test_lesson_import_cron_e2e`, or smoke-test lesson import + cron on a branch deployment.
Investigate why a Vercel preview / production deployment of the FastAPI server is broken (404 on every path, 500 on every path, e2e CI red, etc.). Pulls the right log surface for the symptom and maps HTTP error headers to root causes. Use whenever the deployed server returns wrong responses, the server-ci e2e job fails, or autofix loops keep retrying without converging.
Health-check every active Vercel Preview deployment listed in the live manifest at `https://happyword.cool/api/v1/public/preview-urls.json`. Probes `GET /api/v1/public/health` through Vercel Deployment Protection (`x-vercel-protection-bypass` header), prints a one-line status per preview, and exits non-zero if any are sick. Use when the user asks to "test preview health", "check previews", "are PR previews alive?", before merging anything that touches `server/`, after a fleet-wide redeploy or env-var rotation, or after rotating `VERCEL_AUTOMATION_BYPASS_SECRET` — do NOT loop ad-hoc `curl` calls or use `tools/vercel/smoke-prod.sh` (production-only) for this.
Drives a per-feature visual + spec-anchored gap scout across HarmonyOS / iOS / Android using tools/parity_scout/. Use when asked to "find iOS / Android gaps vs HarmonyOS main", "check parity for <feature>", or "screenshot the three platforms and tell me what's different".
Drives a per-feature visual + spec-anchored gap scout across HarmonyOS / iOS / Android using tools/parity_scout/. Use when asked to "find iOS / Android gaps vs HarmonyOS main", "check parity for <feature>", or "screenshot the three platforms and tell me what's different".
| name | vercel-trigger-cron |
| description | Manually POST Vercel cron endpoints (e.g. extract-pending) using VERCEL_CRON_SECRET from ~/.env. Use when Vercel scheduled cron is unavailable, after imports stuck in extracting, verifying Production/Preview before merge, or debugging async extraction — do not expose secrets in logs or chat. |
From repository root:
bash tools/vercel/trigger-cron.sh
~/.env)Store VERCEL_CRON_SECRET next to VERCEL_* keys in ~/.env (never commit). The value must equal Vercel → Project → Settings → Environment Variables → CRON_SECRET on the deployment you hit (Production or Preview). (Server uses CRON_SECRET; your workstation uses VERCEL_CRON_SECRET.)
Never paste the secret into chats, transcript commands, or echo. The script resolves VERCEL_CRON_SECRET inside a subshell from ~/.env without printing it (same pattern as tools/vercel/preview-health.sh for bypass secrets).
Alternatively export VERCEL_CRON_SECRET in your shell first — still avoid logging it (set -x off).
If the target is a protected Preview (Vercel Deployment Protection / SSO), also set VERCEL_AUTOMATION_BYPASS_SECRET in ~/.env. The script will attach x-vercel-protection-bypass: ... automatically (without printing it).
Default target is https://happyword.cool (Production latest).
# Full preview URL
bash tools/vercel/trigger-cron.sh --url https://happyword-xxxx-terrymas-projects.vercel.app
# Or only the middle fragment (happyword-<frag>-terrymas-projects.vercel.app)
bash tools/vercel/trigger-cron.sh --url-fragment 9y7uijs1p
To target a specific deployment uid (dpl_...), use --deployment-id (requires VERCEL_TOKEN in ~/.env so the script can resolve the URL via the Vercel API).
Ensure Preview env on Vercel also defines CRON_SECRET matching your local VERCEL_CRON_SECRET, or the route returns 401 / CRON_SECRET_NOT_CONFIGURED.
By default the script triggers every cron declared in server/vercel.json (crons[].path). To trigger a single job by name (suffix after /api/v1/admin/cron/):
bash tools/vercel/trigger-cron.sh --job extract-pending
The handler returns JSON such as {"claimed":0|1,"succeeded":0|1,"failed":0|1}. Exit 0 only on HTTP 200; non-200 exits 1. Missing secret after resolution exits 2.
Optional --json-only: pretty-print body with jq (requires jq on PATH); still exits non-zero on non-200.
server/app/routers/admin_cron.py — POST /api/v1/admin/cron/extract-pendingdocs/ci-secrets.md — CRON_SECRETtools/vercel/trigger-cron.shserver/vercel.json