[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K0WJ1R2XP8RYPVQFSWASRQ":3,"skill-same:01M6K0WJ1R2XP8RYPVQFSWASRQ":84},{"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":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6K0WJ1R2XP8RYPVQFSWASRQ","deploy-to-vercel",null,"Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","NagyVikt\u002Fcodex-plugins","NagyVikt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F137165288?v=4","01M6K0SJ3R2DAZRJKJJS10VN87","Viktor Nagy","01M6K0SJ9HXN0GBD91QDQ9WNVV",2,"MIT","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuild-web-apps\u002Fskills\u002Fdeploy-to-vercel\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"vercel","deploy","deploy to vercel","preview deployment","my","requests","link","app","live","preview","me","use","user","applications","actions","push","create","deployment","2026-11-10 10:12:30",false,"---\nname: deploy-to-vercel\ndescription: Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".\nmetadata:\n  author: vercel\n  version: \"3.0.0\"\n---\n\n# Deploy to Vercel\n\nDeploy any project to Vercel. **Always deploy as preview** (not production) unless the user explicitly asks for production.\n\nThe goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state.\n\n## Step 1: Gather Project State\n\nRun all four checks before deciding which method to use:\n\n```bash\n# 1. Check for a git remote\ngit remote get-url origin 2>\u002Fdev\u002Fnull\n\n# 2. Check if locally linked to a Vercel project (either file means linked)\ncat .vercel\u002Fproject.json 2>\u002Fdev\u002Fnull || cat .vercel\u002Frepo.json 2>\u002Fdev\u002Fnull\n\n# 3. Check if the Vercel CLI is installed and authenticated\nvercel whoami 2>\u002Fdev\u002Fnull\n\n# 4. List available teams (if authenticated)\nvercel teams list --format json 2>\u002Fdev\u002Fnull\n```\n\n### Team selection\n\nIf the user belongs to multiple teams, present all available team slugs as a bulleted list and ask which one to deploy to. Once the user picks a team, proceed immediately to the next step — do not ask for additional confirmation.\n\nPass the team slug via `--scope` on all subsequent CLI commands (`vercel deploy`, `vercel link`, `vercel inspect`, etc.):\n\n```bash\nvercel deploy [path] -y --no-wait --scope \u003Cteam-slug>\n```\n\nIf the project is already linked (`.vercel\u002Fproject.json` or `.vercel\u002Frepo.json` exists), the `orgId` in those files determines the team — no need to ask again. If there is only one team (or just a personal account), skip the prompt and use it directly.\n\n**About the `.vercel\u002F` directory:** A linked project has either:\n- `.vercel\u002Fproject.json` — created by `vercel link` (single project linking). Contains `projectId` and `orgId`.\n- `.vercel\u002Frepo.json` — created by `vercel link --repo` (repo-based linking). Contains `orgId`, `remoteName`, and a `projects` array mapping directories to Vercel project IDs.\n\nEither file means the project is linked. Check for both.\n\n**Do NOT** use `vercel project inspect`, `vercel ls`, or `vercel link` to detect state in an unlinked directory — without a `.vercel\u002F` config, they will interactively prompt (or with `--yes`, silently link as a side-effect). Only `vercel whoami` is safe to run anywhere.\n\n## Step 2: Choose a Deploy Method\n\n### Linked (`.vercel\u002F` exists) + has git remote → Git Push\n\nThis is the ideal state. The project is linked and has git integration.\n\n1. **Ask the user before pushing.** Never push without explicit approval:\n   ```\n   This project is connected to Vercel via git. I can commit and push to\n   trigger a deployment. Want me to proceed?\n   ```\n\n2. **Commit and push:**\n   ```bash\n   git add .\n   git commit -m \"deploy: \u003Cdescription of changes>\"\n   git push\n   ```\n   Vercel automatically builds from the push. Non-production branches get preview deployments; the production branch (usually `main`) gets a production deployment.\n\n3. **Retrieve the preview URL.** If the CLI is authenticated:\n   ```bash\n   sleep 5\n   vercel ls --format json\n   ```\n   The JSON output has a `deployments` array. Find the latest entry — its `url` field is the preview URL.\n\n   If the CLI is not authenticated, tell the user to check the Vercel dashboard or the commit status checks on their git provider for the preview URL.\n\n---\n\n### Linked (`.vercel\u002F` exists) + no git remote → `vercel deploy`\n\nThe project is linked but there's no git repo. Deploy directly with the CLI.\n\n```bash\nvercel deploy [path] -y --no-wait\n```\n\nUse `--no-wait` so the CLI returns immediately with the deployment URL instead of blocking until the build finishes (builds can take a while). Then check on the deployment status with:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\nFor production deploys (only if user explicitly asks):\n```bash\nvercel deploy [path] --prod -y --no-wait\n```\n\n---\n\n### Not linked + CLI is authenticated → Link first, then deploy\n\nThe CLI is working but the project isn't linked yet. This is the opportunity to get the user into the best state.\n\n1. **Ask the user which team to deploy to.** Present the team slugs from Step 1 as a bulleted list. If there's only one team (or just a personal account), skip this step.\n\n2. **Once a team is selected, proceed directly to linking.** Tell the user what will happen but do not ask for separate confirmation:\n   ```\n   Linking this project to \u003Cteam name> on Vercel. This will create a Vercel\n   project to deploy to and enable automatic deployments on future git pushes.\n   ```\n\n3. **If a git remote exists**, use repo-based linking with the selected team scope:\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug>\n   ```\n   This reads the git remote URL and matches it to existing Vercel projects that deploy from that repo. It creates `.vercel\u002Frepo.json`. This is much more reliable than `vercel link` (without `--repo`), which tries to match by directory name and often fails when the local folder and Vercel project are named differently.\n\n   **If there is no git remote**, fall back to standard linking:\n   ```bash\n   vercel link --scope \u003Cteam-slug>\n   ```\n   This prompts the user to select or create a project. It creates `.vercel\u002Fproject.json`.\n\n4. **Then deploy using the best available method:**\n   - If a git remote exists → commit and push (see git push method above)\n   - If no git remote → `vercel deploy [path] -y --no-wait --scope \u003Cteam-slug>`, then `vercel inspect \u003Curl>` to check status\n\n---\n\n### Not linked + CLI not authenticated → Install, auth, link, deploy\n\nThe Vercel CLI isn't set up at all.\n\n1. **Install the CLI (if not already installed):**\n   ```bash\n   npm install -g vercel\n   ```\n\n2. **Authenticate:**\n   ```bash\n   vercel login\n   ```\n   The user completes auth in their browser. If running in a non-interactive environment where login is not possible, skip to the **no-auth fallback** below.\n\n3. **Ask which team to deploy to** — present team slugs from `vercel teams list --format json` as a bulleted list. If only one team \u002F personal account, skip. Once selected, proceed immediately.\n\n4. **Link the project** with the selected team scope (use `--repo` if a git remote exists, plain `vercel link` otherwise):\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug>   # if git remote exists\n   vercel link --scope \u003Cteam-slug>          # if no git remote\n   ```\n\n5. **Deploy** using the best available method (git push if remote exists, otherwise `vercel deploy -y --no-wait --scope \u003Cteam-slug>`, then `vercel inspect \u003Curl>` to check status).\n\n---\n\n### No-Auth Fallback — Codex sandbox\n\n**When to use:** In the Codex sandbox where the CLI may not be authenticated. Codex runs in a sandboxed environment by default — try the CLI first, and fall back to the deploy script if auth fails.\n\n1. **Check whether the Vercel CLI is installed** (no escalation needed for this check):\n   ```bash\n   command -v vercel\n   ```\n\n2. **If `vercel` is installed**, try deploying with the CLI:\n   ```bash\n   vercel deploy [path] -y --no-wait\n   ```\n\n3. **If `vercel` is not installed, or the CLI fails with \"No existing credentials found\"**, use the fallback script:\n   ```bash\n   skill_dir=\"\u003Cpath-to-skill>\"\n\n   # Deploy current directory\n   bash \"$skill_dir\u002Fresources\u002Fdeploy-codex.sh\"\n\n   # Deploy specific project\n   bash \"$skill_dir\u002Fresources\u002Fdeploy-codex.sh\" \u002Fpath\u002Fto\u002Fproject\n\n   # Deploy existing tarball\n   bash \"$skill_dir\u002Fresources\u002Fdeploy-codex.sh\" \u002Fpath\u002Fto\u002Fproject.tgz\n   ```\n\nThe script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with `previewUrl` and `claimUrl`.\n\n**Tell the user:** \"Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment.\"\n\n**Escalated network access:** Only escalate the actual deploy command if sandboxing blocks the network call (`sandbox_permissions=require_escalated`). Do **not** escalate the `command -v vercel` check.\n\n---\n\n## Agent-Specific Notes\n\n### Codex\n\nCodex runs in a sandbox. Check if the CLI is available first, then fall back to the deploy script. Go to the **no-auth fallback — Codex sandbox**.\n\n---\n\n## Output\n\nAlways show the user the deployment URL.\n\n- **Git push:** Use `vercel ls --format json` to find the preview URL. If the CLI isn't authenticated, tell the user to check the Vercel dashboard or commit status checks.\n- **CLI deploy:** Show the URL returned by `vercel deploy --no-wait`. Use `vercel inspect \u003Curl>` to check build status and report it to the user.\n- **No-auth fallback:** Show both the preview URL and the claim URL:\n  ```\n  Deployment successful!\n\n  Preview URL: https:\u002F\u002Fmy-app-abc123.vercel.app\n  Claim URL:   https:\u002F\u002Fvercel.com\u002Fclaim-deployment?code=...\n\n  View your site at the Preview URL.\n  To transfer this deployment to your Vercel account, visit the Claim URL.\n  ```\n\n**Do not** curl or fetch the deployed URL to verify it works. Just return the link.\n\n---\n\n## Troubleshooting\n\n### Escalated Network Access (Codex \u002F sandboxed environments)\n\nIf deployment fails due to network issues (timeouts, DNS errors, connection resets) in a sandboxed environment, rerun with escalated permissions (`sandbox_permissions=require_escalated`). Do not escalate the initial CLI availability check — only escalate the actual deploy command.\n\nExample guidance to the user:\n```\nThe deploy needs escalated network access to deploy to Vercel. I can rerun\nthe command with escalated permissions — want me to proceed?\n```\n\n### CLI Auth Failure\n\nIf `vercel login` or `vercel deploy` fails with authentication errors, fall back to the Codex no-auth deploy script.\n","# Deploy to Vercel\n\nDeploy any project to Vercel. **Always deploy as preview** (not production) unless the user explicitly asks for production.\n\nThe goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state.\n\n## Step 1: Gather Project State\n\nRun all four checks before deciding which method to use:\n\n```bash\n# 1. Check for a git remote\ngit remote get-url origin 2>\u002Fdev\u002Fnull\n\n# 2. Check if locally linked to a Vercel project (either file means linked)\ncat .vercel\u002Fproject.json 2>\u002Fdev\u002Fnull || cat .vercel\u002Frepo.json 2>\u002Fdev\u002Fnull\n\n# 3. Check if the Vercel CLI is installed and authenticated\nvercel whoami 2>\u002Fdev\u002Fnull\n\n# 4. List available teams (if authenticated)\nvercel teams list --format json 2>\u002Fdev\u002Fnull\n```\n\n### Team selection\n\nIf the user belongs to multiple teams, present all available team slugs as a bulleted list and ask which one to deploy to. Once the user picks a team, proceed immediately to the next step — do not ask for additional confirmation.\n\nPass the team slug via `--scope` on all subsequent CLI commands (`vercel deploy`, `vercel link`, `vercel inspect`, etc.):\n\n```bash\nvercel deploy [path] -y --no-wait --scope \u003Cteam-slug>\n```\n\nIf the project is already linked (`.vercel\u002Fproject.json` or `.vercel\u002Frepo.json` exists), the `orgId` in those files determines the team — no need to ask again. If there is only one team (or just a personal account), skip the prompt and use it directly.\n\n**About the `.vercel\u002F` directory:** A linked project has either:\n- `.vercel\u002Fproject.json` — created by `vercel link` (single project linking). Contains `projectId` and `orgId`.\n- `.vercel\u002Frepo.json` — created by `vercel link --repo` (repo-based linking). Contains `orgId`, `remoteName`, and a `projects` array mapping directories to Vercel project IDs.\n\nEither file means the project is linked. Check for both.\n\n**Do NOT** use `vercel project inspect`, `vercel ls`, or `vercel link` to detect state in an unlinked directory — without a `.vercel\u002F` config, they will interactively prompt (or with `--yes`, silently link as a side-effect). Only `vercel whoami` is safe to run anywhere.\n\n## Step 2: Choose a Deploy Method\n\n### Linked (`.vercel\u002F` exists) + has git remote → Git Push\n\nThis is the ideal state. The project is linked and has git integration.\n\n1. **Ask the user before pushing.** Never push without explicit approval:\n   ```\n   This project is connected to Vercel via git. I can commit and push to\n   trigger a deployment. Want me to proceed?\n   ```\n\n2. **Commit and push:**\n   ```bash\n   git add .\n   git commit -m \"deploy: \u003Cdescription of changes>\"\n   git push\n   ```\n   Vercel automatically builds from the push. Non-production branches get preview deployments; the production branch (usually `main`) gets a production deployment.\n\n3. **Retrieve the preview URL.** If the CLI is authenticated:\n   ```bash\n   sleep 5\n   vercel ls --format json\n   ```\n   The JSON output has a `deployments` array. Find the latest entry — its `url` field is the preview URL.\n\n   If the CLI is not authenticated, tell the user to check the Vercel dashboard or the commit status checks on their git provider for the preview URL.\n\n---\n\n### Linked (`.vercel\u002F` exists) + no git remote → `vercel deploy`\n\nThe project is linked but there's no git repo. Deploy directly with the CLI.\n\n```bash\nvercel deploy [path] -y --no-wait\n```\n\nUse `--no-wait` so the CLI returns immediately with the deployment URL instead of blocking until the build finishes (builds can take a while). Then check on the deployment status with:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\nFor production deploys (only if user explicitly asks):\n```bash\nvercel deploy [path] --prod -y --no-wait\n```\n\n---\n\n### Not linked + CLI is authenticated → Link first, then deploy\n\nThe CLI is working but the project isn't linked yet. This is the opportunity to get the user into the best state.\n\n1. **Ask the user which team to deploy to.** Present the team slugs from Step 1 as a bulleted list. If there's only one team (or just a personal account), skip this step.\n\n2. **Once a team is selected, proceed directly to linking.** Tell the user what will happen but do not ask for separate confirmation:\n   ```\n   Linking this project to \u003Cteam name> on Vercel. This will create a Vercel\n   project to deploy to and enable automatic deployments on future git pushes.\n   ```\n\n3. **If a git remote exists**, use repo-based linking with the selected team scope:\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug>\n   ```\n   This reads the git remote URL and matches it to existing Vercel projects that deploy from that repo. It creates `.vercel\u002Frepo.json`. This is much more reliable than `vercel link` (without `--repo`), which tries to match by directory name and often fails when the local folder and Vercel project are named differently.\n\n   **If there is no git remote**, fall back to standard linking:\n   ```bash\n   vercel link --scope \u003Cteam-slug>\n   ```\n   This prompts the user to select or create a project. It creates `.vercel\u002Fproject.json`.\n\n4. **Then deploy using the best available method:**\n   - If a git remote exists → commit and push (see git push method above)\n   - If no git remote → `vercel deploy [path] -y --no-wait --scope \u003Cteam-slug>`, then `vercel inspect \u003Curl>` to check status\n\n---\n\n### Not linked + CLI not authenticated → Install, auth, link, deploy\n\nThe Vercel CLI isn't set up at all.\n\n1. **Install the CLI (if not already installed):**\n   ```bash\n   npm install -g vercel\n   ```\n\n2. **Authenticate:**\n   ```bash\n   vercel login\n   ```\n   The user completes auth in their browser. If running in a non-interactive environment where login is not possible, skip to the **no-auth fallback** below.\n\n3. **Ask which team to deploy to** — present team slugs from `vercel teams list --format json` as a bulleted list. If only one team \u002F personal account, skip. Once selected, proceed immediately.\n\n4. **Link the project** with the selected team scope (use `--repo` if a git remote exists, plain `vercel link` otherwise):\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug>   # if git remote exists\n   vercel link --scope \u003Cteam-slug>          # if no git remote\n   ```\n\n5. **Deploy** using the best available method (git push if remote exists, otherwise `vercel deploy -y --no-wait --scope \u003Cteam-slug>`, then `vercel inspect \u003Curl>` to check status).\n\n---\n\n### No-Auth Fallback — Codex sandbox\n\n**When to use:** In the Codex sandbox where the CLI may not be authenticated. Codex runs in a sandboxed environment by default — try the CLI first, and fall back to the deploy script if auth fails.\n\n1. **Check whether the Vercel CLI is installed** (no escalation needed for this check):\n   ```bash\n   command -v vercel\n   ```\n\n2. **If `vercel` is installed**, try deploying with the CLI:\n   ```bash\n   vercel deploy [path] -y --no-wait\n   ```\n\n3. **If `vercel` is not installed, or the CLI fails with \"No existing credentials found\"**, use the fallback script:\n   ```bash\n   skill_dir=\"\u003Cpath-to-skill>\"\n\n   # Deploy current directory\n   bash \"$skill_dir\u002Fresources\u002Fdeploy-codex.sh\"\n\n   # Deploy specific project\n   bash \"$skill_dir\u002Fresources\u002Fdeploy-codex.sh\" \u002Fpath\u002Fto\u002Fproject\n\n   # Deploy existing tarball\n   bash \"$skill_dir\u002Fresources\u002Fdeploy-codex.sh\" \u002Fpath\u002Fto\u002Fproject.tgz\n   ```\n\nThe script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with `previewUrl` and `claimUrl`.\n\n**Tell the user:** \"Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment.\"\n\n**Escalated network access:** Only escalate the actual deploy command if sandboxing blocks the network call (`sandbox_permissions=require_escalated`). Do **not** escalate the `command -v vercel` check.\n\n---\n\n## Agent-Specific Notes\n\n### Codex\n\nCodex runs in a sandbox. Check if the CLI is available first, then fall back to the deploy script. Go to the **no-auth fallback — Codex sandbox**.\n\n---\n\n## Output\n\nAlways show the user the deployment URL.\n\n- **Git push:** Use `vercel ls --format json` to find the preview URL. If the CLI isn't authenticated, tell the user to check the Vercel dashboard or commit status checks.\n- **CLI deploy:** Show the URL returned by `vercel deploy --no-wait`. Use `vercel inspect \u003Curl>` to check build status and report it to the user.\n- **No-auth fallback:** Show both the preview URL and the claim URL:\n  ```\n  Deployment successful!\n\n  Preview URL: https:\u002F\u002Fmy-app-abc123.vercel.app\n  Claim URL:   https:\u002F\u002Fvercel.com\u002Fclaim-deployment?code=...\n\n  View your site at the Preview URL.\n  To transfer this deployment to your Vercel account, visit the Claim URL.\n  ```\n\n**Do not** curl or fetch the deployed URL to verify it works. Just return the link.\n\n---\n\n## Troubleshooting\n\n### Escalated Network Access (Codex \u002F sandboxed environments)\n\nIf deployment fails due to network issues (timeouts, DNS errors, connection resets) in a sandboxed environment, rerun with escalated permissions (`sandbox_permissions=require_escalated`). Do not escalate the initial CLI availability check — only escalate the actual deploy command.\n\nExample guidance to the user:\n```\nThe deploy needs escalated network access to deploy to Vercel. I can rerun\nthe command with escalated permissions — want me to proceed?\n```\n\n### CLI Auth Failure\n\nIf `vercel login` or `vercel deploy` fails with authentication errors, fall back to the Codex no-auth deploy script.\n",{"name":5,"metadata":47,"description":7},{"author":24,"version":48},"3.0.0","main","9a4409c8751439c3aeeea2bc3940ba05dc3cd3b5","plugins\u002Fbuild-web-apps\u002Fskills\u002Fdeploy-to-vercel",0,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FNagyVikt","https:\u002F\u002Fwebu.hu\u002F","Codex is a tool they said...\r\n\r\nCreator of GitGuardex, CueCards. Tech stack: Next.js · TypeScript · Rust · Linux. ","2026-03-30 02:19:53",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add NagyVikt\u002Fcodex-plugins --skill deploy-to-vercel",{"tool":64,"command":65},"bunx","bunx skills add NagyVikt\u002Fcodex-plugins --skill deploy-to-vercel",{"tool":67,"command":68},"pnpm","pnpm dlx skills add NagyVikt\u002Fcodex-plugins --skill deploy-to-vercel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuild-web-apps\u002Fskills\u002Fdeploy-to-vercel\u002FSKILL.md",true,[72,78],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"Archive.zip","ASSET","资产文件",11314,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuild-web-apps\u002Fskills\u002Fdeploy-to-vercel\u002FArchive.zip",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"resources\u002Fdeploy-codex.sh","SCRIPT","脚本",8855,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuild-web-apps\u002Fskills\u002Fdeploy-to-vercel\u002Fresources\u002Fdeploy-codex.sh",[85,124,157,180,207,229],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":105,"publishedAt":42},"01M6K1ZEN8P9R2S6NPNJNJ8JVH","workflow","Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[91,94,97,102],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":103,"categoryName":104,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000038","人力资源",[87,106,40,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"workflows","run","streaming","logs","start","why","loop","wait for","branch","auto","log","conversation","human","lib","condition","rendering","retries","sleep",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":140,"publishedAt":42},"01M6K1Z71NWFSPHK2VJJ73MVSY","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[130,133,134,137],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":135,"categoryName":136,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":138,"categoryName":139,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000033","数据分析师",[126,141,108,142,143,144,114,145,146,147,148,149,150,31,151,152,153,154,155,156],"auth","routing middleware","api","projects","user story","full stack","jest","local","project","end","false","unit","error","middleware","loading","unit test",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":42},"01M6K1YPRYJS3BQEDP8HKBHPEJ","vercel-storage","Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[163],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},[165,166,24,167,107,168,169,115,170,171,172,173,174,175,31,119,176,177,178,179],"storage","vercel storage","config","supabase","migrate","router","clerk","expert","prisma","connection pooling","neon","turso","upstash","URL","auth0",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":191,"publishedAt":42},"01M6K1YFEP0GPPGMQ3D0FPTS27","vercel-services","Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[186,189,190],{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[192,193,24,194,195,196,197,198,199,200,201,49,202,203,149,204,31,205,153,206],"vercel services","services","frontend","docker compose","SET","configure","monorepo","go api","fastapi","up","aws lambda","go backend","get","apps","python backend",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":213,"publishedAt":42},"01M6K1Y8S3CRD43DPKX0PK1MTT","vercel-sandbox","Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[214,215,24,216,217,40,107,218,219,220,221,222,223,224,225,226,155,227,209,228],"sandbox","vercel sandbox","safe","ai agents","code","ai sdk","Code Generation","playground","generated","spawn","install","runner","io","child","student",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":236,"publishedAt":42},"01M6K1Y1J8S7AN97H75SHBGF7J","vercel-queues","Vercel Queues guidance (public beta) — durable event streaming with topics, consumer groups, retries, and delayed delivery. $0.60\u002F1M ops. Powers Workflow DevKit. Use when building async processing, fan-out patterns, or event-driven architectures.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-queues\u002FSKILL.md",[235],{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},[237,24,87,106,108,238,196,143,197,201,239,240,241,242,31,119,243,122,155,244],"vercel queues","beta","message","delivery","across","worker","processing","at"]