[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M795DZXBHNMB2MZAWJGRVVVC":3,"skill-same:01M795DZXBHNMB2MZAWJGRVVVC":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M795DZXBHNMB2MZAWJGRVVVC","salesforce-incident-runbook",null,"Execute Salesforce incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Salesforce-related outages, investigating API errors,\nor running post-incident reviews for Salesforce integration failures.\nTrigger with phrases like \"salesforce incident\", \"salesforce outage\",\n\"salesforce down\", \"salesforce on-call\", \"salesforce emergency\", \"salesforce broken\".","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--salesforce-pack--salesforce-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: salesforce-incident-runbook\ndescription: |\n  Execute Salesforce incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Salesforce-related outages, investigating API errors,\n  or running post-incident reviews for Salesforce integration failures.\n  Trigger with phrases like \"salesforce incident\", \"salesforce outage\",\n  \"salesforce down\", \"salesforce on-call\", \"salesforce emergency\", \"salesforce broken\".\nallowed-tools: Read, Grep, Bash(sf:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, crm, salesforce]\ncompatible-with: claude-code\n---\n\n# Salesforce Incident Runbook\n\n## Overview\nRapid incident response procedures for Salesforce integration failures, covering Salesforce-side outages, API limit exhaustion, authentication failures, and data sync issues.\n\n## Prerequisites\n- Salesforce CLI authenticated (`sf org login`)\n- Access to Salesforce Status API\n- Monitoring dashboards configured (see `salesforce-observability`)\n- Communication channels (Slack, PagerDuty)\n\n## Quick Triage (Do This First)\n\n```bash\n# 1. Is Salesforce itself down?\ncurl -s https:\u002F\u002Fapi.status.salesforce.com\u002Fv1\u002Fincidents\u002Factive | jq '.[0:3]'\n# If incidents returned → Salesforce-side issue, enable fallback mode\n\n# 2. Check your org's instance status\n# Find your instance at: https:\u002F\u002Fstatus.salesforce.com\ncurl -s \"https:\u002F\u002Fapi.status.salesforce.com\u002Fv1\u002Finstances\u002FNA45\u002Fstatus\" | jq '.status'\n\n# 3. Check API limits — are we out of calls?\nsf limits api display --target-org my-org --json | jq '.result[] | select(.name == \"DailyApiRequests\")'\n# If remaining = 0 → API_LIMIT_EXCEEDED, see mitigation below\n\n# 4. Check authentication\nsf org display --target-org my-org --json | jq '.result.connectedStatus'\n# If \"RefreshTokenError\" → re-authenticate\n\n# 5. Check recent errors in your logs\nsf apex log list --target-org my-org --json | jq '.result[0:5]'\n```\n\n## Decision Tree\n\n```\nIntegration returning errors?\n├── YES: Is status.salesforce.com showing incident?\n│   ├── YES → Salesforce outage. Enable fallback mode. Monitor status page.\n│   └── NO → Check error type below:\n│       ├── INVALID_SESSION_ID (401) → Token expired. Re-authenticate.\n│       ├── REQUEST_LIMIT_EXCEEDED (403) → API limit hit. Reduce calls.\n│       ├── UNABLE_TO_LOCK_ROW (409) → Record contention. Retry with backoff.\n│       ├── MALFORMED_QUERY \u002F INVALID_FIELD → Code bug. Check SOQL.\n│       └── 500\u002F503 → Salesforce-side. Wait and retry.\n└── NO: Is data syncing correctly?\n    ├── YES → Likely resolved or intermittent. Monitor.\n    └── NO → Check CDC subscription, query timestamps, bulk job status.\n```\n\n## Immediate Actions by Error Type\n\n### REQUEST_LIMIT_EXCEEDED — API Limit Exhausted\n```typescript\n\u002F\u002F This is a P1 — your integration is completely blocked\n\n\u002F\u002F 1. Check what's consuming API calls\nconst limits = await conn.request('\u002Fservices\u002Fdata\u002Fv59.0\u002Flimits\u002F');\nconsole.log('API calls:', limits.DailyApiRequests);\nconsole.log('Bulk API:', limits.DailyBulkV2QueryJobs);\n\u002F\u002F Limits reset on a 24-hour rolling basis\n\n\u002F\u002F 2. Identify top consumers (Enterprise+ orgs with EventLogFile)\nconst topUsers = await conn.query(`\n  SELECT UserId, COUNT(Id) callCount\n  FROM EventLogFile\n  WHERE EventType = 'API' AND LogDate = TODAY\n  GROUP BY UserId\n  ORDER BY COUNT(Id) DESC\n  LIMIT 10\n`);\n\n\u002F\u002F 3. Immediate mitigation: pause non-critical integrations\n\u002F\u002F Set env var: SF_CRITICAL_ONLY=true\n\u002F\u002F Only allow essential operations (auth, health check, critical writes)\n```\n\n### INVALID_SESSION_ID — Authentication Failure\n```bash\n# Token expired or revoked — re-authenticate\nsf org login web --alias my-org --instance-url https:\u002F\u002Flogin.salesforce.com\n\n# For CI\u002Fautomated: re-auth with JWT\nsf org login jwt \\\n  --client-id $SF_CLIENT_ID \\\n  --jwt-key-file server.key \\\n  --username $SF_USERNAME \\\n  --alias my-org\n\n# Verify connection is restored\nsf org display --target-org my-org\n```\n\n### Salesforce System Outage\n```typescript\n\u002F\u002F Enable graceful degradation — serve stale data from cache\nconst FALLBACK_MODE = process.env.SF_FALLBACK_MODE === 'true';\n\nasync function queryWithFallback\u003CT>(soql: string, cacheKey: string): Promise\u003CT[]> {\n  if (FALLBACK_MODE) {\n    const cached = await redis.get(cacheKey);\n    if (cached) {\n      console.warn('SF FALLBACK: serving cached data');\n      return JSON.parse(cached);\n    }\n    throw new Error('Salesforce unavailable and no cached data');\n  }\n\n  const conn = await getConnection();\n  const result = await conn.query\u003CT>(soql);\n\n  \u002F\u002F Always update cache for fallback\n  await redis.set(cacheKey, JSON.stringify(result.records), 'EX', 3600);\n  return result.records;\n}\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\nP1 INCIDENT: Salesforce Integration\nStatus: INVESTIGATING\nError: [REQUEST_LIMIT_EXCEEDED \u002F INVALID_SESSION_ID \u002F SF outage]\nImpact: [Data sync paused \u002F API calls failing \u002F user-facing errors]\nCurrent action: [Checking limits \u002F re-authenticating \u002F enabling fallback]\nNext update: [time]\n```\n\n### Postmortem Template\n```markdown\n## Incident: Salesforce [Error Type]\n**Date:** YYYY-MM-DD | **Duration:** X hours | **Severity:** P[1-4]\n\n### Summary\n[One sentence — e.g., \"API limit exhausted due to unoptimized batch job\"]\n\n### Root Cause\n[e.g., \"New sync job ran SELECT * on Contact (3M records) using individual queries instead of Bulk API\"]\n\n### Impact\n- API calls blocked for [duration]\n- [N] users affected \u002F [N] records not synced\n\n### Timeline\n- HH:MM — Alerts fired: REQUEST_LIMIT_EXCEEDED\n- HH:MM — Triage: identified bulk sync as consumer\n- HH:MM — Mitigated: paused sync job\n- HH:MM — Resolved: API limit rolled over\n\n### Action Items\n- [ ] Migrate sync to Bulk API 2.0 — @owner — due date\n- [ ] Add API budget guard (80% warning) — @owner — due date\n- [ ] Set up EventLogFile monitoring for top consumers — @owner — due date\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status API | Network issue | Try https:\u002F\u002Fstatus.salesforce.com manually |\n| sf CLI auth expired | Token revoked | Re-authenticate with `sf org login` |\n| Limits API returns 403 | Limit already exceeded | Wait for rolling 24hr reset |\n| Bulk job stuck | Processing timeout | Abort and retry: `sf data bulk delete` |\n\n## Resources\n- [Salesforce Status API](https:\u002F\u002Fapi.status.salesforce.com\u002F)\n- [Salesforce Trust Site](https:\u002F\u002Fstatus.salesforce.com)\n- [API Limits Quick Reference](https:\u002F\u002Fdeveloper.salesforce.com\u002Fdocs\u002Fatlas.en-us.salesforce_app_limits_cheatsheet.meta\u002Fsalesforce_app_limits_cheatsheet\u002Fsalesforce_app_limits_platform_api.htm)\n\n## Next Steps\nFor data handling, see `salesforce-data-handling`.\n","# Salesforce Incident Runbook\n\n## Overview\nRapid incident response procedures for Salesforce integration failures, covering Salesforce-side outages, API limit exhaustion, authentication failures, and data sync issues.\n\n## Prerequisites\n- Salesforce CLI authenticated (`sf org login`)\n- Access to Salesforce Status API\n- Monitoring dashboards configured (see `salesforce-observability`)\n- Communication channels (Slack, PagerDuty)\n\n## Quick Triage (Do This First)\n\n```bash\n# 1. Is Salesforce itself down?\ncurl -s https:\u002F\u002Fapi.status.salesforce.com\u002Fv1\u002Fincidents\u002Factive | jq '.[0:3]'\n# If incidents returned → Salesforce-side issue, enable fallback mode\n\n# 2. Check your org's instance status\n# Find your instance at: https:\u002F\u002Fstatus.salesforce.com\ncurl -s \"https:\u002F\u002Fapi.status.salesforce.com\u002Fv1\u002Finstances\u002FNA45\u002Fstatus\" | jq '.status'\n\n# 3. Check API limits — are we out of calls?\nsf limits api display --target-org my-org --json | jq '.result[] | select(.name == \"DailyApiRequests\")'\n# If remaining = 0 → API_LIMIT_EXCEEDED, see mitigation below\n\n# 4. Check authentication\nsf org display --target-org my-org --json | jq '.result.connectedStatus'\n# If \"RefreshTokenError\" → re-authenticate\n\n# 5. Check recent errors in your logs\nsf apex log list --target-org my-org --json | jq '.result[0:5]'\n```\n\n## Decision Tree\n\n```\nIntegration returning errors?\n├── YES: Is status.salesforce.com showing incident?\n│   ├── YES → Salesforce outage. Enable fallback mode. Monitor status page.\n│   └── NO → Check error type below:\n│       ├── INVALID_SESSION_ID (401) → Token expired. Re-authenticate.\n│       ├── REQUEST_LIMIT_EXCEEDED (403) → API limit hit. Reduce calls.\n│       ├── UNABLE_TO_LOCK_ROW (409) → Record contention. Retry with backoff.\n│       ├── MALFORMED_QUERY \u002F INVALID_FIELD → Code bug. Check SOQL.\n│       └── 500\u002F503 → Salesforce-side. Wait and retry.\n└── NO: Is data syncing correctly?\n    ├── YES → Likely resolved or intermittent. Monitor.\n    └── NO → Check CDC subscription, query timestamps, bulk job status.\n```\n\n## Immediate Actions by Error Type\n\n### REQUEST_LIMIT_EXCEEDED — API Limit Exhausted\n```typescript\n\u002F\u002F This is a P1 — your integration is completely blocked\n\n\u002F\u002F 1. Check what's consuming API calls\nconst limits = await conn.request('\u002Fservices\u002Fdata\u002Fv59.0\u002Flimits\u002F');\nconsole.log('API calls:', limits.DailyApiRequests);\nconsole.log('Bulk API:', limits.DailyBulkV2QueryJobs);\n\u002F\u002F Limits reset on a 24-hour rolling basis\n\n\u002F\u002F 2. Identify top consumers (Enterprise+ orgs with EventLogFile)\nconst topUsers = await conn.query(`\n  SELECT UserId, COUNT(Id) callCount\n  FROM EventLogFile\n  WHERE EventType = 'API' AND LogDate = TODAY\n  GROUP BY UserId\n  ORDER BY COUNT(Id) DESC\n  LIMIT 10\n`);\n\n\u002F\u002F 3. Immediate mitigation: pause non-critical integrations\n\u002F\u002F Set env var: SF_CRITICAL_ONLY=true\n\u002F\u002F Only allow essential operations (auth, health check, critical writes)\n```\n\n### INVALID_SESSION_ID — Authentication Failure\n```bash\n# Token expired or revoked — re-authenticate\nsf org login web --alias my-org --instance-url https:\u002F\u002Flogin.salesforce.com\n\n# For CI\u002Fautomated: re-auth with JWT\nsf org login jwt \\\n  --client-id $SF_CLIENT_ID \\\n  --jwt-key-file server.key \\\n  --username $SF_USERNAME \\\n  --alias my-org\n\n# Verify connection is restored\nsf org display --target-org my-org\n```\n\n### Salesforce System Outage\n```typescript\n\u002F\u002F Enable graceful degradation — serve stale data from cache\nconst FALLBACK_MODE = process.env.SF_FALLBACK_MODE === 'true';\n\nasync function queryWithFallback\u003CT>(soql: string, cacheKey: string): Promise\u003CT[]> {\n  if (FALLBACK_MODE) {\n    const cached = await redis.get(cacheKey);\n    if (cached) {\n      console.warn('SF FALLBACK: serving cached data');\n      return JSON.parse(cached);\n    }\n    throw new Error('Salesforce unavailable and no cached data');\n  }\n\n  const conn = await getConnection();\n  const result = await conn.query\u003CT>(soql);\n\n  \u002F\u002F Always update cache for fallback\n  await redis.set(cacheKey, JSON.stringify(result.records), 'EX', 3600);\n  return result.records;\n}\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\nP1 INCIDENT: Salesforce Integration\nStatus: INVESTIGATING\nError: [REQUEST_LIMIT_EXCEEDED \u002F INVALID_SESSION_ID \u002F SF outage]\nImpact: [Data sync paused \u002F API calls failing \u002F user-facing errors]\nCurrent action: [Checking limits \u002F re-authenticating \u002F enabling fallback]\nNext update: [time]\n```\n\n### Postmortem Template\n```markdown\n## Incident: Salesforce [Error Type]\n**Date:** YYYY-MM-DD | **Duration:** X hours | **Severity:** P[1-4]\n\n### Summary\n[One sentence — e.g., \"API limit exhausted due to unoptimized batch job\"]\n\n### Root Cause\n[e.g., \"New sync job ran SELECT * on Contact (3M records) using individual queries instead of Bulk API\"]\n\n### Impact\n- API calls blocked for [duration]\n- [N] users affected \u002F [N] records not synced\n\n### Timeline\n- HH:MM — Alerts fired: REQUEST_LIMIT_EXCEEDED\n- HH:MM — Triage: identified bulk sync as consumer\n- HH:MM — Mitigated: paused sync job\n- HH:MM — Resolved: API limit rolled over\n\n### Action Items\n- [ ] Migrate sync to Bulk API 2.0 — @owner — due date\n- [ ] Add API budget guard (80% warning) — @owner — due date\n- [ ] Set up EventLogFile monitoring for top consumers — @owner — due date\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status API | Network issue | Try https:\u002F\u002Fstatus.salesforce.com manually |\n| sf CLI auth expired | Token revoked | Re-authenticate with `sf org login` |\n| Limits API returns 403 | Limit already exceeded | Wait for rolling 24hr reset |\n| Bulk job stuck | Processing timeout | Abort and retry: `sf data bulk delete` |\n\n## Resources\n- [Salesforce Status API](https:\u002F\u002Fapi.status.salesforce.com\u002F)\n- [Salesforce Trust Site](https:\u002F\u002Fstatus.salesforce.com)\n- [API Limits Quick Reference](https:\u002F\u002Fdeveloper.salesforce.com\u002Fdocs\u002Fatlas.en-us.salesforce_app_limits_cheatsheet.meta\u002Fsalesforce_app_limits_cheatsheet\u002Fsalesforce_app_limits_platform_api.htm)\n\n## Next Steps\nFor data handling, see `salesforce-data-handling`.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","crm","salesforce","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Salesforce incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Salesforce-related outages, investigating API errors,\nor running post-incident reviews for Salesforce integration failures.\nTrigger with phrases like \"salesforce incident\", \"salesforce outage\",\n\"salesforce down\", \"salesforce on-call\", \"salesforce emergency\", \"salesforce broken\".\n","Read, Grep, Bash(sf:*), Bash(curl:*)","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--salesforce-pack--salesforce-incident-runbook",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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill salesforce-incident-runbook",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill salesforce-incident-runbook",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill salesforce-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--salesforce-pack--salesforce-incident-runbook\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]