[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZXSYMAERW0EFKMKRAMWK5":3,"skill-same:01M78ZXSYMAERW0EFKMKRAMWK5":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},"01M78ZXSYMAERW0EFKMKRAMWK5","figma-architecture-variants",null,"Choose between Figma integration architectures: CLI script, webhook service, or plugin.\nUse when deciding how to integrate with Figma, comparing REST API vs Plugin API,\nor planning a Figma-connected application.\nTrigger with phrases like \"figma architecture\", \"figma blueprint\",\n\"how to integrate figma\", \"figma plugin vs api\", \"figma project type\".","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-architecture-variants\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: figma-architecture-variants\ndescription: |\n  Choose between Figma integration architectures: CLI script, webhook service, or plugin.\n  Use when deciding how to integrate with Figma, comparing REST API vs Plugin API,\n  or planning a Figma-connected application.\n  Trigger with phrases like \"figma architecture\", \"figma blueprint\",\n  \"how to integrate figma\", \"figma plugin vs api\", \"figma project type\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, figma]\ncompatible-with: claude-code\n---\n\n# Figma Architecture Variants\n\n## Overview\nThree proven architecture patterns for Figma integrations, based on the two primary Figma APIs: the REST API (external tools) and the Plugin API (in-editor experiences).\n\n## Prerequisites\n- Clear use case requirements\n- Understanding of Figma REST API vs Plugin API differences\n\n## Instructions\n\n### Step 1: Choose Your Architecture\n\n| Architecture | API Used | Best For | Hosting |\n|-------------|----------|----------|---------|\n| CLI\u002FScript | REST API | Design token sync, asset export | None (runs locally or in CI) |\n| Webhook Service | REST API | Real-time automation, Slack bots | Server\u002Fserverless |\n| Figma Plugin | Plugin API | In-editor tools, design linting | Runs in Figma desktop app |\n\n### Variant A: CLI Script (Simplest)\n\n**Use case:** Extract design tokens, export icons, sync to code\n\n```\nDeveloper runs script\n        │\n        ▼\n  ┌─────────────┐\n  │ CLI Script   │  (Node.js)\n  │ - extract.ts │\n  └──────┬───────┘\n         │ GET \u002Fv1\u002Ffiles\u002F:key\n         │ GET \u002Fv1\u002Fimages\u002F:key\n         ▼\n  ┌─────────────┐\n  │ Figma REST  │\n  │ API         │\n  └──────┬──────┘\n         │\n         ▼\n  ┌─────────────┐\n  │ Output      │\n  │ - tokens.css│\n  │ - icons\u002F    │\n  └─────────────┘\n```\n\n```json\n{\n  \"scripts\": {\n    \"figma:tokens\": \"tsx scripts\u002Fextract-tokens.ts\",\n    \"figma:icons\": \"tsx scripts\u002Fexport-icons.ts\",\n    \"figma:sync\": \"npm run figma:tokens && npm run figma:icons\"\n  }\n}\n```\n\n**Pros:** Zero infrastructure, runs in CI, easy to debug\n**Cons:** Not real-time, manual trigger, no webhook support\n\n---\n\n### Variant B: Webhook Service (Event-Driven)\n\n**Use case:** Auto-sync on file save, Slack notifications, build triggers\n\n```\n  ┌─────────────┐\n  │ Figma Cloud  │\n  │ FILE_UPDATE  │──── Webhook V2 ────┐\n  │ FILE_COMMENT │                    │\n  └──────────────┘                    │\n                                      ▼\n                               ┌──────────────┐\n                               │ Your Service  │\n                               │ (Vercel\u002FFly)  │\n                               ├──────────────┤\n                               │ \u002Fwebhooks     │ ← Verify passcode\n                               │ \u002Fhealth       │\n                               │ \u002Fapi\u002Ftokens   │\n                               └──────┬───────┘\n                                      │\n                          ┌───────────┼───────────┐\n                          ▼           ▼           ▼\n                    ┌──────────┐ ┌──────────┐ ┌──────────┐\n                    │ Token    │ │ Slack    │ │ CI       │\n                    │ Rebuild  │ │ Notify   │ │ Trigger  │\n                    └──────────┘ └──────────┘ └──────────┘\n```\n\n```typescript\n\u002F\u002F Minimal webhook service (Express)\nconst app = express();\napp.post('\u002Fwebhooks\u002Ffigma', express.json(), verifyPasscode, (req, res) => {\n  res.status(200).json({ received: true });\n  processEvent(req.body); \u002F\u002F async\n});\napp.get('\u002Fhealth', healthCheck);\napp.listen(process.env.PORT || 3000);\n```\n\n**Pros:** Real-time, event-driven, no polling waste\n**Cons:** Requires hosting, HTTPS endpoint, webhook management\n\n---\n\n### Variant C: Figma Plugin (In-Editor)\n\n**Use case:** Design linting, component generation, data population\n\n```\n  ┌─────────────────────────────────────────┐\n  │             Figma Desktop App            │\n  │                                         │\n  │  ┌─────────────┐   ┌─────────────────┐ │\n  │  │ Plugin       │   │ Canvas          │ │\n  │  │ Sandbox     │   │ (your design)   │ │\n  │  │             │   │                 │ │\n  │  │ code.ts     │◄──│ figma.currentPage│ │\n  │  │ figma.*     │──►│ figma.createRect │ │\n  │  │             │   │                 │ │\n  │  ├─────────────┤   └─────────────────┘ │\n  │  │ UI iframe   │                        │\n  │  │ ui.html     │                        │\n  │  │ (React\u002FHTML)│                        │\n  │  └─────────────┘                        │\n  └─────────────────────────────────────────┘\n```\n\n```json\n\u002F\u002F manifest.json\n{\n  \"name\": \"My Design Linter\",\n  \"id\": \"1234567890\",\n  \"api\": \"1.0.0\",\n  \"main\": \"dist\u002Fcode.js\",\n  \"ui\": \"dist\u002Fui.html\",\n  \"editorType\": [\"figma\"],\n  \"permissions\": [\"currentuser\"]\n}\n```\n\n```typescript\n\u002F\u002F code.ts -- Plugin API (runs in Figma sandbox)\n\u002F\u002F Access the document directly -- no REST API needed\nconst page = figma.currentPage;\nconst frames = page.findAll(n => n.type === 'FRAME');\n\n\u002F\u002F Create nodes programmatically\nconst rect = figma.createRectangle();\nrect.resize(200, 100);\nrect.fills = [{ type: 'SOLID', color: { r: 1, g: 0.5, b: 0 } }];\npage.appendChild(rect);\n\n\u002F\u002F Read component properties\nconst components = page.findAll(n => n.type === 'COMPONENT') as ComponentNode[];\nfor (const comp of components) {\n  console.log(`${comp.name}: ${comp.width}x${comp.height}`);\n}\n```\n\n**Pros:** Direct document access, instant feedback, rich UI\n**Cons:** Only works in Figma desktop, no server-side processing, sandboxed\n\n### Step 2: Decision Matrix\n\n| Factor | CLI Script | Webhook Service | Figma Plugin |\n|--------|-----------|-----------------|--------------|\n| Real-time | No | Yes | Yes (in-editor) |\n| Infrastructure | None | Server\u002Fserverless | None |\n| CI\u002FCD integration | Natural | Via webhook | Not applicable |\n| User interaction | No | No | Yes |\n| API used | REST API | REST API | Plugin API |\n| File modification | No (read-only) | No (read-only) | Yes (full access) |\n| Figma app required | No | No | Yes |\n| Auth | PAT | PAT + webhook passcode | None (runs in Figma) |\n\n### Step 3: Hybrid Architecture\nMany production systems combine variants:\n\n```\nCLI (CI) ← Scheduled token sync (daily at 9 AM)\n     +\nWebhook Service ← Real-time notifications (Slack, rebuild triggers)\n     +\nFigma Plugin ← In-editor design linting and data population\n```\n\n## Output\n- Architecture variant selected based on use case\n- Data flow documented\n- API choice justified (REST vs Plugin)\n- Implementation skeleton provided\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| CLI too slow | Full file fetch | Use `depth=1` and `\u002Fnodes` |\n| Webhook not firing | No HTTPS | Deploy to platform with TLS |\n| Plugin sandbox limits | Heavy computation | Offload to REST API via fetch in UI iframe |\n| Wrong variant choice | Over-engineering | Start with CLI, add webhook when needed |\n\n## Resources\n- [Figma REST API](https:\u002F\u002Fdevelopers.figma.com\u002Fdocs\u002Frest-api\u002F)\n- [Figma Plugin API](https:\u002F\u002Fdevelopers.figma.com\u002Fdocs\u002Fplugins\u002F)\n- [Figma Widgets API](https:\u002F\u002Fdevelopers.figma.com\u002Fdocs\u002Fwidgets\u002F)\n- [Compare Figma APIs](https:\u002F\u002Fwww.figma.com\u002Fdevelopers\u002Fcompare-apis)\n\n## Next Steps\nFor common anti-patterns, see `figma-known-pitfalls`.\n","# Figma Architecture Variants\n\n## Overview\nThree proven architecture patterns for Figma integrations, based on the two primary Figma APIs: the REST API (external tools) and the Plugin API (in-editor experiences).\n\n## Prerequisites\n- Clear use case requirements\n- Understanding of Figma REST API vs Plugin API differences\n\n## Instructions\n\n### Step 1: Choose Your Architecture\n\n| Architecture | API Used | Best For | Hosting |\n|-------------|----------|----------|---------|\n| CLI\u002FScript | REST API | Design token sync, asset export | None (runs locally or in CI) |\n| Webhook Service | REST API | Real-time automation, Slack bots | Server\u002Fserverless |\n| Figma Plugin | Plugin API | In-editor tools, design linting | Runs in Figma desktop app |\n\n### Variant A: CLI Script (Simplest)\n\n**Use case:** Extract design tokens, export icons, sync to code\n\n```\nDeveloper runs script\n        │\n        ▼\n  ┌─────────────┐\n  │ CLI Script   │  (Node.js)\n  │ - extract.ts │\n  └──────┬───────┘\n         │ GET \u002Fv1\u002Ffiles\u002F:key\n         │ GET \u002Fv1\u002Fimages\u002F:key\n         ▼\n  ┌─────────────┐\n  │ Figma REST  │\n  │ API         │\n  └──────┬──────┘\n         │\n         ▼\n  ┌─────────────┐\n  │ Output      │\n  │ - tokens.css│\n  │ - icons\u002F    │\n  └─────────────┘\n```\n\n```json\n{\n  \"scripts\": {\n    \"figma:tokens\": \"tsx scripts\u002Fextract-tokens.ts\",\n    \"figma:icons\": \"tsx scripts\u002Fexport-icons.ts\",\n    \"figma:sync\": \"npm run figma:tokens && npm run figma:icons\"\n  }\n}\n```\n\n**Pros:** Zero infrastructure, runs in CI, easy to debug\n**Cons:** Not real-time, manual trigger, no webhook support\n\n---\n\n### Variant B: Webhook Service (Event-Driven)\n\n**Use case:** Auto-sync on file save, Slack notifications, build triggers\n\n```\n  ┌─────────────┐\n  │ Figma Cloud  │\n  │ FILE_UPDATE  │──── Webhook V2 ────┐\n  │ FILE_COMMENT │                    │\n  └──────────────┘                    │\n                                      ▼\n                               ┌──────────────┐\n                               │ Your Service  │\n                               │ (Vercel\u002FFly)  │\n                               ├──────────────┤\n                               │ \u002Fwebhooks     │ ← Verify passcode\n                               │ \u002Fhealth       │\n                               │ \u002Fapi\u002Ftokens   │\n                               └──────┬───────┘\n                                      │\n                          ┌───────────┼───────────┐\n                          ▼           ▼           ▼\n                    ┌──────────┐ ┌──────────┐ ┌──────────┐\n                    │ Token    │ │ Slack    │ │ CI       │\n                    │ Rebuild  │ │ Notify   │ │ Trigger  │\n                    └──────────┘ └──────────┘ └──────────┘\n```\n\n```typescript\n\u002F\u002F Minimal webhook service (Express)\nconst app = express();\napp.post('\u002Fwebhooks\u002Ffigma', express.json(), verifyPasscode, (req, res) => {\n  res.status(200).json({ received: true });\n  processEvent(req.body); \u002F\u002F async\n});\napp.get('\u002Fhealth', healthCheck);\napp.listen(process.env.PORT || 3000);\n```\n\n**Pros:** Real-time, event-driven, no polling waste\n**Cons:** Requires hosting, HTTPS endpoint, webhook management\n\n---\n\n### Variant C: Figma Plugin (In-Editor)\n\n**Use case:** Design linting, component generation, data population\n\n```\n  ┌─────────────────────────────────────────┐\n  │             Figma Desktop App            │\n  │                                         │\n  │  ┌─────────────┐   ┌─────────────────┐ │\n  │  │ Plugin       │   │ Canvas          │ │\n  │  │ Sandbox     │   │ (your design)   │ │\n  │  │             │   │                 │ │\n  │  │ code.ts     │◄──│ figma.currentPage│ │\n  │  │ figma.*     │──►│ figma.createRect │ │\n  │  │             │   │                 │ │\n  │  ├─────────────┤   └─────────────────┘ │\n  │  │ UI iframe   │                        │\n  │  │ ui.html     │                        │\n  │  │ (React\u002FHTML)│                        │\n  │  └─────────────┘                        │\n  └─────────────────────────────────────────┘\n```\n\n```json\n\u002F\u002F manifest.json\n{\n  \"name\": \"My Design Linter\",\n  \"id\": \"1234567890\",\n  \"api\": \"1.0.0\",\n  \"main\": \"dist\u002Fcode.js\",\n  \"ui\": \"dist\u002Fui.html\",\n  \"editorType\": [\"figma\"],\n  \"permissions\": [\"currentuser\"]\n}\n```\n\n```typescript\n\u002F\u002F code.ts -- Plugin API (runs in Figma sandbox)\n\u002F\u002F Access the document directly -- no REST API needed\nconst page = figma.currentPage;\nconst frames = page.findAll(n => n.type === 'FRAME');\n\n\u002F\u002F Create nodes programmatically\nconst rect = figma.createRectangle();\nrect.resize(200, 100);\nrect.fills = [{ type: 'SOLID', color: { r: 1, g: 0.5, b: 0 } }];\npage.appendChild(rect);\n\n\u002F\u002F Read component properties\nconst components = page.findAll(n => n.type === 'COMPONENT') as ComponentNode[];\nfor (const comp of components) {\n  console.log(`${comp.name}: ${comp.width}x${comp.height}`);\n}\n```\n\n**Pros:** Direct document access, instant feedback, rich UI\n**Cons:** Only works in Figma desktop, no server-side processing, sandboxed\n\n### Step 2: Decision Matrix\n\n| Factor | CLI Script | Webhook Service | Figma Plugin |\n|--------|-----------|-----------------|--------------|\n| Real-time | No | Yes | Yes (in-editor) |\n| Infrastructure | None | Server\u002Fserverless | None |\n| CI\u002FCD integration | Natural | Via webhook | Not applicable |\n| User interaction | No | No | Yes |\n| API used | REST API | REST API | Plugin API |\n| File modification | No (read-only) | No (read-only) | Yes (full access) |\n| Figma app required | No | No | Yes |\n| Auth | PAT | PAT + webhook passcode | None (runs in Figma) |\n\n### Step 3: Hybrid Architecture\nMany production systems combine variants:\n\n```\nCLI (CI) ← Scheduled token sync (daily at 9 AM)\n     +\nWebhook Service ← Real-time notifications (Slack, rebuild triggers)\n     +\nFigma Plugin ← In-editor design linting and data population\n```\n\n## Output\n- Architecture variant selected based on use case\n- Data flow documented\n- API choice justified (REST vs Plugin)\n- Implementation skeleton provided\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| CLI too slow | Full file fetch | Use `depth=1` and `\u002Fnodes` |\n| Webhook not firing | No HTTPS | Deploy to platform with TLS |\n| Plugin sandbox limits | Heavy computation | Offload to REST API via fetch in UI iframe |\n| Wrong variant choice | Over-engineering | Start with CLI, add webhook when needed |\n\n## Resources\n- [Figma REST API](https:\u002F\u002Fdevelopers.figma.com\u002Fdocs\u002Frest-api\u002F)\n- [Figma Plugin API](https:\u002F\u002Fdevelopers.figma.com\u002Fdocs\u002Fplugins\u002F)\n- [Figma Widgets API](https:\u002F\u002Fdevelopers.figma.com\u002Fdocs\u002Fwidgets\u002F)\n- [Compare Figma APIs](https:\u002F\u002Fwww.figma.com\u002Fdevelopers\u002Fcompare-apis)\n\n## Next Steps\nFor common anti-patterns, see `figma-known-pitfalls`.\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","Choose between Figma integration architectures: CLI script, webhook service, or plugin.\nUse when deciding how to integrate with Figma, comparing REST API vs Plugin API,\nor planning a Figma-connected application.\nTrigger with phrases like \"figma architecture\", \"figma blueprint\",\n\"how to integrate figma\", \"figma plugin vs api\", \"figma project type\".\n","Read, Grep","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--figma-pack--figma-architecture-variants",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-architecture-variants",{"tool":47,"command":48},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill figma-architecture-variants",{"tool":50,"command":51},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill figma-architecture-variants","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--figma-pack--figma-architecture-variants\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",[],[]]