[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7920PACCWMTYVGXPN0C1PKH":3,"skill-same:01M7920PACCWMTYVGXPN0C1PKH":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},"01M7920PACCWMTYVGXPN0C1PKH","klaviyo-security-basics",null,"Apply Klaviyo security best practices for API key management and access control.\nUse when securing API keys, configuring OAuth scopes, implementing webhook\nsignature verification, or auditing Klaviyo security configuration.\nTrigger with phrases like \"klaviyo security\", \"klaviyo secrets\",\n\"secure klaviyo\", \"klaviyo API key security\", \"klaviyo OAuth\".","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--klaviyo-pack--klaviyo-security-basics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: klaviyo-security-basics\ndescription: |\n  Apply Klaviyo security best practices for API key management and access control.\n  Use when securing API keys, configuring OAuth scopes, implementing webhook\n  signature verification, or auditing Klaviyo security configuration.\n  Trigger with phrases like \"klaviyo security\", \"klaviyo secrets\",\n  \"secure klaviyo\", \"klaviyo API key security\", \"klaviyo OAuth\".\nallowed-tools: Read, Write, Edit, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, klaviyo, email-marketing, cdp]\ncompatible-with: claude-code\n---\n\n# Klaviyo Security Basics\n\n## Overview\n\nSecurity best practices for Klaviyo: API key types, OAuth scopes, webhook HMAC-SHA256 signature verification, and secret rotation procedures.\n\n## Prerequisites\n\n- Klaviyo account with API key access\n- Understanding of environment variables and secret management\n- Access to Klaviyo dashboard (Settings > API Keys)\n\n## Instructions\n\n### Step 1: Understand Key Types\n\n| Key Type | Format | Use Case | Sensitivity |\n|----------|--------|----------|-------------|\n| Private API Key | `pk_*` (40+ chars) | Server-side REST API | **CRITICAL** -- never expose client-side |\n| Public API Key | 6 alphanumeric chars | Client-side Track\u002FIdentify only | Low -- safe in browser JS |\n\nPrivate keys authenticate via `Authorization: Klaviyo-API-Key pk_***` header. Public keys pass as `company_id` query parameter.\n\n### Step 2: Environment Variable Configuration\n\n```bash\n# .env (NEVER commit)\nKLAVIYO_PRIVATE_KEY=pk_***************************************\nKLAVIYO_PUBLIC_KEY=UXxxXx\nKLAVIYO_WEBHOOK_SIGNING_SECRET=whsec_*************************\n\n# .gitignore -- mandatory entries\n.env\n.env.local\n.env.*.local\n```\n\n```typescript\n\u002F\u002F src\u002Fconfig\u002Fklaviyo.ts -- validated config loader\nfunction requireEnv(name: string): string {\n  const value = process.env[name];\n  if (!value) throw new Error(`Missing required env: ${name}`);\n  return value;\n}\n\nexport const klaviyoConfig = {\n  privateKey: requireEnv('KLAVIYO_PRIVATE_KEY'),\n  publicKey: process.env.KLAVIYO_PUBLIC_KEY || '',\n  webhookSecret: process.env.KLAVIYO_WEBHOOK_SIGNING_SECRET || '',\n};\n```\n\n### Step 3: Least-Privilege API Key Scopes\n\nCreate separate API keys per environment with minimal scopes:\n\n| Environment | Recommended Scopes | Rationale |\n|-------------|-------------------|-----------|\n| Development | `profiles:read`, `events:read`, `lists:read` | Read-only exploration |\n| Staging | `profiles:read\u002Fwrite`, `events:write`, `lists:read\u002Fwrite` | Full test coverage |\n| Production | Exact scopes your app needs | Minimize blast radius |\n| CI\u002FCD | `profiles:read`, `events:read` | Smoke tests only |\n\n```bash\n# Use separate env vars per environment\nKLAVIYO_PRIVATE_KEY_DEV=pk_dev_***\nKLAVIYO_PRIVATE_KEY_STAGING=pk_staging_***\nKLAVIYO_PRIVATE_KEY_PROD=pk_prod_***\n```\n\n### Step 4: Webhook Signature Verification (HMAC-SHA256)\n\nKlaviyo signs webhook payloads using HMAC-SHA256 with your webhook signing secret.\n\n```typescript\n\u002F\u002F src\u002Fklaviyo\u002Fwebhook-verify.ts\nimport crypto from 'crypto';\n\n\u002F**\n * Verify Klaviyo webhook signature.\n * Klaviyo uses the webhook signing secret (set when creating the webhook)\n * to compute an HMAC-SHA256 signature of the payload.\n *\u002F\nexport function verifyKlaviyoWebhookSignature(\n  payload: Buffer | string,\n  signature: string,\n  secret: string\n): boolean {\n  if (!signature || !secret) return false;\n\n  const expectedSignature = crypto\n    .createHmac('sha256', secret)\n    .update(typeof payload === 'string' ? payload : payload.toString())\n    .digest('base64');\n\n  \u002F\u002F Timing-safe comparison to prevent timing attacks\n  try {\n    return crypto.timingSafeEqual(\n      Buffer.from(signature),\n      Buffer.from(expectedSignature)\n    );\n  } catch {\n    return false;  \u002F\u002F Different lengths\n  }\n}\n```\n\n### Step 5: Express Webhook Middleware\n\n```typescript\nimport express from 'express';\n\napp.post('\u002Fwebhooks\u002Fklaviyo',\n  express.raw({ type: 'application\u002Fjson' }),\n  (req, res) => {\n    const signature = req.headers['klaviyo-webhook-signature'] as string;\n\n    if (!verifyKlaviyoWebhookSignature(\n      req.body,\n      signature,\n      process.env.KLAVIYO_WEBHOOK_SIGNING_SECRET!\n    )) {\n      console.warn('[Security] Invalid webhook signature rejected');\n      return res.status(401).json({ error: 'Invalid signature' });\n    }\n\n    const event = JSON.parse(req.body.toString());\n    \u002F\u002F Process verified event...\n    res.status(200).json({ received: true });\n  }\n);\n```\n\n### Step 6: API Key Rotation Procedure\n\n```bash\n# 1. Generate new key in Klaviyo dashboard (Settings > API Keys)\n#    - Name it with date: \"Production API Key 2025-03\"\n#    - Assign same scopes as the old key\n\n# 2. Deploy new key (zero-downtime)\n#    Update secret in your deployment platform:\n#    - Vercel: vercel env add KLAVIYO_PRIVATE_KEY production\n#    - AWS: aws secretsmanager update-secret --secret-id klaviyo-key --secret-string pk_new_***\n#    - GCP: echo -n \"pk_new_***\" | gcloud secrets versions add klaviyo-key --data-file=-\n\n# 3. Verify new key works\ncurl -s -w \"%{http_code}\" -o \u002Fdev\u002Fnull \\\n  -H \"Authorization: Klaviyo-API-Key pk_new_***\" \\\n  -H \"revision: 2024-10-15\" \\\n  \"https:\u002F\u002Fa.klaviyo.com\u002Fapi\u002Faccounts\u002F\"\n\n# 4. Revoke old key in Klaviyo dashboard\n#    Settings > API Keys > Delete old key\n\n# 5. Audit: check logs for any 401s after rotation\n```\n\n## Security Checklist\n\n- [ ] Private API keys stored in environment variables \u002F secret manager\n- [ ] `.env` files in `.gitignore`\n- [ ] Different API keys per environment (dev\u002Fstaging\u002Fprod)\n- [ ] Minimal scopes per environment\n- [ ] Webhook signatures verified with HMAC-SHA256\n- [ ] API key rotation scheduled (quarterly recommended)\n- [ ] No private keys in client-side code\n- [ ] CI\u002FCD uses read-only key for tests\n- [ ] Git history scanned for leaked keys (`git log -p | grep pk_`)\n\n## Error Handling\n\n| Security Issue | Detection | Mitigation |\n|----------------|-----------|------------|\n| Leaked private key | Git scanning, `trufflehog` | Revoke immediately, rotate |\n| Excessive scopes | Scope audit | Reduce to minimum required |\n| Missing webhook verification | Code review | Add HMAC check |\n| Key not rotated | Age > 90 days | Schedule rotation |\n| 401s after rotation | Log monitoring | Verify all services updated |\n\n## Resources\n\n- [Authenticate API Requests](https:\u002F\u002Fdevelopers.klaviyo.com\u002Fen\u002Fdocs\u002Fauthenticate_)\n- [OAuth Setup](https:\u002F\u002Fdevelopers.klaviyo.com\u002Fen\u002Fdocs\u002Fset_up_oauth)\n- [Webhooks API Overview](https:\u002F\u002Fdevelopers.klaviyo.com\u002Fen\u002Freference\u002Fwebhooks_api_overview)\n\n## Next Steps\n\nFor production deployment, see `klaviyo-prod-checklist`.\n","# Klaviyo Security Basics\n\n## Overview\n\nSecurity best practices for Klaviyo: API key types, OAuth scopes, webhook HMAC-SHA256 signature verification, and secret rotation procedures.\n\n## Prerequisites\n\n- Klaviyo account with API key access\n- Understanding of environment variables and secret management\n- Access to Klaviyo dashboard (Settings > API Keys)\n\n## Instructions\n\n### Step 1: Understand Key Types\n\n| Key Type | Format | Use Case | Sensitivity |\n|----------|--------|----------|-------------|\n| Private API Key | `pk_*` (40+ chars) | Server-side REST API | **CRITICAL** -- never expose client-side |\n| Public API Key | 6 alphanumeric chars | Client-side Track\u002FIdentify only | Low -- safe in browser JS |\n\nPrivate keys authenticate via `Authorization: Klaviyo-API-Key pk_***` header. Public keys pass as `company_id` query parameter.\n\n### Step 2: Environment Variable Configuration\n\n```bash\n# .env (NEVER commit)\nKLAVIYO_PRIVATE_KEY=pk_***************************************\nKLAVIYO_PUBLIC_KEY=UXxxXx\nKLAVIYO_WEBHOOK_SIGNING_SECRET=whsec_*************************\n\n# .gitignore -- mandatory entries\n.env\n.env.local\n.env.*.local\n```\n\n```typescript\n\u002F\u002F src\u002Fconfig\u002Fklaviyo.ts -- validated config loader\nfunction requireEnv(name: string): string {\n  const value = process.env[name];\n  if (!value) throw new Error(`Missing required env: ${name}`);\n  return value;\n}\n\nexport const klaviyoConfig = {\n  privateKey: requireEnv('KLAVIYO_PRIVATE_KEY'),\n  publicKey: process.env.KLAVIYO_PUBLIC_KEY || '',\n  webhookSecret: process.env.KLAVIYO_WEBHOOK_SIGNING_SECRET || '',\n};\n```\n\n### Step 3: Least-Privilege API Key Scopes\n\nCreate separate API keys per environment with minimal scopes:\n\n| Environment | Recommended Scopes | Rationale |\n|-------------|-------------------|-----------|\n| Development | `profiles:read`, `events:read`, `lists:read` | Read-only exploration |\n| Staging | `profiles:read\u002Fwrite`, `events:write`, `lists:read\u002Fwrite` | Full test coverage |\n| Production | Exact scopes your app needs | Minimize blast radius |\n| CI\u002FCD | `profiles:read`, `events:read` | Smoke tests only |\n\n```bash\n# Use separate env vars per environment\nKLAVIYO_PRIVATE_KEY_DEV=pk_dev_***\nKLAVIYO_PRIVATE_KEY_STAGING=pk_staging_***\nKLAVIYO_PRIVATE_KEY_PROD=pk_prod_***\n```\n\n### Step 4: Webhook Signature Verification (HMAC-SHA256)\n\nKlaviyo signs webhook payloads using HMAC-SHA256 with your webhook signing secret.\n\n```typescript\n\u002F\u002F src\u002Fklaviyo\u002Fwebhook-verify.ts\nimport crypto from 'crypto';\n\n\u002F**\n * Verify Klaviyo webhook signature.\n * Klaviyo uses the webhook signing secret (set when creating the webhook)\n * to compute an HMAC-SHA256 signature of the payload.\n *\u002F\nexport function verifyKlaviyoWebhookSignature(\n  payload: Buffer | string,\n  signature: string,\n  secret: string\n): boolean {\n  if (!signature || !secret) return false;\n\n  const expectedSignature = crypto\n    .createHmac('sha256', secret)\n    .update(typeof payload === 'string' ? payload : payload.toString())\n    .digest('base64');\n\n  \u002F\u002F Timing-safe comparison to prevent timing attacks\n  try {\n    return crypto.timingSafeEqual(\n      Buffer.from(signature),\n      Buffer.from(expectedSignature)\n    );\n  } catch {\n    return false;  \u002F\u002F Different lengths\n  }\n}\n```\n\n### Step 5: Express Webhook Middleware\n\n```typescript\nimport express from 'express';\n\napp.post('\u002Fwebhooks\u002Fklaviyo',\n  express.raw({ type: 'application\u002Fjson' }),\n  (req, res) => {\n    const signature = req.headers['klaviyo-webhook-signature'] as string;\n\n    if (!verifyKlaviyoWebhookSignature(\n      req.body,\n      signature,\n      process.env.KLAVIYO_WEBHOOK_SIGNING_SECRET!\n    )) {\n      console.warn('[Security] Invalid webhook signature rejected');\n      return res.status(401).json({ error: 'Invalid signature' });\n    }\n\n    const event = JSON.parse(req.body.toString());\n    \u002F\u002F Process verified event...\n    res.status(200).json({ received: true });\n  }\n);\n```\n\n### Step 6: API Key Rotation Procedure\n\n```bash\n# 1. Generate new key in Klaviyo dashboard (Settings > API Keys)\n#    - Name it with date: \"Production API Key 2025-03\"\n#    - Assign same scopes as the old key\n\n# 2. Deploy new key (zero-downtime)\n#    Update secret in your deployment platform:\n#    - Vercel: vercel env add KLAVIYO_PRIVATE_KEY production\n#    - AWS: aws secretsmanager update-secret --secret-id klaviyo-key --secret-string pk_new_***\n#    - GCP: echo -n \"pk_new_***\" | gcloud secrets versions add klaviyo-key --data-file=-\n\n# 3. Verify new key works\ncurl -s -w \"%{http_code}\" -o \u002Fdev\u002Fnull \\\n  -H \"Authorization: Klaviyo-API-Key pk_new_***\" \\\n  -H \"revision: 2024-10-15\" \\\n  \"https:\u002F\u002Fa.klaviyo.com\u002Fapi\u002Faccounts\u002F\"\n\n# 4. Revoke old key in Klaviyo dashboard\n#    Settings > API Keys > Delete old key\n\n# 5. Audit: check logs for any 401s after rotation\n```\n\n## Security Checklist\n\n- [ ] Private API keys stored in environment variables \u002F secret manager\n- [ ] `.env` files in `.gitignore`\n- [ ] Different API keys per environment (dev\u002Fstaging\u002Fprod)\n- [ ] Minimal scopes per environment\n- [ ] Webhook signatures verified with HMAC-SHA256\n- [ ] API key rotation scheduled (quarterly recommended)\n- [ ] No private keys in client-side code\n- [ ] CI\u002FCD uses read-only key for tests\n- [ ] Git history scanned for leaked keys (`git log -p | grep pk_`)\n\n## Error Handling\n\n| Security Issue | Detection | Mitigation |\n|----------------|-----------|------------|\n| Leaked private key | Git scanning, `trufflehog` | Revoke immediately, rotate |\n| Excessive scopes | Scope audit | Reduce to minimum required |\n| Missing webhook verification | Code review | Add HMAC check |\n| Key not rotated | Age > 90 days | Schedule rotation |\n| 401s after rotation | Log monitoring | Verify all services updated |\n\n## Resources\n\n- [Authenticate API Requests](https:\u002F\u002Fdevelopers.klaviyo.com\u002Fen\u002Fdocs\u002Fauthenticate_)\n- [OAuth Setup](https:\u002F\u002Fdevelopers.klaviyo.com\u002Fen\u002Fdocs\u002Fset_up_oauth)\n- [Webhooks API Overview](https:\u002F\u002Fdevelopers.klaviyo.com\u002Fen\u002Freference\u002Fwebhooks_api_overview)\n\n## Next Steps\n\nFor production deployment, see `klaviyo-prod-checklist`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","klaviyo","email-marketing","cdp","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Apply Klaviyo security best practices for API key management and access control.\nUse when securing API keys, configuring OAuth scopes, implementing webhook\nsignature verification, or auditing Klaviyo security configuration.\nTrigger with phrases like \"klaviyo security\", \"klaviyo secrets\",\n\"secure klaviyo\", \"klaviyo API key security\", \"klaviyo OAuth\".\n","Read, Write, Edit, Grep","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--klaviyo-pack--klaviyo-security-basics",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 klaviyo-security-basics",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill klaviyo-security-basics",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill klaviyo-security-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--klaviyo-pack--klaviyo-security-basics\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",[],[]]