[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7971Z5QXT16TPQFPFPQRQVA":3,"skill-same:01M7971Z5QXT16TPQFPFPQRQVA":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},"01M7971Z5QXT16TPQFPFPQRQVA","vercel-load-scale",null,"Load test and scale Vercel deployments with concurrency tuning and capacity planning.\nUse when running performance tests, planning for traffic spikes,\nor optimizing serverless function scaling on Vercel.\nTrigger with phrases like \"vercel load test\", \"vercel scale\",\n\"vercel performance test\", \"vercel capacity\", \"vercel benchmark\".","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-load-scale\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-load-scale\ndescription: |\n  Load test and scale Vercel deployments with concurrency tuning and capacity planning.\n  Use when running performance tests, planning for traffic spikes,\n  or optimizing serverless function scaling on Vercel.\n  Trigger with phrases like \"vercel load test\", \"vercel scale\",\n  \"vercel performance test\", \"vercel capacity\", \"vercel benchmark\".\nallowed-tools: Read, Write, Edit, Bash(npx:*), 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, testing, performance, scaling]\n---\n# Vercel Load & Scale\n\n## Overview\nLoad test Vercel deployments to identify scaling limits, cold start impact, and concurrency thresholds. Covers k6\u002Fautocannon test scripts, Vercel's auto-scaling model, Fluid Compute concurrency, and capacity planning.\n\n## Prerequisites\n- Load testing tool: k6, autocannon, or artillery\n- Test environment deployment (never load test production without approval)\n- Access to Vercel Analytics for monitoring during tests\n\n## Instructions\n\n### Step 1: Understand Vercel's Scaling Model\nVercel serverless functions scale automatically:\n\n| Behavior | Details |\n|----------|---------|\n| Scale-up | New function instances spawn on demand |\n| Scale-down | Idle instances shut down after ~15 minutes |\n| Cold starts | First request to a new instance pays initialization cost |\n| Concurrency | Each instance handles one request at a time (by default) |\n| Fluid Compute | Pro\u002FEnterprise: multiple requests per instance |\n\n**Concurrency limits by plan:**\n\n| Plan | Max Concurrent Functions |\n|------|------------------------|\n| Hobby | 10 |\n| Pro | 1,000 |\n| Enterprise | 100,000 |\n\n### Step 2: Basic Load Test with autocannon\n```bash\n# Install autocannon\nnpm install -g autocannon\n\n# Test with 50 concurrent connections for 30 seconds\nautocannon -c 50 -d 30 https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint\n\n# Output includes:\n# Latency: avg, p50, p99, max\n# Requests\u002Fsec: avg, min, max\n# Errors: timeouts, non-2xx responses\n```\n\n### Step 3: k6 Load Test Script\n```javascript\n\u002F\u002F load-test.js\nimport http from 'k6\u002Fhttp';\nimport { check, sleep } from 'k6';\nimport { Rate, Trend } from 'k6\u002Fmetrics';\n\nconst errorRate = new Rate('errors');\nconst coldStartRate = new Rate('cold_starts');\nconst latency = new Trend('api_latency');\n\nexport const options = {\n  stages: [\n    { duration: '1m', target: 10 },   \u002F\u002F Warm up\n    { duration: '3m', target: 50 },   \u002F\u002F Ramp to 50 users\n    { duration: '2m', target: 100 },  \u002F\u002F Peak load\n    { duration: '1m', target: 0 },    \u002F\u002F Cool down\n  ],\n  thresholds: {\n    http_req_duration: ['p(95)\u003C2000'],  \u002F\u002F P95 \u003C 2s\n    errors: ['rate\u003C0.01'],              \u002F\u002F Error rate \u003C 1%\n  },\n};\n\nexport default function () {\n  const res = http.get('https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint');\n\n  check(res, {\n    'status is 200': (r) => r.status === 200,\n    'latency \u003C 2s': (r) => r.timings.duration \u003C 2000,\n  });\n\n  errorRate.add(res.status !== 200);\n  latency.add(res.timings.duration);\n\n  \u002F\u002F Track cold starts if your API returns this header\n  if (res.headers['X-Cold-Start'] === 'true') {\n    coldStartRate.add(1);\n  }\n\n  sleep(1);\n}\n```\n\n```bash\n# Run the load test\nk6 run load-test.js\n\n# Run with output to JSON for analysis\nk6 run --out json=results.json load-test.js\n```\n\n### Step 4: Cold Start Stress Test\n```javascript\n\u002F\u002F cold-start-test.js — specifically test cold start behavior\nimport http from 'k6\u002Fhttp';\nimport { sleep } from 'k6';\n\nexport const options = {\n  scenarios: {\n    \u002F\u002F Scenario 1: Sustained load (warm instances)\n    sustained: {\n      executor: 'constant-arrival-rate',\n      rate: 10,\n      timeUnit: '1s',\n      duration: '2m',\n      preAllocatedVUs: 20,\n    },\n    \u002F\u002F Scenario 2: Spike (forces new cold starts)\n    spike: {\n      executor: 'ramping-arrival-rate',\n      startRate: 10,\n      timeUnit: '1s',\n      stages: [\n        { target: 200, duration: '10s' },  \u002F\u002F Sudden spike\n        { target: 10, duration: '1m' },     \u002F\u002F Return to normal\n      ],\n      preAllocatedVUs: 300,\n      startTime: '2m',  \u002F\u002F Start after sustained phase\n    },\n  },\n};\n\nexport default function () {\n  const res = http.get('https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint');\n  \u002F\u002F Log cold start timing for analysis\n}\n```\n\n### Step 5: Fluid Compute Concurrency Tuning\n```json\n\u002F\u002F vercel.json — configure concurrency for Fluid Compute (Pro\u002FEnterprise)\n{\n  \"functions\": {\n    \"api\u002Fhigh-throughput.ts\": {\n      \"memory\": 1024,\n      \"maxDuration\": 30,\n      \"concurrency\": 10\n    }\n  }\n}\n```\n\nWith Fluid Compute concurrency, a single function instance handles multiple requests:\n- Reduces cold starts (fewer instances needed)\n- Reduces cost (shared memory across requests)\n- Best for I\u002FO-bound functions (waiting on DB\u002FAPI calls)\n- Not ideal for CPU-bound functions (computation blocks other requests)\n\n### Step 6: Capacity Planning\n```\nCapacity Planning Formula:\n\n  Required instances = Peak RPS * Avg Response Time (seconds)\n\n  Example:\n  - Peak: 500 requests\u002Fsecond\n  - Avg response: 200ms (0.2s)\n  - Required: 500 * 0.2 = 100 concurrent instances\n\n  With Fluid Compute (concurrency=10):\n  - Required: 500 * 0.2 \u002F 10 = 10 concurrent instances\n\n  Plan check:\n  - Hobby (10 concurrent): NOT sufficient\n  - Pro (1000 concurrent): Sufficient with headroom\n```\n\n## Load Test Results Template\n\n```markdown\n## Load Test Report — [Date]\n\n### Configuration\n- Target: https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint\n- Tool: k6 v0.50\n- Duration: 7 minutes (ramp up → peak → cool down)\n- Peak concurrent users: 100\n\n### Results\n| Metric | Value |\n|--------|-------|\n| Total requests | 12,450 |\n| Success rate | 99.8% |\n| P50 latency | 45ms |\n| P95 latency | 320ms |\n| P99 latency | 1,200ms |\n| Max latency | 3,400ms |\n| Cold start % | 8% |\n| Avg cold start duration | 650ms |\n| Throttled (429) | 0 |\n\n### Recommendations\n1. Cold start: 650ms avg — consider Edge Functions for latency-critical paths\n2. P99 spike: caused by cold starts — Fluid Compute concurrency would help\n3. No throttling at 100 concurrent — Pro plan (1000 limit) is sufficient\n```\n\n## Output\n- Load test scripts for sustained and spike traffic scenarios\n- Cold start frequency and duration measured\n- Concurrency limits tested and validated\n- Capacity plan with scaling recommendations\n- Benchmark results documented\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `FUNCTION_THROTTLED` (429) | Exceeded concurrent limit | Reduce test concurrency or upgrade plan |\n| Vercel blocks load test | Not from approved IP | Contact Vercel support before load testing |\n| High P99 but low P50 | Cold starts on spikes | Use Fluid Compute concurrency or Edge Functions |\n| All requests timeout | Function region far from test origin | Set `regions` in vercel.json closer to test source |\n| Inconsistent results | Shared infrastructure variability | Run multiple test rounds, use median results |\n\n## Resources\n- [Vercel Function Limits](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Flimitations)\n- [Concurrency Scaling](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fconcurrency-scaling)\n- [Fluid Compute](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fusage-and-pricing)\n- [k6 Documentation](https:\u002F\u002Fk6.io\u002Fdocs\u002F)\n- [Vercel Load Testing Policy](https:\u002F\u002Fvercel.com\u002Fkb\u002Fguide\u002Fwhat-s-vercel-s-policy-regarding-load-testing-deployments)\n\n## Next Steps\nFor reliability patterns, see `vercel-reliability-patterns`.\n","# Vercel Load & Scale\n\n## Overview\nLoad test Vercel deployments to identify scaling limits, cold start impact, and concurrency thresholds. Covers k6\u002Fautocannon test scripts, Vercel's auto-scaling model, Fluid Compute concurrency, and capacity planning.\n\n## Prerequisites\n- Load testing tool: k6, autocannon, or artillery\n- Test environment deployment (never load test production without approval)\n- Access to Vercel Analytics for monitoring during tests\n\n## Instructions\n\n### Step 1: Understand Vercel's Scaling Model\nVercel serverless functions scale automatically:\n\n| Behavior | Details |\n|----------|---------|\n| Scale-up | New function instances spawn on demand |\n| Scale-down | Idle instances shut down after ~15 minutes |\n| Cold starts | First request to a new instance pays initialization cost |\n| Concurrency | Each instance handles one request at a time (by default) |\n| Fluid Compute | Pro\u002FEnterprise: multiple requests per instance |\n\n**Concurrency limits by plan:**\n\n| Plan | Max Concurrent Functions |\n|------|------------------------|\n| Hobby | 10 |\n| Pro | 1,000 |\n| Enterprise | 100,000 |\n\n### Step 2: Basic Load Test with autocannon\n```bash\n# Install autocannon\nnpm install -g autocannon\n\n# Test with 50 concurrent connections for 30 seconds\nautocannon -c 50 -d 30 https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint\n\n# Output includes:\n# Latency: avg, p50, p99, max\n# Requests\u002Fsec: avg, min, max\n# Errors: timeouts, non-2xx responses\n```\n\n### Step 3: k6 Load Test Script\n```javascript\n\u002F\u002F load-test.js\nimport http from 'k6\u002Fhttp';\nimport { check, sleep } from 'k6';\nimport { Rate, Trend } from 'k6\u002Fmetrics';\n\nconst errorRate = new Rate('errors');\nconst coldStartRate = new Rate('cold_starts');\nconst latency = new Trend('api_latency');\n\nexport const options = {\n  stages: [\n    { duration: '1m', target: 10 },   \u002F\u002F Warm up\n    { duration: '3m', target: 50 },   \u002F\u002F Ramp to 50 users\n    { duration: '2m', target: 100 },  \u002F\u002F Peak load\n    { duration: '1m', target: 0 },    \u002F\u002F Cool down\n  ],\n  thresholds: {\n    http_req_duration: ['p(95)\u003C2000'],  \u002F\u002F P95 \u003C 2s\n    errors: ['rate\u003C0.01'],              \u002F\u002F Error rate \u003C 1%\n  },\n};\n\nexport default function () {\n  const res = http.get('https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint');\n\n  check(res, {\n    'status is 200': (r) => r.status === 200,\n    'latency \u003C 2s': (r) => r.timings.duration \u003C 2000,\n  });\n\n  errorRate.add(res.status !== 200);\n  latency.add(res.timings.duration);\n\n  \u002F\u002F Track cold starts if your API returns this header\n  if (res.headers['X-Cold-Start'] === 'true') {\n    coldStartRate.add(1);\n  }\n\n  sleep(1);\n}\n```\n\n```bash\n# Run the load test\nk6 run load-test.js\n\n# Run with output to JSON for analysis\nk6 run --out json=results.json load-test.js\n```\n\n### Step 4: Cold Start Stress Test\n```javascript\n\u002F\u002F cold-start-test.js — specifically test cold start behavior\nimport http from 'k6\u002Fhttp';\nimport { sleep } from 'k6';\n\nexport const options = {\n  scenarios: {\n    \u002F\u002F Scenario 1: Sustained load (warm instances)\n    sustained: {\n      executor: 'constant-arrival-rate',\n      rate: 10,\n      timeUnit: '1s',\n      duration: '2m',\n      preAllocatedVUs: 20,\n    },\n    \u002F\u002F Scenario 2: Spike (forces new cold starts)\n    spike: {\n      executor: 'ramping-arrival-rate',\n      startRate: 10,\n      timeUnit: '1s',\n      stages: [\n        { target: 200, duration: '10s' },  \u002F\u002F Sudden spike\n        { target: 10, duration: '1m' },     \u002F\u002F Return to normal\n      ],\n      preAllocatedVUs: 300,\n      startTime: '2m',  \u002F\u002F Start after sustained phase\n    },\n  },\n};\n\nexport default function () {\n  const res = http.get('https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint');\n  \u002F\u002F Log cold start timing for analysis\n}\n```\n\n### Step 5: Fluid Compute Concurrency Tuning\n```json\n\u002F\u002F vercel.json — configure concurrency for Fluid Compute (Pro\u002FEnterprise)\n{\n  \"functions\": {\n    \"api\u002Fhigh-throughput.ts\": {\n      \"memory\": 1024,\n      \"maxDuration\": 30,\n      \"concurrency\": 10\n    }\n  }\n}\n```\n\nWith Fluid Compute concurrency, a single function instance handles multiple requests:\n- Reduces cold starts (fewer instances needed)\n- Reduces cost (shared memory across requests)\n- Best for I\u002FO-bound functions (waiting on DB\u002FAPI calls)\n- Not ideal for CPU-bound functions (computation blocks other requests)\n\n### Step 6: Capacity Planning\n```\nCapacity Planning Formula:\n\n  Required instances = Peak RPS * Avg Response Time (seconds)\n\n  Example:\n  - Peak: 500 requests\u002Fsecond\n  - Avg response: 200ms (0.2s)\n  - Required: 500 * 0.2 = 100 concurrent instances\n\n  With Fluid Compute (concurrency=10):\n  - Required: 500 * 0.2 \u002F 10 = 10 concurrent instances\n\n  Plan check:\n  - Hobby (10 concurrent): NOT sufficient\n  - Pro (1000 concurrent): Sufficient with headroom\n```\n\n## Load Test Results Template\n\n```markdown\n## Load Test Report — [Date]\n\n### Configuration\n- Target: https:\u002F\u002Fmy-app-preview.vercel.app\u002Fapi\u002Fendpoint\n- Tool: k6 v0.50\n- Duration: 7 minutes (ramp up → peak → cool down)\n- Peak concurrent users: 100\n\n### Results\n| Metric | Value |\n|--------|-------|\n| Total requests | 12,450 |\n| Success rate | 99.8% |\n| P50 latency | 45ms |\n| P95 latency | 320ms |\n| P99 latency | 1,200ms |\n| Max latency | 3,400ms |\n| Cold start % | 8% |\n| Avg cold start duration | 650ms |\n| Throttled (429) | 0 |\n\n### Recommendations\n1. Cold start: 650ms avg — consider Edge Functions for latency-critical paths\n2. P99 spike: caused by cold starts — Fluid Compute concurrency would help\n3. No throttling at 100 concurrent — Pro plan (1000 limit) is sufficient\n```\n\n## Output\n- Load test scripts for sustained and spike traffic scenarios\n- Cold start frequency and duration measured\n- Concurrency limits tested and validated\n- Capacity plan with scaling recommendations\n- Benchmark results documented\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `FUNCTION_THROTTLED` (429) | Exceeded concurrent limit | Reduce test concurrency or upgrade plan |\n| Vercel blocks load test | Not from approved IP | Contact Vercel support before load testing |\n| High P99 but low P50 | Cold starts on spikes | Use Fluid Compute concurrency or Edge Functions |\n| All requests timeout | Function region far from test origin | Set `regions` in vercel.json closer to test source |\n| Inconsistent results | Shared infrastructure variability | Run multiple test rounds, use median results |\n\n## Resources\n- [Vercel Function Limits](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Flimitations)\n- [Concurrency Scaling](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fconcurrency-scaling)\n- [Fluid Compute](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fusage-and-pricing)\n- [k6 Documentation](https:\u002F\u002Fk6.io\u002Fdocs\u002F)\n- [Vercel Load Testing Policy](https:\u002F\u002Fvercel.com\u002Fkb\u002Fguide\u002Fwhat-s-vercel-s-policy-regarding-load-testing-deployments)\n\n## Next Steps\nFor reliability patterns, see `vercel-reliability-patterns`.\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","testing","performance","scaling","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Load test and scale Vercel deployments with concurrency tuning and capacity planning.\nUse when running performance tests, planning for traffic spikes,\nor optimizing serverless function scaling on Vercel.\nTrigger with phrases like \"vercel load test\", \"vercel scale\",\n\"vercel performance test\", \"vercel capacity\", \"vercel benchmark\".\n","Read, Write, Edit, Bash(npx:*), Bash(vercel:*), Bash(curl:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--vercel-pack--vercel-load-scale",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-load-scale",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill vercel-load-scale",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill vercel-load-scale","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-load-scale\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",[],[]]