[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69A6ADX690STSN63WKRD37K":3,"skill-same:01M69A6ADX690STSN63WKRD37K":51},{"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":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M69A6ADX690STSN63WKRD37K","vercel-cli",null,"Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables.","microsoft\u002Famplifier-app-nanoclaw","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A31J3GTKVZDZZVPRQWWR5",5,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fvercel-cli\u002FSKILL.md",[],[19,20,21,22],"cli","vercel cli","web","deploy","2026-11-10 10:12:30",false,"---\nname: vercel-cli\ndescription: Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables.\n---\n\n# Vercel CLI\n\nYou can deploy web applications to Vercel using the `vercel` CLI.\n\n**HARD RULE: You MUST NOT write HTML, CSS, or JavaScript yourself. When asked to build a website or web app, you MUST delegate to a Frontend Engineer subagent (see \"Building Websites\" section below). This is not optional. Violation wastes your context window on code that belongs in a separate agent.**\n\n## Auth\n\nAuth is handled by OneCLI — the HTTPS_PROXY injects the real token into API requests automatically. The Vercel CLI requires a token to be present to skip its local credential check, so **always pass `--token placeholder`** on every command. OneCLI replaces this with the real token at the proxy level.\n\nBefore any Vercel operation, verify auth:\n\n```bash\nvercel whoami --token placeholder\n```\n\nIf this fails with an auth error, ask the user to add a Vercel token to OneCLI. They can create one at https:\u002F\u002Fvercel.com\u002Faccount\u002Ftokens and register it via `onecli secrets create` on the host. Once added, retry `vercel whoami`.\n\n## Deploying\n\nAlways use `--yes` to skip interactive prompts and `--token placeholder` for auth (OneCLI replaces with real token).\n\n```bash\n# Deploy to production\nvercel deploy --yes --prod --token placeholder\n\n# Deploy from a specific directory\nvercel deploy --yes --prod --token placeholder --cwd \u002Fpath\u002Fto\u002Fproject\n\n# Preview deployment (not production)\nvercel deploy --yes --token placeholder\n```\n\nAfter deploying, verify the live URL:\n\n```bash\n# Check deployment status\nvercel inspect \u003Cdeployment-url> --token placeholder\n```\n\nIf you have `agent-browser` available, open the deployed URL and take a screenshot to visually verify.\n\n## Project Management\n\n```bash\n# Link to an existing Vercel project (non-interactive)\nvercel link --yes --token placeholder\n\n# List recent deployments\nvercel ls --token placeholder\n\n# List all projects\nvercel project ls --token placeholder\n```\n\n## Domains\n\n```bash\n# List domains\nvercel domains ls --token placeholder\n\n# Add a domain to the current project\nvercel domains add example.com --token placeholder\n```\n\n## Environment Variables\n\n```bash\n# Pull env vars from Vercel to local .env\nvercel env pull --token placeholder\n\n# Add an env var (use echo to pipe the value — avoids interactive prompt)\necho \"value\" | vercel env add VAR_NAME production --token placeholder\n```\n\n## Common Errors\n\n| Error | Fix |\n|-------|-----|\n| `Error: No framework detected` | Ensure the project has a `package.json` with a `build` script, or set the framework in `vercel.json` |\n| `Error: Rate limited` | Wait and retry. Don't loop — report to user |\n| `Error: You have reached your project limit` | User needs to upgrade Vercel plan or delete unused projects |\n| `ENOTFOUND api.vercel.com` | Network issue. Check proxy connectivity |\n| Auth error after `vercel whoami` | Credential may be expired. Ask the user to refresh the Vercel token in OneCLI |\n\n## Building Websites — Delegate to Frontend Engineer\n\nWhen asked to **build, create, or redesign** a website or web app, do NOT build it yourself. You MUST delegate to a Frontend Engineer agent. This is a two-step process and **both steps are required**:\n\n**Step 1 — Create the agent** (skip if you already have a \"frontend-engineer\" destination):\n\n```\ncreate_agent({\n  name: \"Frontend Engineer\",\n  instructions: \"You are a dedicated frontend engineer. Your frontend-engineer skill has your full workflow. Build what is requested, test it visually with agent-browser, deploy to Vercel, and send back the live URL + screenshots to your parent agent when done.\"\n})\n```\n\n**Step 2 — Send the build request** (MANDATORY — do this immediately after step 1):\n\n```\nsend_message(to: \"frontend-engineer\", text: \"\u003Cfull description of what to build, including design requirements, content, colors, and any assets>\")\n```\n\n⚠️ **CRITICAL**: If you skip step 2, nothing happens. The agent exists but has no work. You MUST send the message. Do NOT tell the user \"it's working on it\" until you have actually called send_message.\n\nAfter sending, tell the user you've handed it off and will share the result when it comes back. The Frontend Engineer will send you the live URL + screenshots when done — forward those to the user.\n\n**When to delegate vs do it yourself:**\n- **Delegate**: building new sites, redesigns, multi-page apps, anything that needs visual testing\n- **Do yourself**: simple `vercel deploy` of an existing project, checking deployment status, managing domains\u002Fenv vars\n\n## Best Practices\n\n- Run `pnpm run build` locally before deploying to catch build errors early\n- Use `--cwd` instead of `cd` to keep your working directory stable\n- For Next.js projects, `vercel deploy` auto-detects the framework — no extra config needed\n- Use `vercel.json` only when you need custom build settings, rewrites, or headers\n","# Vercel CLI\n\nYou can deploy web applications to Vercel using the `vercel` CLI.\n\n**HARD RULE: You MUST NOT write HTML, CSS, or JavaScript yourself. When asked to build a website or web app, you MUST delegate to a Frontend Engineer subagent (see \"Building Websites\" section below). This is not optional. Violation wastes your context window on code that belongs in a separate agent.**\n\n## Auth\n\nAuth is handled by OneCLI — the HTTPS_PROXY injects the real token into API requests automatically. The Vercel CLI requires a token to be present to skip its local credential check, so **always pass `--token placeholder`** on every command. OneCLI replaces this with the real token at the proxy level.\n\nBefore any Vercel operation, verify auth:\n\n```bash\nvercel whoami --token placeholder\n```\n\nIf this fails with an auth error, ask the user to add a Vercel token to OneCLI. They can create one at https:\u002F\u002Fvercel.com\u002Faccount\u002Ftokens and register it via `onecli secrets create` on the host. Once added, retry `vercel whoami`.\n\n## Deploying\n\nAlways use `--yes` to skip interactive prompts and `--token placeholder` for auth (OneCLI replaces with real token).\n\n```bash\n# Deploy to production\nvercel deploy --yes --prod --token placeholder\n\n# Deploy from a specific directory\nvercel deploy --yes --prod --token placeholder --cwd \u002Fpath\u002Fto\u002Fproject\n\n# Preview deployment (not production)\nvercel deploy --yes --token placeholder\n```\n\nAfter deploying, verify the live URL:\n\n```bash\n# Check deployment status\nvercel inspect \u003Cdeployment-url> --token placeholder\n```\n\nIf you have `agent-browser` available, open the deployed URL and take a screenshot to visually verify.\n\n## Project Management\n\n```bash\n# Link to an existing Vercel project (non-interactive)\nvercel link --yes --token placeholder\n\n# List recent deployments\nvercel ls --token placeholder\n\n# List all projects\nvercel project ls --token placeholder\n```\n\n## Domains\n\n```bash\n# List domains\nvercel domains ls --token placeholder\n\n# Add a domain to the current project\nvercel domains add example.com --token placeholder\n```\n\n## Environment Variables\n\n```bash\n# Pull env vars from Vercel to local .env\nvercel env pull --token placeholder\n\n# Add an env var (use echo to pipe the value — avoids interactive prompt)\necho \"value\" | vercel env add VAR_NAME production --token placeholder\n```\n\n## Common Errors\n\n| Error | Fix |\n|-------|-----|\n| `Error: No framework detected` | Ensure the project has a `package.json` with a `build` script, or set the framework in `vercel.json` |\n| `Error: Rate limited` | Wait and retry. Don't loop — report to user |\n| `Error: You have reached your project limit` | User needs to upgrade Vercel plan or delete unused projects |\n| `ENOTFOUND api.vercel.com` | Network issue. Check proxy connectivity |\n| Auth error after `vercel whoami` | Credential may be expired. Ask the user to refresh the Vercel token in OneCLI |\n\n## Building Websites — Delegate to Frontend Engineer\n\nWhen asked to **build, create, or redesign** a website or web app, do NOT build it yourself. You MUST delegate to a Frontend Engineer agent. This is a two-step process and **both steps are required**:\n\n**Step 1 — Create the agent** (skip if you already have a \"frontend-engineer\" destination):\n\n```\ncreate_agent({\n  name: \"Frontend Engineer\",\n  instructions: \"You are a dedicated frontend engineer. Your frontend-engineer skill has your full workflow. Build what is requested, test it visually with agent-browser, deploy to Vercel, and send back the live URL + screenshots to your parent agent when done.\"\n})\n```\n\n**Step 2 — Send the build request** (MANDATORY — do this immediately after step 1):\n\n```\nsend_message(to: \"frontend-engineer\", text: \"\u003Cfull description of what to build, including design requirements, content, colors, and any assets>\")\n```\n\n⚠️ **CRITICAL**: If you skip step 2, nothing happens. The agent exists but has no work. You MUST send the message. Do NOT tell the user \"it's working on it\" until you have actually called send_message.\n\nAfter sending, tell the user you've handed it off and will share the result when it comes back. The Frontend Engineer will send you the live URL + screenshots when done — forward those to the user.\n\n**When to delegate vs do it yourself:**\n- **Delegate**: building new sites, redesigns, multi-page apps, anything that needs visual testing\n- **Do yourself**: simple `vercel deploy` of an existing project, checking deployment status, managing domains\u002Fenv vars\n\n## Best Practices\n\n- Run `pnpm run build` locally before deploying to catch build errors early\n- Use `--cwd` instead of `cd` to keep your working directory stable\n- For Next.js projects, `vercel deploy` auto-detects the framework — no extra config needed\n- Use `vercel.json` only when you need custom build settings, rewrites, or headers\n",{"name":5,"description":7},"main","85a2d934766d21e4696ac1b00157179f28bca9e3","container\u002Fskills\u002Fvercel-cli",2,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-30 04:24:16",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add microsoft\u002Famplifier-app-nanoclaw --skill vercel-cli",{"tool":43,"command":44},"bunx","bunx skills add microsoft\u002Famplifier-app-nanoclaw --skill vercel-cli",{"tool":46,"command":47},"pnpm","pnpm dlx skills add microsoft\u002Famplifier-app-nanoclaw --skill vercel-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fvercel-cli\u002FSKILL.md",true,[],[52,61,68,82,95,106],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":23},"01M69A6E27JZN10H82TZ2GMC3A","whatsapp-formatting","Format messages for WhatsApp, including mentions that render as real WhatsApp tags. Use when responding in a WhatsApp conversation (platform_id \u002F chatJid ends with @s.whatsapp.net or @g.us).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fwhatsapp-formatting\u002FSKILL.md",[],[59,60],"whatsapp formatting","whatsapp",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":23},"01M69A6CGJ968RNVGYTRSWZKWB","welcome","Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fwelcome\u002FSKILL.md",[],[63],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":23},"01M69A68WJ94V4MXGXGK9T0QG7","slack-formatting","Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with \"slack_\" or JID contains slack identifiers).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fslack-formatting\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[80,81],"slack formatting","slack",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":23},"01M69A673Z17TDXK3DBC5YJFM7","self-customize","Customize your own agent — add capabilities, install packages, add MCP servers, edit code or CLAUDE.md. Use when the user asks you to add a feature, install a tool, or modify how you work. For non-trivial code changes, delegate to a builder agent via create_agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fself-customize\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发",[92,93,94],"self customize","customize","MCP",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":102,"publishedAt":23},"01M69A657JFNEG45Z1Y05BVK5R","onecli-gateway","OneCLI Gateway: transparent HTTPS proxy that injects stored credentials into outbound calls. You MUST use this skill when the user asks you to read emails, check calendar, access GitHub repos, create issues, check Stripe payments, or interact with ANY external service or API. Do NOT use browser extensions or OAuth CLI tools. Make HTTP requests directly; the gateway injects credentials automatically.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fonecli-gateway\u002FSKILL.md",[101],{"categoryNo":89,"categoryName":90,"taxonomyType":77,"taxonomyTypeDesc":78},[103,104,105,19],"onecli gateway","repos","github",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":115,"publishedAt":23},"01M69A637C4RNE0PH92G5Q3HE9","frontend-engineer","Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Use alongside vercel-cli for production-quality deployments.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Famplifier-app-nanoclaw\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Ffrontend-engineer\u002FSKILL.md",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000009","前端开发",[116,117,21,118,119,19],"frontend","frontend engineer","test","workflow"]