[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7970N5NHS57G7VJCS6Z9VCQ":3,"skill-same:01M7970N5NHS57G7VJCS6Z9VCQ":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},"01M7970N5NHS57G7VJCS6Z9VCQ","vercel-debug-bundle",null,"Collect Vercel debug evidence for support tickets and troubleshooting.\nUse when encountering persistent issues, preparing support tickets,\nor collecting diagnostic information for Vercel problems.\nTrigger with phrases like \"vercel debug\", \"vercel support bundle\",\n\"collect vercel logs\", \"vercel diagnostic\".","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-debug-bundle\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-debug-bundle\ndescription: |\n  Collect Vercel debug evidence for support tickets and troubleshooting.\n  Use when encountering persistent issues, preparing support tickets,\n  or collecting diagnostic information for Vercel problems.\n  Trigger with phrases like \"vercel debug\", \"vercel support bundle\",\n  \"collect vercel logs\", \"vercel diagnostic\".\nallowed-tools: Read, Bash(vercel:*), Bash(curl:*), Bash(tar:*), Bash(jq:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, vercel, debugging, support]\n---\n# Vercel Debug Bundle\n\n## Overview\nCollect a comprehensive debug bundle containing deployment state, function logs, environment configuration, and build output for Vercel support escalation or team troubleshooting.\n\n## Current State\n!`vercel --version 2>\u002Fdev\u002Fnull || echo 'Vercel CLI not installed'`\n!`node --version 2>\u002Fdev\u002Fnull || echo 'Node.js N\u002FA'`\n\n## Prerequisites\n- Vercel CLI installed and authenticated\n- Access to the affected deployment\n- `jq` for JSON processing (recommended)\n\n## Instructions\n\n### Step 1: Collect Deployment Information\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\nDEPLOY_URL=\"${1:-$(vercel ls --json 2>\u002Fdev\u002Fnull | jq -r '.[0].url')}\"\nBUNDLE_DIR=\"vercel-debug-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$BUNDLE_DIR\"\n\necho \"=== Collecting debug bundle for: $DEPLOY_URL ===\"\n\n# Deployment inspection\nvercel inspect \"$DEPLOY_URL\" > \"$BUNDLE_DIR\u002Finspect.txt\" 2>&1 || true\n\n# Deployment details via API\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002F$DEPLOY_URL\" \\\n  | jq '{uid, name, state, target, readyState, errorMessage, meta, regions}' \\\n  > \"$BUNDLE_DIR\u002Fdeployment.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 2: Collect Function Logs\n```bash\n# Recent function logs (last 100 entries)\nvercel logs \"$DEPLOY_URL\" --output=short --limit=100 \\\n  > \"$BUNDLE_DIR\u002Ffunction-logs.txt\" 2>&1 || true\n\n# Function logs via API with filtering\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv2\u002Fdeployments\u002F$DEPLOY_URL\u002Fevents?limit=100&direction=backward\" \\\n  | jq '.[] | {timestamp: .created, type, text}' \\\n  > \"$BUNDLE_DIR\u002Fevents.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 3: Collect Build Output\n```bash\n# Build logs\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002F$DEPLOY_URL\" \\\n  | jq '.build' > \"$BUNDLE_DIR\u002Fbuild-info.json\" 2>\u002Fdev\u002Fnull || true\n\n# List all functions in the deployment\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002F$DEPLOY_URL\" \\\n  | jq '.routes, .functions' > \"$BUNDLE_DIR\u002Froutes-functions.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 4: Collect Environment State (Redacted)\n```bash\n# Environment variable names only (no values)\nvercel env ls > \"$BUNDLE_DIR\u002Fenv-vars-list.txt\" 2>&1 || true\n\n# Project configuration (redacted)\nif [ -f \"vercel.json\" ]; then\n  cp vercel.json \"$BUNDLE_DIR\u002Fvercel.json\"\nfi\n\n# Package versions\nif [ -f \"package.json\" ]; then\n  jq '{name, version, dependencies, devDependencies, engines}' package.json \\\n    > \"$BUNDLE_DIR\u002Fpackage-summary.json\" 2>\u002Fdev\u002Fnull || true\nfi\n\n# Node.js and CLI versions\n{\n  echo \"node: $(node --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA')\"\n  echo \"npm: $(npm --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA')\"\n  echo \"vercel: $(vercel --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA')\"\n  echo \"os: $(uname -a)\"\n  echo \"date: $(date -u +%Y-%m-%dT%H:%M:%SZ)\"\n} > \"$BUNDLE_DIR\u002Fenvironment.txt\"\n```\n\n### Step 5: Check Vercel Status Page\n```bash\n# Vercel platform status\ncurl -s \"https:\u002F\u002Fwww.vercel-status.com\u002Fapi\u002Fv2\u002Fsummary.json\" \\\n  | jq '{status: .status.description, components: [.components[] | {name, status}]}' \\\n  > \"$BUNDLE_DIR\u002Fplatform-status.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 6: Package the Bundle\n```bash\n# Create archive — excludes secrets\ntar czf \"${BUNDLE_DIR}.tar.gz\" \"$BUNDLE_DIR\"\necho \"Debug bundle created: ${BUNDLE_DIR}.tar.gz\"\necho \"Contents:\"\nls -la \"$BUNDLE_DIR\"\u002F\n```\n\n## Bundle Contents Reference\n\n| File | Contents |\n|------|----------|\n| `inspect.txt` | Deployment inspection output |\n| `deployment.json` | Deployment state, target, errors |\n| `function-logs.txt` | Recent function invocation logs |\n| `events.json` | Deployment event timeline |\n| `build-info.json` | Build configuration and output |\n| `routes-functions.json` | Route and function mapping |\n| `env-vars-list.txt` | Environment variable names (no values) |\n| `vercel.json` | Project configuration |\n| `package-summary.json` | Dependencies and versions |\n| `environment.txt` | System info (Node, CLI, OS) |\n| `platform-status.json` | Vercel platform status at time of capture |\n\n## Support Ticket Template\n```\nSubject: [Project: my-app] FUNCTION_INVOCATION_TIMEOUT on \u002Fapi\u002Fendpoint\n\nEnvironment:\n- Plan: Pro\n- Framework: Next.js 14\n- Region: iad1\n- Node.js: 18.x\n\nIssue:\n[Describe the error, when it started, and the user impact]\n\nSteps to Reproduce:\n1. Deploy commit abc123\n2. Send POST to \u002Fapi\u002Fendpoint with body > 1MB\n3. Function times out after 60s\n\nExpected: 200 response within 5s\nActual: 504 after 60s\n\nDeployment URL: https:\u002F\u002Fmy-app-xxx.vercel.app\nDebug bundle: [attached]\n```\n\n## Output\n- `vercel-debug-YYYYMMDD-HHMMSS.tar.gz` archive\n- All secrets redacted (env var values never captured)\n- Platform status snapshot included\n- Ready to attach to Vercel support ticket\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `vercel inspect` fails | Deployment deleted or token expired | Use API directly with curl |\n| `jq: command not found` | jq not installed | `apt install jq` or `brew install jq` |\n| Empty function logs | Function not invoked or log retention expired | Check Observability tab in dashboard |\n| VERCEL_TOKEN not set | Not authenticated for API calls | Export token or run `vercel login` |\n\n## Resources\n- [Vercel Support Portal](https:\u002F\u002Fvercel.com\u002Fsupport)\n- [Vercel Logs CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Flogs)\n- [Vercel Inspect CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Finspect)\n- [Vercel Status Page](https:\u002F\u002Fwww.vercel-status.com)\n\n## Next Steps\nFor rate limit issues, see `vercel-rate-limits`.\n","# Vercel Debug Bundle\n\n## Overview\nCollect a comprehensive debug bundle containing deployment state, function logs, environment configuration, and build output for Vercel support escalation or team troubleshooting.\n\n## Current State\n!`vercel --version 2>\u002Fdev\u002Fnull || echo 'Vercel CLI not installed'`\n!`node --version 2>\u002Fdev\u002Fnull || echo 'Node.js N\u002FA'`\n\n## Prerequisites\n- Vercel CLI installed and authenticated\n- Access to the affected deployment\n- `jq` for JSON processing (recommended)\n\n## Instructions\n\n### Step 1: Collect Deployment Information\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\nDEPLOY_URL=\"${1:-$(vercel ls --json 2>\u002Fdev\u002Fnull | jq -r '.[0].url')}\"\nBUNDLE_DIR=\"vercel-debug-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$BUNDLE_DIR\"\n\necho \"=== Collecting debug bundle for: $DEPLOY_URL ===\"\n\n# Deployment inspection\nvercel inspect \"$DEPLOY_URL\" > \"$BUNDLE_DIR\u002Finspect.txt\" 2>&1 || true\n\n# Deployment details via API\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002F$DEPLOY_URL\" \\\n  | jq '{uid, name, state, target, readyState, errorMessage, meta, regions}' \\\n  > \"$BUNDLE_DIR\u002Fdeployment.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 2: Collect Function Logs\n```bash\n# Recent function logs (last 100 entries)\nvercel logs \"$DEPLOY_URL\" --output=short --limit=100 \\\n  > \"$BUNDLE_DIR\u002Ffunction-logs.txt\" 2>&1 || true\n\n# Function logs via API with filtering\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv2\u002Fdeployments\u002F$DEPLOY_URL\u002Fevents?limit=100&direction=backward\" \\\n  | jq '.[] | {timestamp: .created, type, text}' \\\n  > \"$BUNDLE_DIR\u002Fevents.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 3: Collect Build Output\n```bash\n# Build logs\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002F$DEPLOY_URL\" \\\n  | jq '.build' > \"$BUNDLE_DIR\u002Fbuild-info.json\" 2>\u002Fdev\u002Fnull || true\n\n# List all functions in the deployment\ncurl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  \"https:\u002F\u002Fapi.vercel.com\u002Fv13\u002Fdeployments\u002F$DEPLOY_URL\" \\\n  | jq '.routes, .functions' > \"$BUNDLE_DIR\u002Froutes-functions.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 4: Collect Environment State (Redacted)\n```bash\n# Environment variable names only (no values)\nvercel env ls > \"$BUNDLE_DIR\u002Fenv-vars-list.txt\" 2>&1 || true\n\n# Project configuration (redacted)\nif [ -f \"vercel.json\" ]; then\n  cp vercel.json \"$BUNDLE_DIR\u002Fvercel.json\"\nfi\n\n# Package versions\nif [ -f \"package.json\" ]; then\n  jq '{name, version, dependencies, devDependencies, engines}' package.json \\\n    > \"$BUNDLE_DIR\u002Fpackage-summary.json\" 2>\u002Fdev\u002Fnull || true\nfi\n\n# Node.js and CLI versions\n{\n  echo \"node: $(node --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA')\"\n  echo \"npm: $(npm --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA')\"\n  echo \"vercel: $(vercel --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA')\"\n  echo \"os: $(uname -a)\"\n  echo \"date: $(date -u +%Y-%m-%dT%H:%M:%SZ)\"\n} > \"$BUNDLE_DIR\u002Fenvironment.txt\"\n```\n\n### Step 5: Check Vercel Status Page\n```bash\n# Vercel platform status\ncurl -s \"https:\u002F\u002Fwww.vercel-status.com\u002Fapi\u002Fv2\u002Fsummary.json\" \\\n  | jq '{status: .status.description, components: [.components[] | {name, status}]}' \\\n  > \"$BUNDLE_DIR\u002Fplatform-status.json\" 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 6: Package the Bundle\n```bash\n# Create archive — excludes secrets\ntar czf \"${BUNDLE_DIR}.tar.gz\" \"$BUNDLE_DIR\"\necho \"Debug bundle created: ${BUNDLE_DIR}.tar.gz\"\necho \"Contents:\"\nls -la \"$BUNDLE_DIR\"\u002F\n```\n\n## Bundle Contents Reference\n\n| File | Contents |\n|------|----------|\n| `inspect.txt` | Deployment inspection output |\n| `deployment.json` | Deployment state, target, errors |\n| `function-logs.txt` | Recent function invocation logs |\n| `events.json` | Deployment event timeline |\n| `build-info.json` | Build configuration and output |\n| `routes-functions.json` | Route and function mapping |\n| `env-vars-list.txt` | Environment variable names (no values) |\n| `vercel.json` | Project configuration |\n| `package-summary.json` | Dependencies and versions |\n| `environment.txt` | System info (Node, CLI, OS) |\n| `platform-status.json` | Vercel platform status at time of capture |\n\n## Support Ticket Template\n```\nSubject: [Project: my-app] FUNCTION_INVOCATION_TIMEOUT on \u002Fapi\u002Fendpoint\n\nEnvironment:\n- Plan: Pro\n- Framework: Next.js 14\n- Region: iad1\n- Node.js: 18.x\n\nIssue:\n[Describe the error, when it started, and the user impact]\n\nSteps to Reproduce:\n1. Deploy commit abc123\n2. Send POST to \u002Fapi\u002Fendpoint with body > 1MB\n3. Function times out after 60s\n\nExpected: 200 response within 5s\nActual: 504 after 60s\n\nDeployment URL: https:\u002F\u002Fmy-app-xxx.vercel.app\nDebug bundle: [attached]\n```\n\n## Output\n- `vercel-debug-YYYYMMDD-HHMMSS.tar.gz` archive\n- All secrets redacted (env var values never captured)\n- Platform status snapshot included\n- Ready to attach to Vercel support ticket\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `vercel inspect` fails | Deployment deleted or token expired | Use API directly with curl |\n| `jq: command not found` | jq not installed | `apt install jq` or `brew install jq` |\n| Empty function logs | Function not invoked or log retention expired | Check Observability tab in dashboard |\n| VERCEL_TOKEN not set | Not authenticated for API calls | Export token or run `vercel login` |\n\n## Resources\n- [Vercel Support Portal](https:\u002F\u002Fvercel.com\u002Fsupport)\n- [Vercel Logs CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Flogs)\n- [Vercel Inspect CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Finspect)\n- [Vercel Status Page](https:\u002F\u002Fwww.vercel-status.com)\n\n## Next Steps\nFor rate limit issues, see `vercel-rate-limits`.\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","support","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Collect Vercel debug evidence for support tickets and troubleshooting.\nUse when encountering persistent issues, preparing support tickets,\nor collecting diagnostic information for Vercel problems.\nTrigger with phrases like \"vercel debug\", \"vercel support bundle\",\n\"collect vercel logs\", \"vercel diagnostic\".\n","Read, Bash(vercel:*), Bash(curl:*), Bash(tar:*), Bash(jq:*), Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--vercel-pack--vercel-debug-bundle",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-debug-bundle",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill vercel-debug-bundle",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill vercel-debug-bundle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-debug-bundle\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",[],[]]