[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZSEWN033WVM92KGJSF9VJ":3,"skill-same:01M78ZSEWN033WVM92KGJSF9VJ":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},"01M78ZSEWN033WVM92KGJSF9VJ","exa-known-pitfalls",null,"Identify and avoid Exa anti-patterns and common integration mistakes.\nUse when reviewing Exa code, onboarding new developers,\nor auditing existing Exa integrations for correctness.\nTrigger with phrases like \"exa mistakes\", \"exa anti-patterns\",\n\"exa pitfalls\", \"exa what not to do\", \"exa code review\".","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--exa-pack--exa-known-pitfalls\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: exa-known-pitfalls\ndescription: |\n  Identify and avoid Exa anti-patterns and common integration mistakes.\n  Use when reviewing Exa code, onboarding new developers,\n  or auditing existing Exa integrations for correctness.\n  Trigger with phrases like \"exa mistakes\", \"exa anti-patterns\",\n  \"exa pitfalls\", \"exa what not to do\", \"exa code review\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, exa, audit, best-practices]\n---\n# Exa Known Pitfalls\n\n## Overview\nReal gotchas when integrating Exa's neural search API. Exa uses embeddings-based search rather than keyword matching, which creates a different class of failure modes than traditional search APIs. This skill covers the top pitfalls with wrong\u002Fright examples.\n\n## Pitfall 1: Keyword-Style Queries\n\nExa's neural search interprets natural language semantically. Boolean operators and keyword syntax degrade results.\n\n```typescript\nimport Exa from \"exa-js\";\nconst exa = new Exa(process.env.EXA_API_KEY);\n\n\u002F\u002F BAD: keyword\u002Fboolean style — Exa ignores AND\u002FOR\nconst bad = await exa.search(\n  \"python AND machine learning OR deep learning 2024\"\n);\n\n\u002F\u002F GOOD: natural language statement\nconst good = await exa.search(\n  \"recent tutorials on building ML models with Python\",\n  { type: \"neural\", numResults: 10 }\n);\n```\n\n## Pitfall 2: Wrong Search Type\n\nUsing neural search for exact lookups (URLs, names) or keyword search for conceptual queries silently degrades quality.\n\n```typescript\n\u002F\u002F BAD: neural search for a specific URL\u002Fidentifier\nconst bad = await exa.search(\"arxiv.org\u002Fabs\u002F2301.00001\", { type: \"neural\" });\n\n\u002F\u002F GOOD: keyword for exact terms, neural for concepts\nconst exactMatch = await exa.search(\"arxiv.org\u002Fabs\u002F2301.00001\", {\n  type: \"keyword\",\n});\nconst conceptual = await exa.search(\n  \"transformer architecture improvements for long context\",\n  { type: \"neural\" }\n);\n```\n\n## Pitfall 3: Expecting Content from search()\n\n`search()` returns metadata only (URL, title, score). Content requires `searchAndContents()` or `getContents()`.\n\n```typescript\n\u002F\u002F BAD: accessing .text from search() — it's undefined\nconst results = await exa.search(\"AI safety research\");\nconst text = results.results[0].text;  \u002F\u002F undefined!\n\n\u002F\u002F GOOD: use searchAndContents for text\u002Fhighlights\nconst withContent = await exa.searchAndContents(\"AI safety research\", {\n  numResults: 5,\n  text: { maxCharacters: 2000 },\n  highlights: { maxCharacters: 500 },\n});\nconsole.log(withContent.results[0].text);       \u002F\u002F actual content\nconsole.log(withContent.results[0].highlights);  \u002F\u002F key excerpts\n```\n\n## Pitfall 4: Narrow Date Filters Return Empty\n\nDate filters silently exclude results. A single-day window often returns nothing without error.\n\n```typescript\n\u002F\u002F BAD: too narrow, likely returns empty array\nconst bad = await exa.search(\"AI news\", {\n  startPublishedDate: \"2025-03-15T00:00:00.000Z\",\n  endPublishedDate: \"2025-03-15T23:59:59.000Z\",\n});\n\n\u002F\u002F GOOD: reasonable window with fallback\nlet results = await exa.search(\"AI news\", {\n  startPublishedDate: \"2025-03-01T00:00:00.000Z\",\n  endPublishedDate: \"2025-03-31T23:59:59.000Z\",\n  numResults: 10,\n});\n\u002F\u002F Fallback if no results\nif (results.results.length === 0) {\n  results = await exa.search(\"AI news\", { numResults: 10 });\n}\n```\n\n## Pitfall 5: findSimilar Takes a URL, Not a Query\n\n`findSimilar` expects a URL as its first argument. Passing a query string gives meaningless results.\n\n```typescript\n\u002F\u002F BAD: passing a query string to findSimilar\nconst bad = await exa.findSimilar(\"machine learning research papers\");\n\n\u002F\u002F GOOD: pass a URL — findSimilar finds pages semantically similar to it\nconst good = await exa.findSimilar(\"https:\u002F\u002Farxiv.org\u002Fabs\u002F2301.00001\", {\n  numResults: 10,\n  excludeSourceDomain: true,\n});\n```\n\n## Pitfall 6: Date Filters with company\u002Fpeople Categories\n\nThe `company` and `people` categories do NOT support date filters. Using them returns a 400 error.\n\n```typescript\n\u002F\u002F BAD: date filter with company category → 400 error\nconst bad = await exa.search(\"AI startups\", {\n  category: \"company\",\n  startPublishedDate: \"2024-01-01T00:00:00.000Z\",  \u002F\u002F not supported!\n});\n\n\u002F\u002F GOOD: company search without date filters\nconst good = await exa.search(\"AI startups\", {\n  category: \"company\",\n  numResults: 10,\n});\n```\n\n## Pitfall 7: Not Limiting Content Size\n\nRequesting full text without `maxCharacters` can return massive payloads, increasing latency and cost.\n\n```typescript\n\u002F\u002F BAD: unlimited text retrieval\nconst bad = await exa.searchAndContents(\"topic\", {\n  numResults: 20,\n  text: true,  \u002F\u002F could return megabytes of content\n});\n\n\u002F\u002F GOOD: limit content size\nconst good = await exa.searchAndContents(\"topic\", {\n  numResults: 10,\n  text: { maxCharacters: 2000 },  \u002F\u002F cap at 2000 chars per result\n  highlights: { maxCharacters: 500 },\n});\n```\n\n## Pitfall 8: Creating New Client Per Request\n\nEach `new Exa()` call creates a new HTTP client. Reuse a singleton for connection pooling.\n\n```typescript\n\u002F\u002F BAD: new client every request (in a route handler)\napp.get(\"\u002Fsearch\", async (req, res) => {\n  const exa = new Exa(process.env.EXA_API_KEY);  \u002F\u002F wasteful!\n  const results = await exa.search(req.query.q);\n  res.json(results);\n});\n\n\u002F\u002F GOOD: singleton client\nconst exa = new Exa(process.env.EXA_API_KEY);\napp.get(\"\u002Fsearch\", async (req, res) => {\n  const results = await exa.search(req.query.q);\n  res.json(results);\n});\n```\n\n## Pitfall 9: Ignoring the requestId in Errors\n\nExa error responses include `requestId` for support debugging. Always log it.\n\n```typescript\n\u002F\u002F BAD: generic error handling\ntry {\n  await exa.search(\"query\");\n} catch (err) {\n  console.error(\"Search failed\");  \u002F\u002F loses diagnostic info\n}\n\n\u002F\u002F GOOD: capture requestId\ntry {\n  await exa.search(\"query\");\n} catch (err: any) {\n  console.error(\"Search failed:\", {\n    status: err.status,\n    message: err.message,\n    requestId: err.requestId,  \u002F\u002F include when contacting support\n    tag: err.error_tag,\n  });\n}\n```\n\n## Quick Review Checklist\n- [ ] Queries are natural language, not keyword\u002Fboolean syntax\n- [ ] Search type matches the query intent (neural vs keyword)\n- [ ] Using `searchAndContents` when page content is needed\n- [ ] Date filter windows are wide enough (7+ days)\n- [ ] `findSimilar` receives URLs, not query strings\n- [ ] No date filters on `company` or `people` categories\n- [ ] `maxCharacters` set on text and highlights\n- [ ] Exa client is a singleton, not created per request\n- [ ] Error handling captures `requestId`\n\n## Resources\n- [Exa Search Reference](https:\u002F\u002Fdocs.exa.ai\u002Freference\u002Fsearch)\n- [Exa Error Codes](https:\u002F\u002Fdocs.exa.ai\u002Freference\u002Ferror-codes)\n- [Exa Contents Retrieval](https:\u002F\u002Fdocs.exa.ai\u002Freference\u002Fcontents-retrieval)\n\n## Next Steps\nFor SDK patterns, see `exa-sdk-patterns`. For common errors, see `exa-common-errors`.\n","# Exa Known Pitfalls\n\n## Overview\nReal gotchas when integrating Exa's neural search API. Exa uses embeddings-based search rather than keyword matching, which creates a different class of failure modes than traditional search APIs. This skill covers the top pitfalls with wrong\u002Fright examples.\n\n## Pitfall 1: Keyword-Style Queries\n\nExa's neural search interprets natural language semantically. Boolean operators and keyword syntax degrade results.\n\n```typescript\nimport Exa from \"exa-js\";\nconst exa = new Exa(process.env.EXA_API_KEY);\n\n\u002F\u002F BAD: keyword\u002Fboolean style — Exa ignores AND\u002FOR\nconst bad = await exa.search(\n  \"python AND machine learning OR deep learning 2024\"\n);\n\n\u002F\u002F GOOD: natural language statement\nconst good = await exa.search(\n  \"recent tutorials on building ML models with Python\",\n  { type: \"neural\", numResults: 10 }\n);\n```\n\n## Pitfall 2: Wrong Search Type\n\nUsing neural search for exact lookups (URLs, names) or keyword search for conceptual queries silently degrades quality.\n\n```typescript\n\u002F\u002F BAD: neural search for a specific URL\u002Fidentifier\nconst bad = await exa.search(\"arxiv.org\u002Fabs\u002F2301.00001\", { type: \"neural\" });\n\n\u002F\u002F GOOD: keyword for exact terms, neural for concepts\nconst exactMatch = await exa.search(\"arxiv.org\u002Fabs\u002F2301.00001\", {\n  type: \"keyword\",\n});\nconst conceptual = await exa.search(\n  \"transformer architecture improvements for long context\",\n  { type: \"neural\" }\n);\n```\n\n## Pitfall 3: Expecting Content from search()\n\n`search()` returns metadata only (URL, title, score). Content requires `searchAndContents()` or `getContents()`.\n\n```typescript\n\u002F\u002F BAD: accessing .text from search() — it's undefined\nconst results = await exa.search(\"AI safety research\");\nconst text = results.results[0].text;  \u002F\u002F undefined!\n\n\u002F\u002F GOOD: use searchAndContents for text\u002Fhighlights\nconst withContent = await exa.searchAndContents(\"AI safety research\", {\n  numResults: 5,\n  text: { maxCharacters: 2000 },\n  highlights: { maxCharacters: 500 },\n});\nconsole.log(withContent.results[0].text);       \u002F\u002F actual content\nconsole.log(withContent.results[0].highlights);  \u002F\u002F key excerpts\n```\n\n## Pitfall 4: Narrow Date Filters Return Empty\n\nDate filters silently exclude results. A single-day window often returns nothing without error.\n\n```typescript\n\u002F\u002F BAD: too narrow, likely returns empty array\nconst bad = await exa.search(\"AI news\", {\n  startPublishedDate: \"2025-03-15T00:00:00.000Z\",\n  endPublishedDate: \"2025-03-15T23:59:59.000Z\",\n});\n\n\u002F\u002F GOOD: reasonable window with fallback\nlet results = await exa.search(\"AI news\", {\n  startPublishedDate: \"2025-03-01T00:00:00.000Z\",\n  endPublishedDate: \"2025-03-31T23:59:59.000Z\",\n  numResults: 10,\n});\n\u002F\u002F Fallback if no results\nif (results.results.length === 0) {\n  results = await exa.search(\"AI news\", { numResults: 10 });\n}\n```\n\n## Pitfall 5: findSimilar Takes a URL, Not a Query\n\n`findSimilar` expects a URL as its first argument. Passing a query string gives meaningless results.\n\n```typescript\n\u002F\u002F BAD: passing a query string to findSimilar\nconst bad = await exa.findSimilar(\"machine learning research papers\");\n\n\u002F\u002F GOOD: pass a URL — findSimilar finds pages semantically similar to it\nconst good = await exa.findSimilar(\"https:\u002F\u002Farxiv.org\u002Fabs\u002F2301.00001\", {\n  numResults: 10,\n  excludeSourceDomain: true,\n});\n```\n\n## Pitfall 6: Date Filters with company\u002Fpeople Categories\n\nThe `company` and `people` categories do NOT support date filters. Using them returns a 400 error.\n\n```typescript\n\u002F\u002F BAD: date filter with company category → 400 error\nconst bad = await exa.search(\"AI startups\", {\n  category: \"company\",\n  startPublishedDate: \"2024-01-01T00:00:00.000Z\",  \u002F\u002F not supported!\n});\n\n\u002F\u002F GOOD: company search without date filters\nconst good = await exa.search(\"AI startups\", {\n  category: \"company\",\n  numResults: 10,\n});\n```\n\n## Pitfall 7: Not Limiting Content Size\n\nRequesting full text without `maxCharacters` can return massive payloads, increasing latency and cost.\n\n```typescript\n\u002F\u002F BAD: unlimited text retrieval\nconst bad = await exa.searchAndContents(\"topic\", {\n  numResults: 20,\n  text: true,  \u002F\u002F could return megabytes of content\n});\n\n\u002F\u002F GOOD: limit content size\nconst good = await exa.searchAndContents(\"topic\", {\n  numResults: 10,\n  text: { maxCharacters: 2000 },  \u002F\u002F cap at 2000 chars per result\n  highlights: { maxCharacters: 500 },\n});\n```\n\n## Pitfall 8: Creating New Client Per Request\n\nEach `new Exa()` call creates a new HTTP client. Reuse a singleton for connection pooling.\n\n```typescript\n\u002F\u002F BAD: new client every request (in a route handler)\napp.get(\"\u002Fsearch\", async (req, res) => {\n  const exa = new Exa(process.env.EXA_API_KEY);  \u002F\u002F wasteful!\n  const results = await exa.search(req.query.q);\n  res.json(results);\n});\n\n\u002F\u002F GOOD: singleton client\nconst exa = new Exa(process.env.EXA_API_KEY);\napp.get(\"\u002Fsearch\", async (req, res) => {\n  const results = await exa.search(req.query.q);\n  res.json(results);\n});\n```\n\n## Pitfall 9: Ignoring the requestId in Errors\n\nExa error responses include `requestId` for support debugging. Always log it.\n\n```typescript\n\u002F\u002F BAD: generic error handling\ntry {\n  await exa.search(\"query\");\n} catch (err) {\n  console.error(\"Search failed\");  \u002F\u002F loses diagnostic info\n}\n\n\u002F\u002F GOOD: capture requestId\ntry {\n  await exa.search(\"query\");\n} catch (err: any) {\n  console.error(\"Search failed:\", {\n    status: err.status,\n    message: err.message,\n    requestId: err.requestId,  \u002F\u002F include when contacting support\n    tag: err.error_tag,\n  });\n}\n```\n\n## Quick Review Checklist\n- [ ] Queries are natural language, not keyword\u002Fboolean syntax\n- [ ] Search type matches the query intent (neural vs keyword)\n- [ ] Using `searchAndContents` when page content is needed\n- [ ] Date filter windows are wide enough (7+ days)\n- [ ] `findSimilar` receives URLs, not query strings\n- [ ] No date filters on `company` or `people` categories\n- [ ] `maxCharacters` set on text and highlights\n- [ ] Exa client is a singleton, not created per request\n- [ ] Error handling captures `requestId`\n\n## Resources\n- [Exa Search Reference](https:\u002F\u002Fdocs.exa.ai\u002Freference\u002Fsearch)\n- [Exa Error Codes](https:\u002F\u002Fdocs.exa.ai\u002Freference\u002Ferror-codes)\n- [Exa Contents Retrieval](https:\u002F\u002Fdocs.exa.ai\u002Freference\u002Fcontents-retrieval)\n\n## Next Steps\nFor SDK patterns, see `exa-sdk-patterns`. For common errors, see `exa-common-errors`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","exa","audit","best-practices","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Identify and avoid Exa anti-patterns and common integration mistakes.\nUse when reviewing Exa code, onboarding new developers,\nor auditing existing Exa integrations for correctness.\nTrigger with phrases like \"exa mistakes\", \"exa anti-patterns\",\n\"exa pitfalls\", \"exa what not to do\", \"exa code review\".\n","Read, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--exa-pack--exa-known-pitfalls",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 exa-known-pitfalls",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill exa-known-pitfalls",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill exa-known-pitfalls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--exa-pack--exa-known-pitfalls\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",[],[]]