[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7979PVEPXT764M4ECBA04K7":3,"skill-same:01M7979PVEPXT764M4ECBA04K7":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},"01M7979PVEPXT764M4ECBA04K7","windsurf-data-handling",null,"Control what code and data Windsurf AI can access and process in your workspace.\nUse when handling sensitive data, implementing data exclusion patterns,\nor ensuring compliance with privacy regulations in Windsurf environments.\nTrigger with phrases like \"windsurf data privacy\", \"windsurf PII\",\n\"windsurf GDPR\", \"windsurf compliance\", \"codeium data\", \"windsurf telemetry\".","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--windsurf-pack--windsurf-data-handling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: windsurf-data-handling\ndescription: |\n  Control what code and data Windsurf AI can access and process in your workspace.\n  Use when handling sensitive data, implementing data exclusion patterns,\n  or ensuring compliance with privacy regulations in Windsurf environments.\n  Trigger with phrases like \"windsurf data privacy\", \"windsurf PII\",\n  \"windsurf GDPR\", \"windsurf compliance\", \"codeium data\", \"windsurf telemetry\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, windsurf, privacy, compliance, data-handling]\n---\n# Windsurf Data Handling\n\n## Overview\nControl what code and data Windsurf's AI (Cascade, Supercomplete) can access. Covers file exclusion patterns, telemetry controls, Codeium's data processing model, and compliance configuration for regulated environments.\n\n## Prerequisites\n- Windsurf IDE installed\n- Understanding of Codeium's data processing model\n- Identified sensitive files and directories in workspace\n\n## Instructions\n\n### Step 1: Understand Codeium's Data Model\n\n```yaml\n# What happens with your code in Windsurf\ndata_flow:\n  indexed_locally:\n    what: \"File contents, structure, dependencies\"\n    where: \"Local machine only\"\n    purpose: \"Supercomplete context, Cascade awareness\"\n    retention: \"Persists until re-indexed\"\n\n  sent_to_cloud:\n    what: \"Cascade prompts, code snippets around cursor\"\n    where: \"Codeium cloud (or self-hosted for Enterprise)\"\n    purpose: \"AI model inference\"\n    retention: \"Zero-data retention for ALL paid plans\"\n\n  never_processed:\n    what: \"Files in .codeiumignore, .gitignore, node_modules\"\n    where: \"N\u002FA\"\n    purpose: \"N\u002FA\"\n\n  compliance:\n    certifications: [\"SOC 2 Type II\", \"FedRAMP High\"]\n    hipaa: \"BAA available for Enterprise customers\"\n    data_retention: \"Zero for paid plans, configurable for Enterprise\"\n    deployment: \"Cloud, Hybrid, or Self-Hosted options\"\n```\n\n### Step 2: Configure .codeiumignore for Data Protection\n\n```gitignore\n# .codeiumignore — files Windsurf AI will NEVER see or index\n# Uses gitignore syntax. Default: .gitignore and node_modules excluded.\n\n# ===== SECRETS =====\n.env\n.env.*\n.env.local\ncredentials.json\nserviceAccountKey.json\n*.pem\n*.key\n*.p12\n*.pfx\n.aws\u002F\n.gcloud\u002F\n.azure\u002F\nvault-config.*\n\n# ===== CUSTOMER DATA =====\ndata\u002Fcustomers\u002F\ndata\u002Fexports\u002F\ndata\u002Fbackups\u002F\n*.sql\n*.sql.gz\n*.dump\nfixtures\u002Fproduction-*\n\n# ===== INFRASTRUCTURE SECRETS =====\nterraform.tfstate\nterraform.tfstate.backup\n*.tfvars\n*.auto.tfvars\nansible\u002Fvault*\n\n# ===== COMPLIANCE BOUNDARIES =====\n# PCI zone — credit card processing code\nsrc\u002Fpci\u002F\n\n# HIPAA zone — health data processing\nsrc\u002Fhipaa\u002F\n\n# Financial data\nreports\u002Ffinancial\u002F\n```\n\n### Step 3: Disable Telemetry (Regulated Environments)\n\n```json\n\u002F\u002F settings.json — maximum privacy configuration\n{\n  \"codeium.enableTelemetry\": false,\n  \"codeium.enableSnippetTelemetry\": false,\n  \"telemetry.telemetryLevel\": \"off\",\n  \"update.showReleaseNotes\": false\n}\n```\n\n### Step 4: Configure Autocomplete Data Boundaries\n\n```json\n\u002F\u002F Disable Supercomplete for sensitive file types\n{\n  \"codeium.autocomplete.languages\": {\n    \"plaintext\": false,\n    \"env\": false,\n    \"dotenv\": false,\n    \"properties\": false,\n    \"ini\": false,\n    \"yaml\": false,\n    \"json\": false\n  }\n}\n```\n\n**Rationale:** YAML and JSON files often contain configuration with secrets. Disabling Supercomplete for these types prevents the AI from seeing or suggesting content based on config files.\n\n### Step 5: Safe Cascade Usage with Sensitive Code\n\n```markdown\n## Rules for using Cascade in regulated codebases\n\n1. NEVER paste secrets into Cascade chat\n   - BAD: \"My API key is sk-abc123, why isn't it working?\"\n   - GOOD: \"I'm getting auth errors. The key is set in .env as API_KEY.\"\n\n2. NEVER ask Cascade to read excluded files\n   - BAD: \"Read .env and tell me what's configured\"\n   - GOOD: \"What environment variables does src\u002Fconfig.ts expect?\"\n\n3. Use .windsurfrules to enforce safety patterns\n   - \"Always use process.env for secrets, never hardcode\"\n   - \"Never log PII fields: email, phone, ssn, creditCard\"\n\n4. Mark compliance boundaries in .windsurfrules\n   - \"Files in src\u002Fpci\u002F handle credit card data — extra review required\"\n   - \"Files in src\u002Fhipaa\u002F handle health data — never log patient info\"\n```\n\n### Step 6: Enterprise Self-Hosted Deployment\n\nFor maximum data control:\n\n```yaml\n# Enterprise deployment options\ndeployment_modes:\n  cloud:\n    data_flow: \"Code snippets → Codeium cloud → AI response\"\n    retention: \"Zero-data retention (default for paid plans)\"\n    suitable_for: \"Most teams\"\n\n  hybrid:\n    data_flow: \"Code stays on-prem, only prompts sent to cloud\"\n    retention: \"Configurable\"\n    suitable_for: \"Teams with data residency requirements\"\n\n  self_hosted:\n    data_flow: \"Everything on-prem or in your cloud\"\n    retention: \"You control\"\n    suitable_for: \"Highly regulated (finance, healthcare, government)\"\n    requires: \"Enterprise plan + infrastructure team\"\n```\n\n## Data Privacy Audit Checklist\n\n- [ ] `.codeiumignore` covers all secret files and customer data\n- [ ] Telemetry disabled (if required by policy)\n- [ ] Autocomplete disabled for secret-containing file types\n- [ ] `.windsurfrules` includes data handling coding standards\n- [ ] Team trained: never paste secrets into Cascade\n- [ ] Enterprise: deployment mode matches compliance requirements\n- [ ] Enterprise: SSO configured, personal accounts blocked\n- [ ] Regular audit: verify no new sensitive files outside ignore patterns\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| AI suggests hardcoded secrets | Secret was in indexed file | Add to `.codeiumignore`, rotate secret |\n| PII appears in AI suggestions | Customer data in indexed directory | Exclude data directories |\n| Telemetry still sending | Setting not applied | Verify in Settings UI, restart Windsurf |\n| Compliance audit finding | Missing ignore patterns | Audit with `find` for exposed file types |\n\n## Examples\n\n### Quick Privacy Audit\n```bash\nset -euo pipefail\necho \"=== Windsurf Data Privacy Audit ===\"\necho \"Has .codeiumignore: $([ -f .codeiumignore ] && echo 'YES' || echo 'NO')\"\necho \"Potential exposed secrets:\"\nfind . -type f \\\n  -not -path '*\u002Fnode_modules\u002F*' -not -path '*\u002F.git\u002F*' \\\n  \\( -name '*.env*' -o -name '*.key' -o -name '*.pem' -o -name 'credentials*' \\) \\\n  2>\u002Fdev\u002Fnull | while read f; do\n    grep -q \"$(basename \"$f\")\" .codeiumignore 2>\u002Fdev\u002Fnull && echo \"  $f: PROTECTED\" || echo \"  $f: EXPOSED\"\n  done\n```\n\n## Resources\n- [Codeium Privacy Policy](https:\u002F\u002Fcodeium.com\u002Fprivacy-policy)\n- [Windsurf Security](https:\u002F\u002Fwindsurf.com\u002Fsecurity)\n- [Windsurf Ignore Docs](https:\u002F\u002Fdocs.windsurf.com\u002Fcontext-awareness\u002Fwindsurf-ignore)\n\n## Next Steps\nFor enterprise access controls, see `windsurf-enterprise-rbac`.\n","# Windsurf Data Handling\n\n## Overview\nControl what code and data Windsurf's AI (Cascade, Supercomplete) can access. Covers file exclusion patterns, telemetry controls, Codeium's data processing model, and compliance configuration for regulated environments.\n\n## Prerequisites\n- Windsurf IDE installed\n- Understanding of Codeium's data processing model\n- Identified sensitive files and directories in workspace\n\n## Instructions\n\n### Step 1: Understand Codeium's Data Model\n\n```yaml\n# What happens with your code in Windsurf\ndata_flow:\n  indexed_locally:\n    what: \"File contents, structure, dependencies\"\n    where: \"Local machine only\"\n    purpose: \"Supercomplete context, Cascade awareness\"\n    retention: \"Persists until re-indexed\"\n\n  sent_to_cloud:\n    what: \"Cascade prompts, code snippets around cursor\"\n    where: \"Codeium cloud (or self-hosted for Enterprise)\"\n    purpose: \"AI model inference\"\n    retention: \"Zero-data retention for ALL paid plans\"\n\n  never_processed:\n    what: \"Files in .codeiumignore, .gitignore, node_modules\"\n    where: \"N\u002FA\"\n    purpose: \"N\u002FA\"\n\n  compliance:\n    certifications: [\"SOC 2 Type II\", \"FedRAMP High\"]\n    hipaa: \"BAA available for Enterprise customers\"\n    data_retention: \"Zero for paid plans, configurable for Enterprise\"\n    deployment: \"Cloud, Hybrid, or Self-Hosted options\"\n```\n\n### Step 2: Configure .codeiumignore for Data Protection\n\n```gitignore\n# .codeiumignore — files Windsurf AI will NEVER see or index\n# Uses gitignore syntax. Default: .gitignore and node_modules excluded.\n\n# ===== SECRETS =====\n.env\n.env.*\n.env.local\ncredentials.json\nserviceAccountKey.json\n*.pem\n*.key\n*.p12\n*.pfx\n.aws\u002F\n.gcloud\u002F\n.azure\u002F\nvault-config.*\n\n# ===== CUSTOMER DATA =====\ndata\u002Fcustomers\u002F\ndata\u002Fexports\u002F\ndata\u002Fbackups\u002F\n*.sql\n*.sql.gz\n*.dump\nfixtures\u002Fproduction-*\n\n# ===== INFRASTRUCTURE SECRETS =====\nterraform.tfstate\nterraform.tfstate.backup\n*.tfvars\n*.auto.tfvars\nansible\u002Fvault*\n\n# ===== COMPLIANCE BOUNDARIES =====\n# PCI zone — credit card processing code\nsrc\u002Fpci\u002F\n\n# HIPAA zone — health data processing\nsrc\u002Fhipaa\u002F\n\n# Financial data\nreports\u002Ffinancial\u002F\n```\n\n### Step 3: Disable Telemetry (Regulated Environments)\n\n```json\n\u002F\u002F settings.json — maximum privacy configuration\n{\n  \"codeium.enableTelemetry\": false,\n  \"codeium.enableSnippetTelemetry\": false,\n  \"telemetry.telemetryLevel\": \"off\",\n  \"update.showReleaseNotes\": false\n}\n```\n\n### Step 4: Configure Autocomplete Data Boundaries\n\n```json\n\u002F\u002F Disable Supercomplete for sensitive file types\n{\n  \"codeium.autocomplete.languages\": {\n    \"plaintext\": false,\n    \"env\": false,\n    \"dotenv\": false,\n    \"properties\": false,\n    \"ini\": false,\n    \"yaml\": false,\n    \"json\": false\n  }\n}\n```\n\n**Rationale:** YAML and JSON files often contain configuration with secrets. Disabling Supercomplete for these types prevents the AI from seeing or suggesting content based on config files.\n\n### Step 5: Safe Cascade Usage with Sensitive Code\n\n```markdown\n## Rules for using Cascade in regulated codebases\n\n1. NEVER paste secrets into Cascade chat\n   - BAD: \"My API key is sk-abc123, why isn't it working?\"\n   - GOOD: \"I'm getting auth errors. The key is set in .env as API_KEY.\"\n\n2. NEVER ask Cascade to read excluded files\n   - BAD: \"Read .env and tell me what's configured\"\n   - GOOD: \"What environment variables does src\u002Fconfig.ts expect?\"\n\n3. Use .windsurfrules to enforce safety patterns\n   - \"Always use process.env for secrets, never hardcode\"\n   - \"Never log PII fields: email, phone, ssn, creditCard\"\n\n4. Mark compliance boundaries in .windsurfrules\n   - \"Files in src\u002Fpci\u002F handle credit card data — extra review required\"\n   - \"Files in src\u002Fhipaa\u002F handle health data — never log patient info\"\n```\n\n### Step 6: Enterprise Self-Hosted Deployment\n\nFor maximum data control:\n\n```yaml\n# Enterprise deployment options\ndeployment_modes:\n  cloud:\n    data_flow: \"Code snippets → Codeium cloud → AI response\"\n    retention: \"Zero-data retention (default for paid plans)\"\n    suitable_for: \"Most teams\"\n\n  hybrid:\n    data_flow: \"Code stays on-prem, only prompts sent to cloud\"\n    retention: \"Configurable\"\n    suitable_for: \"Teams with data residency requirements\"\n\n  self_hosted:\n    data_flow: \"Everything on-prem or in your cloud\"\n    retention: \"You control\"\n    suitable_for: \"Highly regulated (finance, healthcare, government)\"\n    requires: \"Enterprise plan + infrastructure team\"\n```\n\n## Data Privacy Audit Checklist\n\n- [ ] `.codeiumignore` covers all secret files and customer data\n- [ ] Telemetry disabled (if required by policy)\n- [ ] Autocomplete disabled for secret-containing file types\n- [ ] `.windsurfrules` includes data handling coding standards\n- [ ] Team trained: never paste secrets into Cascade\n- [ ] Enterprise: deployment mode matches compliance requirements\n- [ ] Enterprise: SSO configured, personal accounts blocked\n- [ ] Regular audit: verify no new sensitive files outside ignore patterns\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| AI suggests hardcoded secrets | Secret was in indexed file | Add to `.codeiumignore`, rotate secret |\n| PII appears in AI suggestions | Customer data in indexed directory | Exclude data directories |\n| Telemetry still sending | Setting not applied | Verify in Settings UI, restart Windsurf |\n| Compliance audit finding | Missing ignore patterns | Audit with `find` for exposed file types |\n\n## Examples\n\n### Quick Privacy Audit\n```bash\nset -euo pipefail\necho \"=== Windsurf Data Privacy Audit ===\"\necho \"Has .codeiumignore: $([ -f .codeiumignore ] && echo 'YES' || echo 'NO')\"\necho \"Potential exposed secrets:\"\nfind . -type f \\\n  -not -path '*\u002Fnode_modules\u002F*' -not -path '*\u002F.git\u002F*' \\\n  \\( -name '*.env*' -o -name '*.key' -o -name '*.pem' -o -name 'credentials*' \\) \\\n  2>\u002Fdev\u002Fnull | while read f; do\n    grep -q \"$(basename \"$f\")\" .codeiumignore 2>\u002Fdev\u002Fnull && echo \"  $f: PROTECTED\" || echo \"  $f: EXPOSED\"\n  done\n```\n\n## Resources\n- [Codeium Privacy Policy](https:\u002F\u002Fcodeium.com\u002Fprivacy-policy)\n- [Windsurf Security](https:\u002F\u002Fwindsurf.com\u002Fsecurity)\n- [Windsurf Ignore Docs](https:\u002F\u002Fdocs.windsurf.com\u002Fcontext-awareness\u002Fwindsurf-ignore)\n\n## Next Steps\nFor enterprise access controls, see `windsurf-enterprise-rbac`.\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","windsurf","privacy","compliance","data-handling","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Control what code and data Windsurf AI can access and process in your workspace.\nUse when handling sensitive data, implementing data exclusion patterns,\nor ensuring compliance with privacy regulations in Windsurf environments.\nTrigger with phrases like \"windsurf data privacy\", \"windsurf PII\",\n\"windsurf GDPR\", \"windsurf compliance\", \"codeium data\", \"windsurf telemetry\".\n","Read, Write, Edit","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--windsurf-pack--windsurf-data-handling",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 windsurf-data-handling",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill windsurf-data-handling",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill windsurf-data-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--windsurf-pack--windsurf-data-handling\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",[],[]]