[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7971PFD8BAYN72VM49Q2HKS":3,"skill-same:01M7971PFD8BAYN72VM49Q2HKS":58},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7971PFD8BAYN72VM49Q2HKS","vercel-install-auth",null,"Install Vercel CLI and configure API token authentication.\nUse when setting up Vercel for the first time, creating access tokens,\nor initializing a project with vercel link.\nTrigger with phrases like \"install vercel\", \"setup vercel\",\n\"vercel auth\", \"configure vercel token\", \"vercel login\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-install-auth\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-install-auth\ndescription: |\n  Install Vercel CLI and configure API token authentication.\n  Use when setting up Vercel for the first time, creating access tokens,\n  or initializing a project with vercel link.\n  Trigger with phrases like \"install vercel\", \"setup vercel\",\n  \"vercel auth\", \"configure vercel token\", \"vercel login\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(vercel:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, vercel, authentication, cli, setup]\n---\n# Vercel Install & Auth\n\n## Overview\nInstall the Vercel CLI, create a scoped access token, and link your local project to a Vercel project. This skill covers both interactive login and headless CI token authentication via the REST API.\n\n## Prerequisites\n- Node.js 18+ installed\n- npm, pnpm, or yarn available\n- A Vercel account (hobby, pro, or enterprise)\n\n## Instructions\n\n### Step 1: Install Vercel CLI\n```bash\nset -euo pipefail\n# Global install (recommended)\nnpm install -g vercel@latest\n\n# Or project-local\nnpm install --save-dev vercel@latest\n\n# Verify installation\nvercel --version\n```\n\n### Step 2: Authenticate — Interactive Login\n```bash\n# Opens browser for OAuth login, stores token in ~\u002F.config\u002Fcom.vercel.cli\nvercel login\n\n# Or login with a specific email\nvercel login your@email.com\n\n# Login with GitHub\nvercel login --github\n\n# Login with GitLab\nvercel login --gitlab\n```\n\n### Step 3: Authenticate — Headless Token (CI\u002FCD)\nCreate a token in the Vercel dashboard at **Settings > Tokens** or via the API:\n\n```bash\n# Use a pre-created token — set as environment variable\nexport VERCEL_TOKEN=\"your-access-token-here\"\n\n# The CLI reads VERCEL_TOKEN automatically — no login needed\nvercel whoami\n# Output: your-username\n\n# Scope the token to a specific team\nexport VERCEL_ORG_ID=\"team_xxxxxxxxxxxx\"\nexport VERCEL_PROJECT_ID=\"prj_xxxxxxxxxxxx\"\n```\n\n### Step 4: Link Local Project\n```bash\n# Interactive — walks you through project selection\nvercel link\n\n# Or link to a specific project by name\nvercel link --project my-project-name\n\n# Verify the link — pulls .vercel\u002Fproject.json\ncat .vercel\u002Fproject.json\n# {\"orgId\":\"team_xxx\",\"projectId\":\"prj_xxx\"}\n```\n\n### Step 5: Verify Connection via REST API\n```bash\n# Test token against the REST API directly\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  https:\u002F\u002Fapi.vercel.com\u002Fv9\u002Fprojects | jq '.projects[].name'\n\n# List teams\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  https:\u002F\u002Fapi.vercel.com\u002Fv2\u002Fteams | jq '.teams[].name'\n```\n\n### Step 6: Pull Environment Variables\n```bash\n# Pull remote env vars to local .env.development.local\nvercel env pull .env.development.local\n\n# Pull for a specific environment\nvercel env pull --environment=preview\n```\n\n## Token Scopes Reference\n\n| Scope | Access | Use Case |\n|-------|--------|----------|\n| Full Account | All projects, all teams | Personal dev |\n| Team-scoped | One team only | Team CI\u002FCD |\n| Project-scoped | One project only | Per-project automation |\n\nTokens support optional expiration dates. Set short-lived tokens (90 days) for CI and rotate them on a schedule.\n\n## Output\n- Vercel CLI installed and on PATH\n- Authentication token stored or environment variable set\n- Local project linked to Vercel project via `.vercel\u002Fproject.json`\n- Environment variables pulled to local `.env.development.local`\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `Error: No token found` | Not logged in, no VERCEL_TOKEN | Run `vercel login` or export VERCEL_TOKEN |\n| `Error: Invalid token` | Token expired or revoked | Generate new token at vercel.com\u002Faccount\u002Ftokens |\n| `EACCES permission denied` | Global install without sudo | Use `npx vercel` or install with `--prefix ~\u002F.npm-global` |\n| `Error: Team not found` | Wrong VERCEL_ORG_ID | Check team ID in Vercel dashboard > Settings > General |\n| `fetch failed` | Network or proxy issue | Check `HTTPS_PROXY` env var, ensure port 443 outbound |\n\n## `.gitignore` Setup\n```gitignore\n# Vercel\n.vercel\u002F\n.env*.local\n```\n\n## Resources\n- [Vercel CLI Overview](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli)\n- [Access Tokens](https:\u002F\u002Fvercel.com\u002Fdocs\u002Frest-api#creating-an-access-token)\n- [CLI Project Linking](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fproject-linking)\n- [Vercel REST API Reference](https:\u002F\u002Fvercel.com\u002Fdocs\u002Frest-api)\n\n## Next Steps\nAfter successful auth, proceed to `vercel-hello-world` for your first deployment.\n","# Vercel Install & Auth\n\n## Overview\nInstall the Vercel CLI, create a scoped access token, and link your local project to a Vercel project. This skill covers both interactive login and headless CI token authentication via the REST API.\n\n## Prerequisites\n- Node.js 18+ installed\n- npm, pnpm, or yarn available\n- A Vercel account (hobby, pro, or enterprise)\n\n## Instructions\n\n### Step 1: Install Vercel CLI\n```bash\nset -euo pipefail\n# Global install (recommended)\nnpm install -g vercel@latest\n\n# Or project-local\nnpm install --save-dev vercel@latest\n\n# Verify installation\nvercel --version\n```\n\n### Step 2: Authenticate — Interactive Login\n```bash\n# Opens browser for OAuth login, stores token in ~\u002F.config\u002Fcom.vercel.cli\nvercel login\n\n# Or login with a specific email\nvercel login your@email.com\n\n# Login with GitHub\nvercel login --github\n\n# Login with GitLab\nvercel login --gitlab\n```\n\n### Step 3: Authenticate — Headless Token (CI\u002FCD)\nCreate a token in the Vercel dashboard at **Settings > Tokens** or via the API:\n\n```bash\n# Use a pre-created token — set as environment variable\nexport VERCEL_TOKEN=\"your-access-token-here\"\n\n# The CLI reads VERCEL_TOKEN automatically — no login needed\nvercel whoami\n# Output: your-username\n\n# Scope the token to a specific team\nexport VERCEL_ORG_ID=\"team_xxxxxxxxxxxx\"\nexport VERCEL_PROJECT_ID=\"prj_xxxxxxxxxxxx\"\n```\n\n### Step 4: Link Local Project\n```bash\n# Interactive — walks you through project selection\nvercel link\n\n# Or link to a specific project by name\nvercel link --project my-project-name\n\n# Verify the link — pulls .vercel\u002Fproject.json\ncat .vercel\u002Fproject.json\n# {\"orgId\":\"team_xxx\",\"projectId\":\"prj_xxx\"}\n```\n\n### Step 5: Verify Connection via REST API\n```bash\n# Test token against the REST API directly\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  https:\u002F\u002Fapi.vercel.com\u002Fv9\u002Fprojects | jq '.projects[].name'\n\n# List teams\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  https:\u002F\u002Fapi.vercel.com\u002Fv2\u002Fteams | jq '.teams[].name'\n```\n\n### Step 6: Pull Environment Variables\n```bash\n# Pull remote env vars to local .env.development.local\nvercel env pull .env.development.local\n\n# Pull for a specific environment\nvercel env pull --environment=preview\n```\n\n## Token Scopes Reference\n\n| Scope | Access | Use Case |\n|-------|--------|----------|\n| Full Account | All projects, all teams | Personal dev |\n| Team-scoped | One team only | Team CI\u002FCD |\n| Project-scoped | One project only | Per-project automation |\n\nTokens support optional expiration dates. Set short-lived tokens (90 days) for CI and rotate them on a schedule.\n\n## Output\n- Vercel CLI installed and on PATH\n- Authentication token stored or environment variable set\n- Local project linked to Vercel project via `.vercel\u002Fproject.json`\n- Environment variables pulled to local `.env.development.local`\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `Error: No token found` | Not logged in, no VERCEL_TOKEN | Run `vercel login` or export VERCEL_TOKEN |\n| `Error: Invalid token` | Token expired or revoked | Generate new token at vercel.com\u002Faccount\u002Ftokens |\n| `EACCES permission denied` | Global install without sudo | Use `npx vercel` or install with `--prefix ~\u002F.npm-global` |\n| `Error: Team not found` | Wrong VERCEL_ORG_ID | Check team ID in Vercel dashboard > Settings > General |\n| `fetch failed` | Network or proxy issue | Check `HTTPS_PROXY` env var, ensure port 443 outbound |\n\n## `.gitignore` Setup\n```gitignore\n# Vercel\n.vercel\u002F\n.env*.local\n```\n\n## Resources\n- [Vercel CLI Overview](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli)\n- [Access Tokens](https:\u002F\u002Fvercel.com\u002Fdocs\u002Frest-api#creating-an-access-token)\n- [CLI Project Linking](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fproject-linking)\n- [Vercel REST API Reference](https:\u002F\u002Fvercel.com\u002Fdocs\u002Frest-api)\n\n## Next Steps\nAfter successful auth, proceed to `vercel-hello-world` for your first deployment.\n",{"name":5,"tags":24,"author":30,"license":15,"version":31,"description":32,"allowed-tools":33,"compatible-with":34},[25,26,27,28,29],"saas","vercel","authentication","cli","setup","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Install Vercel CLI and configure API token authentication.\nUse when setting up Vercel for the first time, creating access tokens,\nor initializing a project with vercel link.\nTrigger with phrases like \"install vercel\", \"setup vercel\",\n\"vercel auth\", \"configure vercel token\", \"vercel login\".\n","Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(vercel:*), Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--vercel-pack--vercel-install-auth",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill vercel-install-auth",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill vercel-install-auth",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill vercel-install-auth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-install-auth\u002FSKILL.md",true,[],[59,66,73,80,87,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"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":101,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]