[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79707HNEVPAHW4WN07Y8VCJ":3,"skill-same:01M79707HNEVPAHW4WN07Y8VCJ":57},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M79707HNEVPAHW4WN07Y8VCJ","vercel-common-errors",null,"Diagnose and fix common Vercel deployment and function errors.\nUse when encountering Vercel errors, debugging failed deployments,\nor troubleshooting serverless function issues.\nTrigger with phrases like \"vercel error\", \"fix vercel\",\n\"vercel not working\", \"debug vercel\", \"vercel 500\", \"vercel build failed\".","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-common-errors\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-common-errors\ndescription: |\n  Diagnose and fix common Vercel deployment and function errors.\n  Use when encountering Vercel errors, debugging failed deployments,\n  or troubleshooting serverless function issues.\n  Trigger with phrases like \"vercel error\", \"fix vercel\",\n  \"vercel not working\", \"debug vercel\", \"vercel 500\", \"vercel build failed\".\nallowed-tools: Read, Grep, Bash(vercel:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, vercel, debugging, errors]\n---\n# Vercel Common Errors\n\n## Overview\nDiagnose and resolve the most common Vercel errors across three layers: build pipeline, serverless function runtime, and edge network. Each error includes the error code, root cause, and step-by-step fix.\n\n## Prerequisites\n- Vercel CLI installed\n- Access to deployment logs (`vercel logs \u003Curl>`)\n- Access to Vercel dashboard for build logs\n\n## Instructions\n\n### Step 1: Identify the Error Layer\n```bash\n# Check deployment status and error details\nvercel inspect \u003Cdeployment-url>\n\n# View function runtime logs\nvercel logs \u003Cdeployment-url> --follow\n\n# View build logs via API\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002Fdpl_xxx\" | jq '.state, .errorMessage'\n```\n\n**Three error layers:**\n1. **Build errors** — appear during `vercel deploy`, exit codes in build log\n2. **Runtime errors** — appear when functions are invoked, visible in function logs\n3. **Edge\u002Frouting errors** — HTTP errors from Vercel's edge network\n\n### Step 2: Build Errors\n\n**`BUILD_FAILED` — Build command exited with non-zero code**\n```\nError: Command \"npm run build\" exited with 1\n```\n- Check: `vercel.json` → `buildCommand` matches your build script\n- Check: all dependencies listed in `package.json` (not just devDependencies for runtime deps)\n- Fix: run `npm run build` locally to reproduce\n\n**`MISSING_BUILD_SCRIPT` — No build command found**\n```\nError: Missing Build Command\n```\n- Fix: add `\"build\"` to `package.json` scripts or set `buildCommand` in vercel.json\n- For static sites: set `buildCommand` to empty string or `\"true\"`\n\n**`FUNCTION_PAYLOAD_TOO_LARGE` — Serverless function bundle > 250 MB**\n```\nError: The Serverless Function \"api\u002Fheavy\" is 267 MB which exceeds the maximum size of 250 MB\n```\n- Fix: add unused packages to `.vercelignore`, use dynamic imports, split into smaller functions\n- Check: `@vercel\u002Fnft` trace output to see what is being bundled\n\n### Step 3: Runtime Errors\n\n**`FUNCTION_INVOCATION_FAILED` — Unhandled exception in function**\n```bash\n# View the actual error\nvercel logs \u003Cdeployment-url> --output=short\n```\n- Common causes: undefined env var, missing database connection, unhandled promise rejection\n- Fix: wrap handler in try\u002Fcatch, verify all env vars are set for the target environment\n\n**`FUNCTION_INVOCATION_TIMEOUT` — Function exceeded max duration**\n```\nError: Task timed out after 10.00 seconds\n```\n- Hobby: 10s max, Pro: 60s default (up to 300s), Enterprise: 900s\n- Fix: optimize database queries, add connection pooling, or move to background processing\n- Configure in vercel.json:\n```json\n{\n  \"functions\": {\n    \"api\u002Fslow-endpoint.ts\": {\n      \"maxDuration\": 60\n    }\n  }\n}\n```\n\n**`NO_RESPONSE_FROM_FUNCTION` — Function didn't return a response**\n- Cause: handler has a code path that doesn't call `res.send()`, `res.json()`, or return a Response\n- Fix: ensure ALL code paths return a response, including error handlers\n\n**`FUNCTION_THROTTLED` — Too many concurrent function invocations**\n- Hobby: 10 concurrent, Pro: 1000 concurrent\n- Fix: implement client-side retry with backoff, or upgrade plan\n\n### Step 4: Edge\u002FRouting Errors\n\n**`404 NOT_FOUND`**\n- API route 404: verify file is in `api\u002F` or `pages\u002Fapi\u002F` directory\n- Page 404: check `outputDirectory` in vercel.json, verify build output contains the file\n- Fix: run `vercel inspect \u003Curl>` to see the deployment file listing\n\n**`504 GATEWAY_TIMEOUT`**\n- Serverless function exceeded its timeout — same as FUNCTION_INVOCATION_TIMEOUT\n- Fix: increase `maxDuration` or optimize function\n\n**`413 REQUEST_ENTITY_TOO_LARGE`**\n- Request body exceeds 4.5 MB limit\n- Fix: use chunked upload, stream the body, or use presigned URLs for large files\n\n**`DEPLOYMENT_NOT_FOUND`**\n- Deployment was deleted or URL is malformed\n- Fix: verify the deployment still exists with `vercel ls`\n\n### Step 5: Environment Variable Errors\n\n**`ReferenceError: process is not defined` (Edge Runtime)**\n- Cause: using `process.env` in an edge function\n- Fix: Edge Functions can read env vars but only those defined at build time. Ensure vars are set.\n\n**Env var undefined in production but works in preview**\n- Cause: variable scoped to Preview only, not Production\n- Fix: check scopes in **Settings > Environment Variables**, add Production target\n\n```bash\n# Check which environments have the variable\nvercel env ls | grep DATABASE_URL\n```\n\n## Quick Diagnosis Flowchart\n\n```\nError occurred\n├── During build? → Check build logs, run `npm run build` locally\n├── During function invocation? → Check function logs with `vercel logs`\n├── HTTP 404? → Verify file exists in deployment: `vercel inspect`\n├── HTTP 500? → Unhandled exception in function code\n├── HTTP 504? → Function timeout — increase maxDuration\n└── HTTP 429? → Rate limited — implement retry with backoff\n```\n\n## Output\n- Error layer identified (build, runtime, or edge)\n- Root cause diagnosed using logs and inspection\n- Fix applied and verified via new deployment\n- Prevention measures documented\n\n## Error Handling\n| Error Code | HTTP | Layer | Quick Fix |\n|-----------|------|-------|-----------|\n| `BUILD_FAILED` | — | Build | Run build locally, check deps |\n| `FUNCTION_INVOCATION_FAILED` | 500 | Runtime | Check env vars, add try\u002Fcatch |\n| `FUNCTION_INVOCATION_TIMEOUT` | 504 | Runtime | Increase maxDuration in vercel.json |\n| `FUNCTION_THROTTLED` | 429 | Runtime | Reduce concurrency or upgrade plan |\n| `FUNCTION_PAYLOAD_TOO_LARGE` | 413 | Build | Reduce bundle size |\n| `NOT_FOUND` | 404 | Edge | Verify file paths and routes |\n| `EDGE_FUNCTION_INVOCATION_FAILED` | 500 | Edge | Remove Node.js APIs from edge code |\n| `NO_RESPONSE_FROM_FUNCTION` | 502 | Runtime | Return response from all code paths |\n\n## Resources\n- [Vercel Error Codes](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ferrors)\n- [Function Limitations](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Flimitations)\n- [Platform Limits](https:\u002F\u002Fvercel.com\u002Fdocs\u002Flimits)\n- [Vercel Status Page](https:\u002F\u002Fwww.vercel-status.com)\n- [Vercel Logs CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Flogs)\n\n## Next Steps\nFor detailed debug bundles, see `vercel-debug-bundle`.\n","# Vercel Common Errors\n\n## Overview\nDiagnose and resolve the most common Vercel errors across three layers: build pipeline, serverless function runtime, and edge network. Each error includes the error code, root cause, and step-by-step fix.\n\n## Prerequisites\n- Vercel CLI installed\n- Access to deployment logs (`vercel logs \u003Curl>`)\n- Access to Vercel dashboard for build logs\n\n## Instructions\n\n### Step 1: Identify the Error Layer\n```bash\n# Check deployment status and error details\nvercel inspect \u003Cdeployment-url>\n\n# View function runtime logs\nvercel logs \u003Cdeployment-url> --follow\n\n# View build logs via API\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002Fdpl_xxx\" | jq '.state, .errorMessage'\n```\n\n**Three error layers:**\n1. **Build errors** — appear during `vercel deploy`, exit codes in build log\n2. **Runtime errors** — appear when functions are invoked, visible in function logs\n3. **Edge\u002Frouting errors** — HTTP errors from Vercel's edge network\n\n### Step 2: Build Errors\n\n**`BUILD_FAILED` — Build command exited with non-zero code**\n```\nError: Command \"npm run build\" exited with 1\n```\n- Check: `vercel.json` → `buildCommand` matches your build script\n- Check: all dependencies listed in `package.json` (not just devDependencies for runtime deps)\n- Fix: run `npm run build` locally to reproduce\n\n**`MISSING_BUILD_SCRIPT` — No build command found**\n```\nError: Missing Build Command\n```\n- Fix: add `\"build\"` to `package.json` scripts or set `buildCommand` in vercel.json\n- For static sites: set `buildCommand` to empty string or `\"true\"`\n\n**`FUNCTION_PAYLOAD_TOO_LARGE` — Serverless function bundle > 250 MB**\n```\nError: The Serverless Function \"api\u002Fheavy\" is 267 MB which exceeds the maximum size of 250 MB\n```\n- Fix: add unused packages to `.vercelignore`, use dynamic imports, split into smaller functions\n- Check: `@vercel\u002Fnft` trace output to see what is being bundled\n\n### Step 3: Runtime Errors\n\n**`FUNCTION_INVOCATION_FAILED` — Unhandled exception in function**\n```bash\n# View the actual error\nvercel logs \u003Cdeployment-url> --output=short\n```\n- Common causes: undefined env var, missing database connection, unhandled promise rejection\n- Fix: wrap handler in try\u002Fcatch, verify all env vars are set for the target environment\n\n**`FUNCTION_INVOCATION_TIMEOUT` — Function exceeded max duration**\n```\nError: Task timed out after 10.00 seconds\n```\n- Hobby: 10s max, Pro: 60s default (up to 300s), Enterprise: 900s\n- Fix: optimize database queries, add connection pooling, or move to background processing\n- Configure in vercel.json:\n```json\n{\n  \"functions\": {\n    \"api\u002Fslow-endpoint.ts\": {\n      \"maxDuration\": 60\n    }\n  }\n}\n```\n\n**`NO_RESPONSE_FROM_FUNCTION` — Function didn't return a response**\n- Cause: handler has a code path that doesn't call `res.send()`, `res.json()`, or return a Response\n- Fix: ensure ALL code paths return a response, including error handlers\n\n**`FUNCTION_THROTTLED` — Too many concurrent function invocations**\n- Hobby: 10 concurrent, Pro: 1000 concurrent\n- Fix: implement client-side retry with backoff, or upgrade plan\n\n### Step 4: Edge\u002FRouting Errors\n\n**`404 NOT_FOUND`**\n- API route 404: verify file is in `api\u002F` or `pages\u002Fapi\u002F` directory\n- Page 404: check `outputDirectory` in vercel.json, verify build output contains the file\n- Fix: run `vercel inspect \u003Curl>` to see the deployment file listing\n\n**`504 GATEWAY_TIMEOUT`**\n- Serverless function exceeded its timeout — same as FUNCTION_INVOCATION_TIMEOUT\n- Fix: increase `maxDuration` or optimize function\n\n**`413 REQUEST_ENTITY_TOO_LARGE`**\n- Request body exceeds 4.5 MB limit\n- Fix: use chunked upload, stream the body, or use presigned URLs for large files\n\n**`DEPLOYMENT_NOT_FOUND`**\n- Deployment was deleted or URL is malformed\n- Fix: verify the deployment still exists with `vercel ls`\n\n### Step 5: Environment Variable Errors\n\n**`ReferenceError: process is not defined` (Edge Runtime)**\n- Cause: using `process.env` in an edge function\n- Fix: Edge Functions can read env vars but only those defined at build time. Ensure vars are set.\n\n**Env var undefined in production but works in preview**\n- Cause: variable scoped to Preview only, not Production\n- Fix: check scopes in **Settings > Environment Variables**, add Production target\n\n```bash\n# Check which environments have the variable\nvercel env ls | grep DATABASE_URL\n```\n\n## Quick Diagnosis Flowchart\n\n```\nError occurred\n├── During build? → Check build logs, run `npm run build` locally\n├── During function invocation? → Check function logs with `vercel logs`\n├── HTTP 404? → Verify file exists in deployment: `vercel inspect`\n├── HTTP 500? → Unhandled exception in function code\n├── HTTP 504? → Function timeout — increase maxDuration\n└── HTTP 429? → Rate limited — implement retry with backoff\n```\n\n## Output\n- Error layer identified (build, runtime, or edge)\n- Root cause diagnosed using logs and inspection\n- Fix applied and verified via new deployment\n- Prevention measures documented\n\n## Error Handling\n| Error Code | HTTP | Layer | Quick Fix |\n|-----------|------|-------|-----------|\n| `BUILD_FAILED` | — | Build | Run build locally, check deps |\n| `FUNCTION_INVOCATION_FAILED` | 500 | Runtime | Check env vars, add try\u002Fcatch |\n| `FUNCTION_INVOCATION_TIMEOUT` | 504 | Runtime | Increase maxDuration in vercel.json |\n| `FUNCTION_THROTTLED` | 429 | Runtime | Reduce concurrency or upgrade plan |\n| `FUNCTION_PAYLOAD_TOO_LARGE` | 413 | Build | Reduce bundle size |\n| `NOT_FOUND` | 404 | Edge | Verify file paths and routes |\n| `EDGE_FUNCTION_INVOCATION_FAILED` | 500 | Edge | Remove Node.js APIs from edge code |\n| `NO_RESPONSE_FROM_FUNCTION` | 502 | Runtime | Return response from all code paths |\n\n## Resources\n- [Vercel Error Codes](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ferrors)\n- [Function Limitations](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Flimitations)\n- [Platform Limits](https:\u002F\u002Fvercel.com\u002Fdocs\u002Flimits)\n- [Vercel Status Page](https:\u002F\u002Fwww.vercel-status.com)\n- [Vercel Logs CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Flogs)\n\n## Next Steps\nFor detailed debug bundles, see `vercel-debug-bundle`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","vercel","debugging","errors","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Diagnose and fix common Vercel deployment and function errors.\nUse when encountering Vercel errors, debugging failed deployments,\nor troubleshooting serverless function issues.\nTrigger with phrases like \"vercel error\", \"fix vercel\",\n\"vercel not working\", \"debug vercel\", \"vercel 500\", \"vercel build failed\".\n","Read, Grep, Bash(vercel:*), Bash(curl:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--vercel-pack--vercel-common-errors",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill vercel-common-errors",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill vercel-common-errors",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill vercel-common-errors","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-common-errors\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[]]