[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZXMWFT00FB7XSRW40MJDP":3,"skill-same:01M78ZXMWFT00FB7XSRW40MJDP":55},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M78ZXMWFT00FB7XSRW40MJDP","figma-advanced-troubleshooting",null,"Deep debugging for Figma API issues: network analysis, response inspection, and support escalation.\nUse when standard troubleshooting fails, diagnosing intermittent failures,\nor preparing detailed evidence for Figma support.\nTrigger with phrases like \"figma hard bug\", \"figma mystery error\",\n\"figma deep debug\", \"figma intermittent failure\", \"figma support ticket\".","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--figma-pack--figma-advanced-troubleshooting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: figma-advanced-troubleshooting\ndescription: |\n  Deep debugging for Figma API issues: network analysis, response inspection, and support escalation.\n  Use when standard troubleshooting fails, diagnosing intermittent failures,\n  or preparing detailed evidence for Figma support.\n  Trigger with phrases like \"figma hard bug\", \"figma mystery error\",\n  \"figma deep debug\", \"figma intermittent failure\", \"figma support ticket\".\nallowed-tools: Read, Grep, Bash(curl:*), Bash(node:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, figma]\ncompatible-with: claude-code\n---\n\n# Figma Advanced Troubleshooting\n\n## Overview\nDeep debugging techniques for complex Figma REST API issues that resist standard error handling: intermittent failures, unexpected response shapes, rate limit edge cases, and large file timeouts.\n\n## Prerequisites\n- Access to application logs\n- `curl` with verbose mode for network inspection\n- Figma API credentials for testing\n\n## Instructions\n\n### Step 1: Verbose Request Inspection\n```bash\n# Full HTTP request\u002Fresponse trace for a Figma API call\ncurl -v -H \"X-Figma-Token: ${FIGMA_PAT}\" \\\n  \"https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${FIGMA_FILE_KEY}?depth=1\" 2>&1 \\\n  | tee figma-debug-trace.txt\n\n# Extract key diagnostic info:\n# - TLS version and cipher\n# - Response status and headers\n# - Timing breakdown\ncurl -w \"\nDNS:        %{time_namelookup}s\nConnect:    %{time_connect}s\nTLS:        %{time_appconnect}s\nTTFB:       %{time_starttransfer}s\nTotal:      %{time_total}s\nSize:       %{size_download} bytes\nStatus:     %{http_code}\n\" -s -o \u002Fdev\u002Fnull \\\n  -H \"X-Figma-Token: ${FIGMA_PAT}\" \\\n  \"https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${FIGMA_FILE_KEY}?depth=1\"\n```\n\n### Step 2: Response Shape Validation\n```typescript\n\u002F\u002F Figma API responses can be unexpectedly shaped when:\n\u002F\u002F - File is empty or newly created\n\u002F\u002F - Nodes have been deleted between requests\n\u002F\u002F - Plugin data is corrupted\n\nfunction validateFileResponse(data: any): string[] {\n  const issues: string[] = [];\n\n  if (!data.document) issues.push('Missing document root');\n  if (!data.document?.children?.length) issues.push('Document has no pages');\n  if (typeof data.name !== 'string') issues.push('Missing file name');\n  if (!data.version) issues.push('Missing version field');\n\n  \u002F\u002F Check for null nodes (deleted between list and fetch)\n  if (data.nodes) {\n    for (const [id, node] of Object.entries(data.nodes)) {\n      if (node === null) issues.push(`Null node: ${id} (deleted or invisible)`);\n    }\n  }\n\n  \u002F\u002F Check images response for null renders\n  if (data.images) {\n    for (const [id, url] of Object.entries(data.images)) {\n      if (url === null) issues.push(`Image render failed for node: ${id}`);\n    }\n  }\n\n  return issues;\n}\n```\n\n### Step 3: Rate Limit Edge Cases\n```typescript\n\u002F\u002F Problem: Figma rate limits are per-user, per-minute, but the exact\n\u002F\u002F limit is not published and varies by plan tier and seat type.\n\n\u002F\u002F Diagnostic: measure your actual limit by counting successful requests\nasync function measureRateLimit(token: string): Promise\u003C{\n  requestsMade: number;\n  firstRateLimitAt: number | null;\n  retryAfter: number | null;\n}> {\n  let count = 0;\n  let rateLimitAt: number | null = null;\n  let retryAfter: number | null = null;\n\n  \u002F\u002F Make requests until rate limited (use a read-only endpoint)\n  while (count \u003C 200) {\n    const res = await fetch('https:\u002F\u002Fapi.figma.com\u002Fv1\u002Fme', {\n      headers: { 'X-Figma-Token': token },\n    });\n\n    if (res.status === 429) {\n      rateLimitAt = count;\n      retryAfter = parseInt(res.headers.get('Retry-After') || '0');\n      break;\n    }\n\n    count++;\n    \u002F\u002F Small delay to avoid instant burst\n    await new Promise(r => setTimeout(r, 100));\n  }\n\n  return { requestsMade: count, firstRateLimitAt: rateLimitAt, retryAfter };\n}\n```\n\n### Step 4: Large File Debugging\n```typescript\n\u002F\u002F Large Figma files (1000+ components) can cause:\n\u002F\u002F - Response timeouts (>30s)\n\u002F\u002F - Memory issues (100+ MB JSON)\n\u002F\u002F - Rate limits from repeated retries\n\n\u002F\u002F Strategy: chunk the file by page\nasync function fetchLargeFileSafely(fileKey: string, token: string) {\n  \u002F\u002F 1. Get file metadata with depth=1 (just pages, not children)\n  const meta = await fetch(\n    `https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${fileKey}?depth=1`,\n    { headers: { 'X-Figma-Token': token } }\n  ).then(r => r.json());\n\n  console.log(`File: ${meta.name}, Pages: ${meta.document.children.length}`);\n\n  \u002F\u002F 2. Fetch each page's content individually\n  const results = [];\n  for (const page of meta.document.children) {\n    console.log(`Fetching page: ${page.name} (${page.id})`);\n\n    const pageData = await fetch(\n      `https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${fileKey}\u002Fnodes?ids=${page.id}`,\n      { headers: { 'X-Figma-Token': token } }\n    ).then(r => r.json());\n\n    results.push({ pageId: page.id, pageName: page.name, data: pageData });\n\n    \u002F\u002F Respect rate limits between page fetches\n    await new Promise(r => setTimeout(r, 500));\n  }\n\n  return results;\n}\n```\n\n### Step 5: Support Escalation Template\n```markdown\n## Figma API Support Request\n\n**Account email:** [your-email]\n**Plan tier:** [Starter\u002FProfessional\u002FOrganization\u002FEnterprise]\n**Endpoint:** [e.g., GET \u002Fv1\u002Ffiles\u002F:key]\n**File key:** [file key, not sensitive]\n\n### Issue Description\n[1-2 sentences describing the problem]\n\n### Reproduction Steps\n1. Call `GET https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002FFILE_KEY?depth=1`\n2. Observe: [expected vs actual behavior]\n\n### Diagnostic Data\n- HTTP status: [status code]\n- Response headers: [relevant headers, especially rate limit]\n- Response time: [from curl timing]\n- Frequency: [every time \u002F intermittent \u002F specific conditions]\n\n### Request\u002FResponse (redacted)\n```\ncurl -v -H \"X-Figma-Token: [REDACTED]\" \\\n  \"https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002FFILE_KEY?depth=1\"\n\nHTTP\u002F2 [status]\nx-figma-rate-limit-type: [value]\nretry-after: [value]\n```\n\n### Environment\n- Node.js: [version]\n- OS: [os]\n- Region: [your server region]\n- Behind proxy: [yes\u002Fno]\n```\n\n## Output\n- Verbose request\u002Fresponse traces captured\n- Response shape issues identified\n- Rate limit behavior measured\n- Large file handled with page-level chunking\n- Support ticket prepared with diagnostic data\n\n## Error Handling\n| Issue | Diagnostic | Solution |\n|-------|-----------|----------|\n| Intermittent 500s | Track frequency and timing | Log every request; report pattern to Figma |\n| Slow responses | curl timing breakdown | Check if DNS\u002FTLS is the bottleneck |\n| Null image renders | Validate node visibility | Check node opacity and visibility in Figma |\n| Memory crash | Large file JSON | Use `depth=1` + per-page `\u002Fnodes` calls |\n\n## Resources\n- [Figma Developer Forum](https:\u002F\u002Fforum.figma.com\u002F)\n- [Figma Support](https:\u002F\u002Fhelp.figma.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew)\n- [Figma Status Page](https:\u002F\u002Fstatus.figma.com)\n\n## Next Steps\nFor load testing, see `figma-load-scale`.\n","# Figma Advanced Troubleshooting\n\n## Overview\nDeep debugging techniques for complex Figma REST API issues that resist standard error handling: intermittent failures, unexpected response shapes, rate limit edge cases, and large file timeouts.\n\n## Prerequisites\n- Access to application logs\n- `curl` with verbose mode for network inspection\n- Figma API credentials for testing\n\n## Instructions\n\n### Step 1: Verbose Request Inspection\n```bash\n# Full HTTP request\u002Fresponse trace for a Figma API call\ncurl -v -H \"X-Figma-Token: ${FIGMA_PAT}\" \\\n  \"https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${FIGMA_FILE_KEY}?depth=1\" 2>&1 \\\n  | tee figma-debug-trace.txt\n\n# Extract key diagnostic info:\n# - TLS version and cipher\n# - Response status and headers\n# - Timing breakdown\ncurl -w \"\nDNS:        %{time_namelookup}s\nConnect:    %{time_connect}s\nTLS:        %{time_appconnect}s\nTTFB:       %{time_starttransfer}s\nTotal:      %{time_total}s\nSize:       %{size_download} bytes\nStatus:     %{http_code}\n\" -s -o \u002Fdev\u002Fnull \\\n  -H \"X-Figma-Token: ${FIGMA_PAT}\" \\\n  \"https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${FIGMA_FILE_KEY}?depth=1\"\n```\n\n### Step 2: Response Shape Validation\n```typescript\n\u002F\u002F Figma API responses can be unexpectedly shaped when:\n\u002F\u002F - File is empty or newly created\n\u002F\u002F - Nodes have been deleted between requests\n\u002F\u002F - Plugin data is corrupted\n\nfunction validateFileResponse(data: any): string[] {\n  const issues: string[] = [];\n\n  if (!data.document) issues.push('Missing document root');\n  if (!data.document?.children?.length) issues.push('Document has no pages');\n  if (typeof data.name !== 'string') issues.push('Missing file name');\n  if (!data.version) issues.push('Missing version field');\n\n  \u002F\u002F Check for null nodes (deleted between list and fetch)\n  if (data.nodes) {\n    for (const [id, node] of Object.entries(data.nodes)) {\n      if (node === null) issues.push(`Null node: ${id} (deleted or invisible)`);\n    }\n  }\n\n  \u002F\u002F Check images response for null renders\n  if (data.images) {\n    for (const [id, url] of Object.entries(data.images)) {\n      if (url === null) issues.push(`Image render failed for node: ${id}`);\n    }\n  }\n\n  return issues;\n}\n```\n\n### Step 3: Rate Limit Edge Cases\n```typescript\n\u002F\u002F Problem: Figma rate limits are per-user, per-minute, but the exact\n\u002F\u002F limit is not published and varies by plan tier and seat type.\n\n\u002F\u002F Diagnostic: measure your actual limit by counting successful requests\nasync function measureRateLimit(token: string): Promise\u003C{\n  requestsMade: number;\n  firstRateLimitAt: number | null;\n  retryAfter: number | null;\n}> {\n  let count = 0;\n  let rateLimitAt: number | null = null;\n  let retryAfter: number | null = null;\n\n  \u002F\u002F Make requests until rate limited (use a read-only endpoint)\n  while (count \u003C 200) {\n    const res = await fetch('https:\u002F\u002Fapi.figma.com\u002Fv1\u002Fme', {\n      headers: { 'X-Figma-Token': token },\n    });\n\n    if (res.status === 429) {\n      rateLimitAt = count;\n      retryAfter = parseInt(res.headers.get('Retry-After') || '0');\n      break;\n    }\n\n    count++;\n    \u002F\u002F Small delay to avoid instant burst\n    await new Promise(r => setTimeout(r, 100));\n  }\n\n  return { requestsMade: count, firstRateLimitAt: rateLimitAt, retryAfter };\n}\n```\n\n### Step 4: Large File Debugging\n```typescript\n\u002F\u002F Large Figma files (1000+ components) can cause:\n\u002F\u002F - Response timeouts (>30s)\n\u002F\u002F - Memory issues (100+ MB JSON)\n\u002F\u002F - Rate limits from repeated retries\n\n\u002F\u002F Strategy: chunk the file by page\nasync function fetchLargeFileSafely(fileKey: string, token: string) {\n  \u002F\u002F 1. Get file metadata with depth=1 (just pages, not children)\n  const meta = await fetch(\n    `https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${fileKey}?depth=1`,\n    { headers: { 'X-Figma-Token': token } }\n  ).then(r => r.json());\n\n  console.log(`File: ${meta.name}, Pages: ${meta.document.children.length}`);\n\n  \u002F\u002F 2. Fetch each page's content individually\n  const results = [];\n  for (const page of meta.document.children) {\n    console.log(`Fetching page: ${page.name} (${page.id})`);\n\n    const pageData = await fetch(\n      `https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002F${fileKey}\u002Fnodes?ids=${page.id}`,\n      { headers: { 'X-Figma-Token': token } }\n    ).then(r => r.json());\n\n    results.push({ pageId: page.id, pageName: page.name, data: pageData });\n\n    \u002F\u002F Respect rate limits between page fetches\n    await new Promise(r => setTimeout(r, 500));\n  }\n\n  return results;\n}\n```\n\n### Step 5: Support Escalation Template\n```markdown\n## Figma API Support Request\n\n**Account email:** [your-email]\n**Plan tier:** [Starter\u002FProfessional\u002FOrganization\u002FEnterprise]\n**Endpoint:** [e.g., GET \u002Fv1\u002Ffiles\u002F:key]\n**File key:** [file key, not sensitive]\n\n### Issue Description\n[1-2 sentences describing the problem]\n\n### Reproduction Steps\n1. Call `GET https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002FFILE_KEY?depth=1`\n2. Observe: [expected vs actual behavior]\n\n### Diagnostic Data\n- HTTP status: [status code]\n- Response headers: [relevant headers, especially rate limit]\n- Response time: [from curl timing]\n- Frequency: [every time \u002F intermittent \u002F specific conditions]\n\n### Request\u002FResponse (redacted)\n```\ncurl -v -H \"X-Figma-Token: [REDACTED]\" \\\n  \"https:\u002F\u002Fapi.figma.com\u002Fv1\u002Ffiles\u002FFILE_KEY?depth=1\"\n\nHTTP\u002F2 [status]\nx-figma-rate-limit-type: [value]\nretry-after: [value]\n```\n\n### Environment\n- Node.js: [version]\n- OS: [os]\n- Region: [your server region]\n- Behind proxy: [yes\u002Fno]\n```\n\n## Output\n- Verbose request\u002Fresponse traces captured\n- Response shape issues identified\n- Rate limit behavior measured\n- Large file handled with page-level chunking\n- Support ticket prepared with diagnostic data\n\n## Error Handling\n| Issue | Diagnostic | Solution |\n|-------|-----------|----------|\n| Intermittent 500s | Track frequency and timing | Log every request; report pattern to Figma |\n| Slow responses | curl timing breakdown | Check if DNS\u002FTLS is the bottleneck |\n| Null image renders | Validate node visibility | Check node opacity and visibility in Figma |\n| Memory crash | Large file JSON | Use `depth=1` + per-page `\u002Fnodes` calls |\n\n## Resources\n- [Figma Developer Forum](https:\u002F\u002Fforum.figma.com\u002F)\n- [Figma Support](https:\u002F\u002Fhelp.figma.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew)\n- [Figma Status Page](https:\u002F\u002Fstatus.figma.com)\n\n## Next Steps\nFor load testing, see `figma-load-scale`.\n",{"name":5,"tags":24,"author":27,"license":15,"version":28,"description":29,"allowed-tools":30,"compatible-with":31},[25,26],"saas","figma","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Deep debugging for Figma API issues: network analysis, response inspection, and support escalation.\nUse when standard troubleshooting fails, diagnosing intermittent failures,\nor preparing detailed evidence for Figma support.\nTrigger with phrases like \"figma hard bug\", \"figma mystery error\",\n\"figma deep debug\", \"figma intermittent failure\", \"figma support ticket\".\n","Read, Grep, Bash(curl:*), Bash(node:*)","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--figma-pack--figma-advanced-troubleshooting",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill figma-advanced-troubleshooting",{"tool":47,"command":48},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill figma-advanced-troubleshooting",{"tool":50,"command":51},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill figma-advanced-troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--figma-pack--figma-advanced-troubleshooting\u002FSKILL.md",true,[],[56,63,70,77,84,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]