[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7921YFP6AX2ZP6BJ7KX6K2D":3,"skill-same:01M7921YFP6AX2ZP6BJ7KX6K2D":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7921YFP6AX2ZP6BJ7KX6K2D","vercel-env-sync",null,"Reconcile Vercel project environment variables against the local `.env.local` and your app's env schema. Use when the user wants to verify, diff, add, or remove env vars on Vercel so a deploy will boot — or when diagnosing 401 \u002F `[DISPATCH_FAILED]` symptoms that smell like missing secrets. Read-only by default; mutations require explicit user sign-off.","dotlas\u002Fskills","dotlas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F88832003?v=4","01M791ZCS9BAQ40PZ8ADG8TCR1","Dotlas","01M791ZCT18PGXY969S8EZ1MVV",2,"MIT","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcoding\u002Fvercel-env-sync\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-env-sync\ndescription: Reconcile Vercel project environment variables against the local `.env.local` and your app's env schema. Use when the user wants to verify, diff, add, or remove env vars on Vercel so a deploy will boot — or when diagnosing 401 \u002F `[DISPATCH_FAILED]` symptoms that smell like missing secrets. Read-only by default; mutations require explicit user sign-off.\n---\n# Vercel Env Sync\n\n## Safety\n\nNon-negotiable:\n\n1. **NEVER run `vercel deploy`, `vercel rollback`, `vercel alias`,\n   `vercel domains \u003Cmut>`, `vercel project rm`, or any deploy \u002F domain \u002F project\n   mutation.** Production deploys belong to the GitHub integration on `main`. If the\n   user asks for a deploy, refuse and redirect to `git push`.\n2. **NEVER run `vercel link` or `vercel env pull` without first checking\n   `git diff .env.local`.** Both commands overwrite that file.\n   If it’s dirty, back it up (`cp .env.local .env.local.bak`) and tell the user before\n   proceeding.\n3. **NEVER run `vercel env rm` without explicit per-variable, per-environment user\n   sign-off.** Removal is destructive (no undo, no version history).\n   Present the list, wait for the user to name each var in their approval, then execute\n   one at a time.\n4. **NEVER print secret values to the transcript.** Echo `${#VAR}` (length) or\n   first\u002Flast 4 chars only.\n   Treat anything in `.env.local` as production-grade credentials.\n5. **NEVER set Vercel-injected vars** (`VERCEL_URL`, `VERCEL_PROJECT_PRODUCTION_URL`,\n   `VERCEL_ENV`, `VERCEL_GIT_COMMIT_SHA`, `VERCEL_REGION`, …). If you find one set as a\n   project env var, flag it — the dashboard value overrides Vercel’s runtime injection\n   and will silently break URL resolution.\n6. **NEVER add a `NEXT_PUBLIC_*` mirror of a server-only secret** (`CRON_SECRET`,\n   `VERCEL_AUTOMATION_BYPASS_SECRET`, database URLs, API keys).\n   These leak to the browser bundle.\n7. **Vercel CLI is not signed-in by default in CI.** If `vercel whoami` fails, stop and\n   tell the user — do not try to log in non-interactively.\n\n## Discovery\n\nReplace `\u003Cyour-scope>` and `\u003Cyour-vercel-project>` with the values in\n`\u003Capp>\u002F.vercel\u002Fproject.json`. If your project keeps a Vercel conventions doc, read it\nbefore doing anything non-trivial.\n**All `vercel` commands must be detached from stdin (`\u003C \u002Fdev\u002Fnull`) or they hang in\nagent shells.**\n\n```bash\n# Auth + scope\npnpm exec vercel whoami \u003C \u002Fdev\u002Fnull\npnpm exec vercel teams ls \u003C \u002Fdev\u002Fnull 2>&1 | cat\n\n# Confirm the link is correct\ncat \u003Capp>\u002F.vercel\u002Fproject.json 2>\u002Fdev\u002Fnull \\\n  || echo \"NOT LINKED — run: cd \u003Capp> && pnpm exec vercel link --yes --scope \u003Cyour-scope> --project \u003Cyour-vercel-project>\"\n\n# Project facts\ncd \u003Capp> && pnpm exec vercel project inspect \u003Cyour-vercel-project> --scope \u003Cyour-scope> \u003C \u002Fdev\u002Fnull 2>&1 | cat\n```\n\nExpected: scope `\u003Cyour-scope>`, project `\u003Cyour-vercel-project>`, root directory `\u003Capp>`.\nIf anything else, **stop** — you are pointed at the wrong project and any mutation will\nhit production for a different app.\n\n## Diff\n\nThis is the default mode.\nProduce a three-way diff of:\n\n- **Local** — names declared in repo-root `.env.local`.\n- **Schema** — names declared in `\u003Capp>\u002Fenv.ts` (server + client) and any\n  `\u003Cpackages>\u002F*\u002Fkeys.ts`.\n- **Vercel** — names present in `production`, `preview`, `development` per the CLI.\n\n### Pull the three lists\n\n```bash\n# Local names\ngrep -E '^[A-Z_][A-Z0-9_]*=' \u003Crepo-root>\u002F.env.local \\\n  | sed 's\u002F=.*\u002F\u002F' | sort -u > \u002Ftmp\u002Flocal-keys.txt\n\n# Vercel names per environment\ncd \u003Capp>\nfor ENV in production preview development; do\n  pnpm exec vercel env ls \"$ENV\" \u003C \u002Fdev\u002Fnull 2>&1 \\\n    | awk 'NR>3 && $1 ~ \u002F^[A-Z_][A-Z0-9_]*$\u002F {print $1}' | sort -u > \"\u002Ftmp\u002Fvercel-$ENV-keys.txt\"\ndone\n\n# Schema names\n{\n  grep -oE '^\\s*[A-Z_][A-Z0-9_]*:' \u003Capp>\u002Fenv.ts | sed 's\u002F[: ]\u002F\u002Fg'\n  find \u003Cpackages> -name keys.ts -exec grep -hoE '^\\s*[A-Z_][A-Z0-9_]*:' {} \\; | sed 's\u002F[: ]\u002F\u002Fg'\n} | sort -u > \u002Ftmp\u002Fschema-keys.txt\n```\n\n### Compute the delta sets\n\n```bash\n# (A) In local but missing on Vercel production — likely deploy-breakers\ncomm -23 \u002Ftmp\u002Flocal-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n\n# (B) On Vercel but not in local — possibly orphaned, or production-only secrets\ncomm -13 \u002Ftmp\u002Flocal-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n\n# (C) In schema but missing on Vercel production — runtime will throw on boot\ncomm -23 \u002Ftmp\u002Fschema-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n\n# (D) On Vercel production but not in schema — dead weight or undeclared\ncomm -13 \u002Ftmp\u002Fschema-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n```\n\nRepeat (A)\u002F(C) against `preview` and `development` separately — the three environments\ndiverge intentionally.\n\n### Classify each delta\n\nFor every name in the diff:\n\n| Question | Where to look | Implication |\n| --- | --- | --- |\n| Declared in `\u003Capp>\u002Fenv.ts`? | grep `env.ts` for the name | Required-everywhere if no `.optional()`; build fails without it |\n| Declared in any `\u003Cpackages>\u002F*\u002Fkeys.ts`? | grep `\u003Cpackages>\u002F*\u002Fkeys.ts` | Required for the package consumer |\n| Mentioned in latest changeset? | `ls -lt .changeset\u002F*.md \\| head -5` then grep | Authoritative environment targeting (prod-only vs all envs) |\n| Vercel-injected? | Match against `VERCEL_*` in Safety rule 5 | **DO NOT** set; flag as foot-gun |\n| `NEXT_PUBLIC_*`? | Prefix check | Safe to expose; inlined into client bundle at build time |\n| Sensitive? | `vercel env ls` “Type” column | `pull` returns empty string; can only re-add to edit |\n\nA var in `.env.local` but not declared anywhere in the repo is dead weight — recommend\nremoving from `.env.local`, not adding to Vercel.\n\n## Plan\n\nOutput as a table grouped by action.\nAdd operations for vars declared in schema with values sourced from `.env.local` can\nproceed after overall plan approval; `rm` always requires per-variable sign-off.\n\n```\nADD to production:\n  CRON_SECRET            (declared: env.ts server, sensitive: yes, source: .env.local len=64)\n\nADD to preview:\n  CRON_SECRET            (same value as prod)\n\nREMOVE from production (DESTRUCTIVE — needs sign-off):\n  OLD_FEATURE_FLAG       (not declared in schema, last referenced in commit abc1234)\n\nFLAG (do not change without discussion):\n  VERCEL_PROJECT_PRODUCTION_URL = http:\u002F\u002Flocalhost:3000   ← overrides Vercel injection; almost certainly wrong\n```\n\nWait for the user to approve the plan before running any `add`, and per-variable before\nany `rm`.\n\n## Execute\n\n```bash\ncd \u003Crepo-root> && \\\nset -a && source .env.local && set +a && \\\ncd \u003Capp> && \\\nadd() {\n  local name=\"$1\" envname=\"$2\" val=\"$3\"\n  echo \"→ $name [$envname] (len=${#val})\"   # length only — never the value\n  if [[ \"$envname\" == \"preview\" ]]; then\n    # preview always prompts for git branch — pass \"\" to mean \"all preview branches\"\n    pnpm exec vercel env add \"$name\" preview \"\" --value \"$val\" --yes \u003C \u002Fdev\u002Fnull 2>&1 | tail -2\n  else\n    # use --value to avoid stdin consumption conflicts with the branch prompt\n    pnpm exec vercel env add \"$name\" \"$envname\" --value \"$val\" --yes \u003C \u002Fdev\u002Fnull 2>&1 | tail -2\n  fi\n} && \\\nadd CRON_SECRET production \"$CRON_SECRET\" && \\\nadd CRON_SECRET preview    \"$CRON_SECRET\" && \\\necho DONE\n```\n\n`tail -2` keeps each add’s output to `Saving` + the success line.\n\n### Editing an existing var\n\nThere is no in-place edit.\nSequence:\n\n```bash\npnpm exec vercel env rm NAME production --yes \u003C \u002Fdev\u002Fnull   # DESTRUCTIVE — needs sign-off\npnpm exec vercel env add NAME production --value \"$VAL\" --yes \u003C \u002Fdev\u002Fnull\n```\n\nIf the var was sensitive, you cannot `pull` the old value first — confirm the new value\nbefore removing.\n\n### Sensitive-flag note\n\nThe CLI defaults to **Plain**. To mark a value sensitive (encrypted at rest, unreadable\nvia `pull`), set it in the dashboard — this skill does not cover the sensitive flag\nbecause the CLI doesn’t expose it cleanly.\nNote which vars *should* be sensitive (`*_SECRET`, `*_KEY`, `*_TOKEN`, database URLs,\nAPI keys) and ask the user to flip them in the dashboard.\n\n## Verify\n\n```bash\ncd \u003Capp>\nfor ENV in production preview development; do\n  echo \"=== $ENV ===\"\n  pnpm exec vercel env ls \"$ENV\" \u003C \u002Fdev\u002Fnull 2>&1 | grep -E \"\u003Cadded-var-names>\"\ndone\n```\n\nThen tell the user: **“Env-var changes only take effect on the next deploy.\nTrigger a redeploy by pushing a commit to `main` (production) or your PR branch\n(preview).”**\n\n## Diagnostic shortcuts\n\n| Symptom | First env-var to check |\n| --- | --- |\n| `[DISPATCH_FAILED] HTTP 401 — \u003C!doctype html>...` (HTML, not JSON) | `VERCEL_AUTOMATION_BYPASS_SECRET` missing on production |\n| `[DISPATCH_FAILED] HTTP 401 — {\"error\":\"Unauthorized\"}` (JSON) | `CRON_SECRET` missing or mismatched |\n| `[DISPATCH_FAILED] fetch failed [ECONNREFUSED] ... 127.0.0.1:3000` | `NEXT_PUBLIC_APP_URL` missing AND `VERCEL_PROJECT_PRODUCTION_URL` overridden to localhost |\n| `[DISPATCH_FAILED] fetch failed [ENOTFOUND]` | `NEXT_PUBLIC_APP_URL` points at a dead domain or wrong subdomain |\n| Cron route returns 401 HTML | Same as row 1 — Deployment Protection without bypass secret |\n| Cron route returns 404 + `x-middleware-rewrite` header | Not an env issue — route prefix missing from the public-route allowlist in your auth middleware |\n| App boots then crashes on first request with Zod validation error | Var declared required (no `.optional()`) in `env.ts` is missing from production |\n\nFor each, rule out non-env causes before recommending a fix — several of these symptoms\nhave non-env causes that look identical.\n","# Vercel Env Sync\n\n## Safety\n\nNon-negotiable:\n\n1. **NEVER run `vercel deploy`, `vercel rollback`, `vercel alias`,\n   `vercel domains \u003Cmut>`, `vercel project rm`, or any deploy \u002F domain \u002F project\n   mutation.** Production deploys belong to the GitHub integration on `main`. If the\n   user asks for a deploy, refuse and redirect to `git push`.\n2. **NEVER run `vercel link` or `vercel env pull` without first checking\n   `git diff .env.local`.** Both commands overwrite that file.\n   If it’s dirty, back it up (`cp .env.local .env.local.bak`) and tell the user before\n   proceeding.\n3. **NEVER run `vercel env rm` without explicit per-variable, per-environment user\n   sign-off.** Removal is destructive (no undo, no version history).\n   Present the list, wait for the user to name each var in their approval, then execute\n   one at a time.\n4. **NEVER print secret values to the transcript.** Echo `${#VAR}` (length) or\n   first\u002Flast 4 chars only.\n   Treat anything in `.env.local` as production-grade credentials.\n5. **NEVER set Vercel-injected vars** (`VERCEL_URL`, `VERCEL_PROJECT_PRODUCTION_URL`,\n   `VERCEL_ENV`, `VERCEL_GIT_COMMIT_SHA`, `VERCEL_REGION`, …). If you find one set as a\n   project env var, flag it — the dashboard value overrides Vercel’s runtime injection\n   and will silently break URL resolution.\n6. **NEVER add a `NEXT_PUBLIC_*` mirror of a server-only secret** (`CRON_SECRET`,\n   `VERCEL_AUTOMATION_BYPASS_SECRET`, database URLs, API keys).\n   These leak to the browser bundle.\n7. **Vercel CLI is not signed-in by default in CI.** If `vercel whoami` fails, stop and\n   tell the user — do not try to log in non-interactively.\n\n## Discovery\n\nReplace `\u003Cyour-scope>` and `\u003Cyour-vercel-project>` with the values in\n`\u003Capp>\u002F.vercel\u002Fproject.json`. If your project keeps a Vercel conventions doc, read it\nbefore doing anything non-trivial.\n**All `vercel` commands must be detached from stdin (`\u003C \u002Fdev\u002Fnull`) or they hang in\nagent shells.**\n\n```bash\n# Auth + scope\npnpm exec vercel whoami \u003C \u002Fdev\u002Fnull\npnpm exec vercel teams ls \u003C \u002Fdev\u002Fnull 2>&1 | cat\n\n# Confirm the link is correct\ncat \u003Capp>\u002F.vercel\u002Fproject.json 2>\u002Fdev\u002Fnull \\\n  || echo \"NOT LINKED — run: cd \u003Capp> && pnpm exec vercel link --yes --scope \u003Cyour-scope> --project \u003Cyour-vercel-project>\"\n\n# Project facts\ncd \u003Capp> && pnpm exec vercel project inspect \u003Cyour-vercel-project> --scope \u003Cyour-scope> \u003C \u002Fdev\u002Fnull 2>&1 | cat\n```\n\nExpected: scope `\u003Cyour-scope>`, project `\u003Cyour-vercel-project>`, root directory `\u003Capp>`.\nIf anything else, **stop** — you are pointed at the wrong project and any mutation will\nhit production for a different app.\n\n## Diff\n\nThis is the default mode.\nProduce a three-way diff of:\n\n- **Local** — names declared in repo-root `.env.local`.\n- **Schema** — names declared in `\u003Capp>\u002Fenv.ts` (server + client) and any\n  `\u003Cpackages>\u002F*\u002Fkeys.ts`.\n- **Vercel** — names present in `production`, `preview`, `development` per the CLI.\n\n### Pull the three lists\n\n```bash\n# Local names\ngrep -E '^[A-Z_][A-Z0-9_]*=' \u003Crepo-root>\u002F.env.local \\\n  | sed 's\u002F=.*\u002F\u002F' | sort -u > \u002Ftmp\u002Flocal-keys.txt\n\n# Vercel names per environment\ncd \u003Capp>\nfor ENV in production preview development; do\n  pnpm exec vercel env ls \"$ENV\" \u003C \u002Fdev\u002Fnull 2>&1 \\\n    | awk 'NR>3 && $1 ~ \u002F^[A-Z_][A-Z0-9_]*$\u002F {print $1}' | sort -u > \"\u002Ftmp\u002Fvercel-$ENV-keys.txt\"\ndone\n\n# Schema names\n{\n  grep -oE '^\\s*[A-Z_][A-Z0-9_]*:' \u003Capp>\u002Fenv.ts | sed 's\u002F[: ]\u002F\u002Fg'\n  find \u003Cpackages> -name keys.ts -exec grep -hoE '^\\s*[A-Z_][A-Z0-9_]*:' {} \\; | sed 's\u002F[: ]\u002F\u002Fg'\n} | sort -u > \u002Ftmp\u002Fschema-keys.txt\n```\n\n### Compute the delta sets\n\n```bash\n# (A) In local but missing on Vercel production — likely deploy-breakers\ncomm -23 \u002Ftmp\u002Flocal-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n\n# (B) On Vercel but not in local — possibly orphaned, or production-only secrets\ncomm -13 \u002Ftmp\u002Flocal-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n\n# (C) In schema but missing on Vercel production — runtime will throw on boot\ncomm -23 \u002Ftmp\u002Fschema-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n\n# (D) On Vercel production but not in schema — dead weight or undeclared\ncomm -13 \u002Ftmp\u002Fschema-keys.txt \u002Ftmp\u002Fvercel-production-keys.txt\n```\n\nRepeat (A)\u002F(C) against `preview` and `development` separately — the three environments\ndiverge intentionally.\n\n### Classify each delta\n\nFor every name in the diff:\n\n| Question | Where to look | Implication |\n| --- | --- | --- |\n| Declared in `\u003Capp>\u002Fenv.ts`? | grep `env.ts` for the name | Required-everywhere if no `.optional()`; build fails without it |\n| Declared in any `\u003Cpackages>\u002F*\u002Fkeys.ts`? | grep `\u003Cpackages>\u002F*\u002Fkeys.ts` | Required for the package consumer |\n| Mentioned in latest changeset? | `ls -lt .changeset\u002F*.md \\| head -5` then grep | Authoritative environment targeting (prod-only vs all envs) |\n| Vercel-injected? | Match against `VERCEL_*` in Safety rule 5 | **DO NOT** set; flag as foot-gun |\n| `NEXT_PUBLIC_*`? | Prefix check | Safe to expose; inlined into client bundle at build time |\n| Sensitive? | `vercel env ls` “Type” column | `pull` returns empty string; can only re-add to edit |\n\nA var in `.env.local` but not declared anywhere in the repo is dead weight — recommend\nremoving from `.env.local`, not adding to Vercel.\n\n## Plan\n\nOutput as a table grouped by action.\nAdd operations for vars declared in schema with values sourced from `.env.local` can\nproceed after overall plan approval; `rm` always requires per-variable sign-off.\n\n```\nADD to production:\n  CRON_SECRET            (declared: env.ts server, sensitive: yes, source: .env.local len=64)\n\nADD to preview:\n  CRON_SECRET            (same value as prod)\n\nREMOVE from production (DESTRUCTIVE — needs sign-off):\n  OLD_FEATURE_FLAG       (not declared in schema, last referenced in commit abc1234)\n\nFLAG (do not change without discussion):\n  VERCEL_PROJECT_PRODUCTION_URL = http:\u002F\u002Flocalhost:3000   ← overrides Vercel injection; almost certainly wrong\n```\n\nWait for the user to approve the plan before running any `add`, and per-variable before\nany `rm`.\n\n## Execute\n\n```bash\ncd \u003Crepo-root> && \\\nset -a && source .env.local && set +a && \\\ncd \u003Capp> && \\\nadd() {\n  local name=\"$1\" envname=\"$2\" val=\"$3\"\n  echo \"→ $name [$envname] (len=${#val})\"   # length only — never the value\n  if [[ \"$envname\" == \"preview\" ]]; then\n    # preview always prompts for git branch — pass \"\" to mean \"all preview branches\"\n    pnpm exec vercel env add \"$name\" preview \"\" --value \"$val\" --yes \u003C \u002Fdev\u002Fnull 2>&1 | tail -2\n  else\n    # use --value to avoid stdin consumption conflicts with the branch prompt\n    pnpm exec vercel env add \"$name\" \"$envname\" --value \"$val\" --yes \u003C \u002Fdev\u002Fnull 2>&1 | tail -2\n  fi\n} && \\\nadd CRON_SECRET production \"$CRON_SECRET\" && \\\nadd CRON_SECRET preview    \"$CRON_SECRET\" && \\\necho DONE\n```\n\n`tail -2` keeps each add’s output to `Saving` + the success line.\n\n### Editing an existing var\n\nThere is no in-place edit.\nSequence:\n\n```bash\npnpm exec vercel env rm NAME production --yes \u003C \u002Fdev\u002Fnull   # DESTRUCTIVE — needs sign-off\npnpm exec vercel env add NAME production --value \"$VAL\" --yes \u003C \u002Fdev\u002Fnull\n```\n\nIf the var was sensitive, you cannot `pull` the old value first — confirm the new value\nbefore removing.\n\n### Sensitive-flag note\n\nThe CLI defaults to **Plain**. To mark a value sensitive (encrypted at rest, unreadable\nvia `pull`), set it in the dashboard — this skill does not cover the sensitive flag\nbecause the CLI doesn’t expose it cleanly.\nNote which vars *should* be sensitive (`*_SECRET`, `*_KEY`, `*_TOKEN`, database URLs,\nAPI keys) and ask the user to flip them in the dashboard.\n\n## Verify\n\n```bash\ncd \u003Capp>\nfor ENV in production preview development; do\n  echo \"=== $ENV ===\"\n  pnpm exec vercel env ls \"$ENV\" \u003C \u002Fdev\u002Fnull 2>&1 | grep -E \"\u003Cadded-var-names>\"\ndone\n```\n\nThen tell the user: **“Env-var changes only take effect on the next deploy.\nTrigger a redeploy by pushing a commit to `main` (production) or your PR branch\n(preview).”**\n\n## Diagnostic shortcuts\n\n| Symptom | First env-var to check |\n| --- | --- |\n| `[DISPATCH_FAILED] HTTP 401 — \u003C!doctype html>...` (HTML, not JSON) | `VERCEL_AUTOMATION_BYPASS_SECRET` missing on production |\n| `[DISPATCH_FAILED] HTTP 401 — {\"error\":\"Unauthorized\"}` (JSON) | `CRON_SECRET` missing or mismatched |\n| `[DISPATCH_FAILED] fetch failed [ECONNREFUSED] ... 127.0.0.1:3000` | `NEXT_PUBLIC_APP_URL` missing AND `VERCEL_PROJECT_PRODUCTION_URL` overridden to localhost |\n| `[DISPATCH_FAILED] fetch failed [ENOTFOUND]` | `NEXT_PUBLIC_APP_URL` points at a dead domain or wrong subdomain |\n| Cron route returns 401 HTML | Same as row 1 — Deployment Protection without bypass secret |\n| Cron route returns 404 + `x-middleware-rewrite` header | Not an env issue — route prefix missing from the public-route allowlist in your auth middleware |\n| App boots then crashes on first request with Zod validation error | Var declared required (no `.optional()`) in `env.ts` is missing from production |\n\nFor each, rule out non-env causes before recommending a fix — several of these symptoms\nhave non-env causes that look identical.\n",{"name":5,"description":7},"main","44a7c5d185b1020f689d2129547d7470c3715e76","skills\u002Fcustom\u002Fcoding\u002Fvercel-env-sync",0,"https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills","https:\u002F\u002Fwww.skills.sh\u002Fdotlas\u002Fskills","https:\u002F\u002Fgithub.com\u002Fdotlas","www.dotlas.com","A platform to help companies make better city-level decisions and improve the bottom line of their retail footprint.","2026-10-27 22:40:58",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add dotlas\u002Fskills --skill vercel-env-sync",{"tool":40,"command":41},"bunx","bunx skills add dotlas\u002Fskills --skill vercel-env-sync",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dotlas\u002Fskills --skill vercel-env-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcoding\u002Fvercel-env-sync\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M792400972AXPY3XESVHRFRA","where-were-we","Provide the user with a refresher of existing chat turns. Useful when the user wants to understand where we stand in the conversation.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fwhere-were-we\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7923T58GM9G9TVAZB9TGTWE","update-global-dotlas-skills","Sync the globally-installed dotlas\u002Fskills catalog and prune stale remnants. Runs the documented global install command, then detects skills that were installed from dotlas\u002Fskills but no longer exist in the catalog and removes them (with confirmation). Use when the user wants to update, refresh, or clean up their global Dotlas skills, or invokes \u002Fupdate-global-dotlas-skills.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fupdate-global-dotlas-skills\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7923KGCMXT25Y7XVC6G1ERX","unpack","Explain an unfamiliar thing plainly and from first principles, structured so the reader sees why it is true. Use when someone is trying to understand something — a dense or jargon-heavy passage, a baffling error, an unfamiliar mechanism, a codebase, or a document — asks to break something down (\"walk me through this\", \"what does this actually mean\"), or wants their intent turned into a precise instruction for another agent. Trigger on confusion or a request to understand, not on difficulty alone; technical or long content is not itself a signal.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Funpack\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7923HNVVHRKRVQ5M0P7TXZA","sum","Use when the previous response is too technical, complex, or jargon-heavy and needs a clear, plain-language explanation","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fsum\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7923CY3FR71VPKBYRHZNNVH","slack","Compose a Slack message, or digest a Slack thread into compact context. Use when the user asks to reply to a person or channel, write a Slack post, or catch up on a thread without reading the whole transcript. This skill covers how to write well for Slack — both jobs share the same standard.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fslack\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79234W72RKWYV2S38G2B0SY","plan-with-me","Collaborative, human-in-the-loop planning for something new that spans several parts and needs human judgement at each fork. A brainstorming partner that funnels — each fork opens up the real options, then narrows to a decision, surfacing caveats and breaking points, and co-authoring the plan instead of guessing alone. Fits any domain where you plan something new against existing context. Resolves one decision at a time, each with a recommendation, then emits a lightweight plan to hand off for implementation. Use when planning alone would make wrong assumptions, or the user wants to shape something new together.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fplan-with-me\u002FSKILL.md",[],[]]