[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7971DB30G7NAP9H28YJC2Y0":3,"skill-same:01M7971DB30G7NAP9H28YJC2Y0":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},"01M7971DB30G7NAP9H28YJC2Y0","vercel-hello-world",null,"Create a minimal working Vercel deployment with a serverless API route.\nUse when starting a new Vercel project, testing your setup,\nor learning basic Vercel deployment and API route patterns.\nTrigger with phrases like \"vercel hello world\", \"vercel example\",\n\"vercel quick start\", \"simple vercel project\", \"first vercel deploy\".","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-hello-world\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-hello-world\ndescription: |\n  Create a minimal working Vercel deployment with a serverless API route.\n  Use when starting a new Vercel project, testing your setup,\n  or learning basic Vercel deployment and API route patterns.\n  Trigger with phrases like \"vercel hello world\", \"vercel example\",\n  \"vercel quick start\", \"simple vercel project\", \"first vercel deploy\".\nallowed-tools: Read, Write, Edit, Bash(vercel:*), Bash(npm:*), Bash(npx:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, vercel, api, quickstart, deployment]\n---\n# Vercel Hello World\n\n## Overview\nDeploy a minimal project to Vercel with a static page and a serverless API route. Confirms your CLI auth, project structure, and deployment pipeline work end to end.\n\n## Prerequisites\n- Completed `vercel-install-auth` setup\n- Vercel CLI installed and authenticated\n- Node.js 18+\n\n## Instructions\n\n### Step 1: Create Project Structure\n```bash\nmkdir my-vercel-app && cd my-vercel-app\nnpm init -y\n```\n\nCreate the static landing page:\n\n```html\n\u003C!-- public\u002Findex.html -->\n\u003C!DOCTYPE html>\n\u003Chtml>\n\u003Chead>\u003Ctitle>Hello Vercel\u003C\u002Ftitle>\u003C\u002Fhead>\n\u003Cbody>\n  \u003Ch1>Hello from Vercel\u003C\u002Fh1>\n  \u003Cp id=\"result\">Loading...\u003C\u002Fp>\n  \u003Cscript>\n    fetch('\u002Fapi\u002Fhello')\n      .then(r => r.json())\n      .then(d => document.getElementById('result').textContent = d.message);\n  \u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 2: Create Serverless API Route\n```typescript\n\u002F\u002F api\u002Fhello.ts\nimport type { VercelRequest, VercelResponse } from '@vercel\u002Fnode';\n\nexport default function handler(req: VercelRequest, res: VercelResponse) {\n  res.status(200).json({\n    message: 'Hello from Vercel Serverless Function!',\n    timestamp: new Date().toISOString(),\n    region: process.env.VERCEL_REGION || 'local',\n  });\n}\n```\n\nInstall the types:\n```bash\nnpm install --save-dev @vercel\u002Fnode typescript\n```\n\n### Step 3: Add vercel.json Configuration\n```json\n{\n  \"rewrites\": [\n    { \"source\": \"\u002Fapi\u002F(.*)\", \"destination\": \"\u002Fapi\u002F$1\" }\n  ],\n  \"headers\": [\n    {\n      \"source\": \"\u002Fapi\u002F(.*)\",\n      \"headers\": [\n        { \"key\": \"Cache-Control\", \"value\": \"s-maxage=0, stale-while-revalidate\" }\n      ]\n    }\n  ]\n}\n```\n\n### Step 4: Deploy Preview\n```bash\n# Deploy to a preview URL (not production)\nvercel\n\n# Output:\n# Vercel CLI 39.x.x\n# 🔗 Linked to your-team\u002Fmy-vercel-app\n# 🔍 Inspect: https:\u002F\u002Fvercel.com\u002Fyour-team\u002Fmy-vercel-app\u002Fxxx\n# ✅ Preview: https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\n```\n\n### Step 5: Test the Deployment\n```bash\n# Test static page\ncurl -s https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\u002F | head -5\n\n# Test API route\ncurl -s https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\u002Fapi\u002Fhello | jq .\n# {\n#   \"message\": \"Hello from Vercel Serverless Function!\",\n#   \"timestamp\": \"2026-03-22T12:00:00.000Z\",\n#   \"region\": \"iad1\"\n# }\n```\n\n### Step 6: Promote to Production\n```bash\n# Deploy directly to production\nvercel --prod\n\n# Or promote the preview deployment\nvercel promote https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\n```\n\n## Vercel System Environment Variables\n\nThese are available in every function at runtime:\n\n| Variable | Value |\n|----------|-------|\n| `VERCEL` | `\"1\"` — always set on Vercel |\n| `VERCEL_ENV` | `\"production\"`, `\"preview\"`, or `\"development\"` |\n| `VERCEL_URL` | Deployment URL (no protocol) |\n| `VERCEL_REGION` | Function region (e.g., `iad1`) |\n| `VERCEL_GIT_COMMIT_SHA` | Git commit hash |\n| `VERCEL_GIT_COMMIT_MESSAGE` | Git commit message |\n\n## Output\n- Static page served from Vercel CDN\n- Serverless API route returning JSON at `\u002Fapi\u002Fhello`\n- Preview URL for testing before production\n- Production deployment live on your domain\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `404 NOT_FOUND` on `\u002Fapi\u002Fhello` | File not in `api\u002F` directory | Move file to project root `api\u002F` folder |\n| `FUNCTION_INVOCATION_FAILED` | Runtime error in handler | Check function logs: `vercel logs \u003Curl>` |\n| `BUILD_FAILED` | TypeScript compilation error | Run `npx tsc --noEmit` locally first |\n| `NO_RESPONSE_FROM_FUNCTION` | Handler didn't call `res.send\u002Fjson` | Ensure all code paths return a response |\n| `FUNCTION_PAYLOAD_TOO_LARGE` | Response body > 4.5 MB | Paginate or stream the response |\n\n## Resources\n- [Vercel Serverless Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Vercel Project Configuration](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fproject-configuration)\n- [Vercel CLI Deploy](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fdeploy)\n- [@vercel\u002Fnode Runtime](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes\u002Fnode-js)\n\n## Next Steps\nProceed to `vercel-local-dev-loop` for development workflow setup.\n","# Vercel Hello World\n\n## Overview\nDeploy a minimal project to Vercel with a static page and a serverless API route. Confirms your CLI auth, project structure, and deployment pipeline work end to end.\n\n## Prerequisites\n- Completed `vercel-install-auth` setup\n- Vercel CLI installed and authenticated\n- Node.js 18+\n\n## Instructions\n\n### Step 1: Create Project Structure\n```bash\nmkdir my-vercel-app && cd my-vercel-app\nnpm init -y\n```\n\nCreate the static landing page:\n\n```html\n\u003C!-- public\u002Findex.html -->\n\u003C!DOCTYPE html>\n\u003Chtml>\n\u003Chead>\u003Ctitle>Hello Vercel\u003C\u002Ftitle>\u003C\u002Fhead>\n\u003Cbody>\n  \u003Ch1>Hello from Vercel\u003C\u002Fh1>\n  \u003Cp id=\"result\">Loading...\u003C\u002Fp>\n  \u003Cscript>\n    fetch('\u002Fapi\u002Fhello')\n      .then(r => r.json())\n      .then(d => document.getElementById('result').textContent = d.message);\n  \u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 2: Create Serverless API Route\n```typescript\n\u002F\u002F api\u002Fhello.ts\nimport type { VercelRequest, VercelResponse } from '@vercel\u002Fnode';\n\nexport default function handler(req: VercelRequest, res: VercelResponse) {\n  res.status(200).json({\n    message: 'Hello from Vercel Serverless Function!',\n    timestamp: new Date().toISOString(),\n    region: process.env.VERCEL_REGION || 'local',\n  });\n}\n```\n\nInstall the types:\n```bash\nnpm install --save-dev @vercel\u002Fnode typescript\n```\n\n### Step 3: Add vercel.json Configuration\n```json\n{\n  \"rewrites\": [\n    { \"source\": \"\u002Fapi\u002F(.*)\", \"destination\": \"\u002Fapi\u002F$1\" }\n  ],\n  \"headers\": [\n    {\n      \"source\": \"\u002Fapi\u002F(.*)\",\n      \"headers\": [\n        { \"key\": \"Cache-Control\", \"value\": \"s-maxage=0, stale-while-revalidate\" }\n      ]\n    }\n  ]\n}\n```\n\n### Step 4: Deploy Preview\n```bash\n# Deploy to a preview URL (not production)\nvercel\n\n# Output:\n# Vercel CLI 39.x.x\n# 🔗 Linked to your-team\u002Fmy-vercel-app\n# 🔍 Inspect: https:\u002F\u002Fvercel.com\u002Fyour-team\u002Fmy-vercel-app\u002Fxxx\n# ✅ Preview: https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\n```\n\n### Step 5: Test the Deployment\n```bash\n# Test static page\ncurl -s https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\u002F | head -5\n\n# Test API route\ncurl -s https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\u002Fapi\u002Fhello | jq .\n# {\n#   \"message\": \"Hello from Vercel Serverless Function!\",\n#   \"timestamp\": \"2026-03-22T12:00:00.000Z\",\n#   \"region\": \"iad1\"\n# }\n```\n\n### Step 6: Promote to Production\n```bash\n# Deploy directly to production\nvercel --prod\n\n# Or promote the preview deployment\nvercel promote https:\u002F\u002Fmy-vercel-app-xxx.vercel.app\n```\n\n## Vercel System Environment Variables\n\nThese are available in every function at runtime:\n\n| Variable | Value |\n|----------|-------|\n| `VERCEL` | `\"1\"` — always set on Vercel |\n| `VERCEL_ENV` | `\"production\"`, `\"preview\"`, or `\"development\"` |\n| `VERCEL_URL` | Deployment URL (no protocol) |\n| `VERCEL_REGION` | Function region (e.g., `iad1`) |\n| `VERCEL_GIT_COMMIT_SHA` | Git commit hash |\n| `VERCEL_GIT_COMMIT_MESSAGE` | Git commit message |\n\n## Output\n- Static page served from Vercel CDN\n- Serverless API route returning JSON at `\u002Fapi\u002Fhello`\n- Preview URL for testing before production\n- Production deployment live on your domain\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `404 NOT_FOUND` on `\u002Fapi\u002Fhello` | File not in `api\u002F` directory | Move file to project root `api\u002F` folder |\n| `FUNCTION_INVOCATION_FAILED` | Runtime error in handler | Check function logs: `vercel logs \u003Curl>` |\n| `BUILD_FAILED` | TypeScript compilation error | Run `npx tsc --noEmit` locally first |\n| `NO_RESPONSE_FROM_FUNCTION` | Handler didn't call `res.send\u002Fjson` | Ensure all code paths return a response |\n| `FUNCTION_PAYLOAD_TOO_LARGE` | Response body > 4.5 MB | Paginate or stream the response |\n\n## Resources\n- [Vercel Serverless Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Vercel Project Configuration](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fproject-configuration)\n- [Vercel CLI Deploy](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fdeploy)\n- [@vercel\u002Fnode Runtime](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes\u002Fnode-js)\n\n## Next Steps\nProceed to `vercel-local-dev-loop` for development workflow setup.\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","api","quickstart","deployment","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Create a minimal working Vercel deployment with a serverless API route.\nUse when starting a new Vercel project, testing your setup,\nor learning basic Vercel deployment and API route patterns.\nTrigger with phrases like \"vercel hello world\", \"vercel example\",\n\"vercel quick start\", \"simple vercel project\", \"first vercel deploy\".\n","Read, Write, Edit, Bash(vercel:*), Bash(npm:*), Bash(npx:*), Bash(curl:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--vercel-pack--vercel-hello-world",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-hello-world",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill vercel-hello-world",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill vercel-hello-world","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-hello-world\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",[],[]]