[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7932R3QWDXGMARM1HV6THTY":3,"skill-same:01M7932R3QWDXGMARM1HV6THTY":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},"01M7932R3QWDXGMARM1HV6THTY","maintainx-incident-runbook",null,"Manage incident response for MaintainX integration failures.\nUse when experiencing outages, investigating issues,\nor responding to MaintainX integration incidents.\nTrigger with phrases like \"maintainx incident\", \"maintainx outage\",\n\"maintainx down\", \"maintainx emergency\", \"maintainx runbook\".","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--maintainx-pack--maintainx-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maintainx-incident-runbook\ndescription: |\n  Manage incident response for MaintainX integration failures.\n  Use when experiencing outages, investigating issues,\n  or responding to MaintainX integration incidents.\n  Trigger with phrases like \"maintainx incident\", \"maintainx outage\",\n  \"maintainx down\", \"maintainx emergency\", \"maintainx runbook\".\nallowed-tools: Read, Write, Edit, Bash(curl:*), Bash(npm:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, maintainx, incident-response]\n---\n# MaintainX Incident Runbook\n\n## Overview\nStep-by-step procedures for responding to MaintainX integration incidents, from detection through resolution and post-mortem.\n\n## Prerequisites\n- Access to monitoring dashboards\n- MaintainX admin API credentials\n- On-call contact list\n\n## Severity Classification\n\n| Severity | Definition | Response Time |\n|----------|-----------|---------------|\n| **SEV-1** | Complete integration failure, no work orders processing | 15 min |\n| **SEV-2** | Partial failure, some endpoints degraded | 1 hour |\n| **SEV-3** | Performance degradation, slow responses | 4 hours |\n| **SEV-4** | Non-critical feature broken, workaround available | Next business day |\n\n## Instructions\n\n### Step 1: Immediate Triage (First 5 Minutes)\n\n```bash\n#!\u002Fbin\u002Fbash\necho \"=== MaintainX Incident Triage ===\"\necho \"Time: $(date -u)\"\n\n# Check MaintainX API status\necho -e \"\\n--- API Health ---\"\nfor endpoint in users workorders assets locations; do\n  CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    \"https:\u002F\u002Fapi.getmaintainx.com\u002Fv1\u002F$endpoint?limit=1\" \\\n    -H \"Authorization: Bearer $MAINTAINX_API_KEY\")\n  echo \"  \u002F$endpoint: HTTP $CODE\"\ndone\n\n# Check your integration service\necho -e \"\\n--- Integration Service ---\"\ncurl -s http:\u002F\u002Flocalhost:3000\u002Fhealth | jq . 2>\u002Fdev\u002Fnull || echo \"  Service unreachable\"\n\n# Check recent error logs\necho -e \"\\n--- Recent Errors (last 10 min) ---\"\n# Adjust for your log system:\n# journalctl -u maintainx-sync --since \"10 min ago\" --no-pager | grep -i error | tail -10\n```\n\n### Step 2: Determine Root Cause\n\n| Symptom | Likely Cause | Check |\n|---------|-------------|-------|\n| All endpoints return 401 | API key expired | `echo ${#MAINTAINX_API_KEY}` and test with curl |\n| All endpoints return 5xx | MaintainX platform outage | Check [status.getmaintainx.com](https:\u002F\u002Fstatus.getmaintainx.com) |\n| 429 on all requests | Rate limit exceeded | Review request volume in last hour |\n| Specific endpoint 404 | API path changed | Check [MaintainX changelog](https:\u002F\u002Fdeveloper.maintainx.com) |\n| Timeouts | Network issue | `curl -w \"Total: %time_total seconds\" ...` |\n| Your service crashes | Application error | Check container logs, OOM, disk space |\n\n### Step 3: Apply Mitigation\n\n**API Key Expired (SEV-1)**:\n```bash\n# Generate new key: MaintainX > Settings > Integrations > New Key\n# Update in production:\n# GCP Secret Manager:\necho -n \"NEW_KEY_HERE\" | gcloud secrets versions add maintainx-api-key --data-file=-\n# Restart service to pick up new key:\ngcloud run services update maintainx-integration --region us-central1 --no-traffic\n```\n\n**Rate Limited (SEV-2)**:\n```typescript\n\u002F\u002F Immediately reduce request volume\n\u002F\u002F 1. Enable emergency rate limiting\nprocess.env.MAINTAINX_MAX_REQUESTS_PER_SEC = '1';\n\u002F\u002F 2. Disable non-critical sync jobs\nawait disableScheduledJobs(['asset-sync', 'report-generator']);\n\u002F\u002F 3. Keep only critical work order processing\n```\n\n**MaintainX Platform Outage (SEV-1)**:\n```typescript\n\u002F\u002F Switch to queue-based processing\n\u002F\u002F Buffer all outgoing requests for replay after recovery\nconst queue: Array\u003C{ method: string; path: string; body: any }> = [];\n\nfunction bufferRequest(method: string, path: string, body?: any) {\n  queue.push({ method, path, body });\n  console.log(`Buffered: ${method} ${path} (queue size: ${queue.length})`);\n}\n\n\u002F\u002F When MaintainX recovers, replay buffered requests\nasync function replayQueue(client: MaintainXClient) {\n  console.log(`Replaying ${queue.length} buffered requests...`);\n  for (const req of queue) {\n    await withRetry(() => client.request(req.method, req.path, req.body));\n  }\n  queue.length = 0;\n}\n```\n\n### Step 4: Verify Resolution\n\n```bash\n# Run full health check\ncurl -s http:\u002F\u002Flocalhost:3000\u002Fhealth | jq .\n\n# Verify data flow\necho \"Work orders created in last hour:\"\ncurl -s \"https:\u002F\u002Fapi.getmaintainx.com\u002Fv1\u002Fworkorders?createdAtGte=$(date -u -d '1 hour ago' +%Y-%m-%dT%H:%M:%SZ)&limit=5\" \\\n  -H \"Authorization: Bearer $MAINTAINX_API_KEY\" | jq '.workOrders | length'\n\n# Check for data gaps\necho \"Checking sync state...\"\ncat .maintainx-sync-state.json 2>\u002Fdev\u002Fnull || echo \"No sync state file found\"\n```\n\n### Step 5: Post-Incident Documentation\n\n```markdown\n## Incident Report Template\n\n**Date**: YYYY-MM-DD\n**Severity**: SEV-X\n**Duration**: X hours Y minutes\n**Impact**: [What was affected - e.g., \"work order sync halted for 2 hours\"]\n\n### Timeline\n- HH:MM - Alert triggered\n- HH:MM - Triage started\n- HH:MM - Root cause identified\n- HH:MM - Mitigation applied\n- HH:MM - Full recovery confirmed\n\n### Root Cause\n[Technical explanation]\n\n### Resolution\n[What was done to fix it]\n\n### Action Items\n- [ ] Implement [specific improvement]\n- [ ] Add monitoring for [gap found]\n- [ ] Update runbook with [lesson learned]\n```\n\n## Output\n- Incident triaged and severity classified\n- Root cause identified using diagnostic steps\n- Mitigation applied (key rotation, rate reduction, or request buffering)\n- Recovery verified with health checks and data flow validation\n- Post-incident report documented\n\n## Error Handling\n| Scenario | Immediate Action |\n|----------|-----------------|\n| Total API failure | Buffer requests, check status page, escalate |\n| Intermittent 500s | Enable retry logic, reduce request rate |\n| Data sync gap | Note gap window, schedule backfill after recovery |\n| Webhook delivery failure | Fall back to polling, queue missed events |\n\n## Resources\n- [MaintainX Status Page](https:\u002F\u002Fstatus.getmaintainx.com)\n- [MaintainX API Reference](https:\u002F\u002Fdeveloper.maintainx.com\u002Freference)\n- [MaintainX Help Center](https:\u002F\u002Fhelp.getmaintainx.com)\n\n## Next Steps\nFor data handling patterns, see `maintainx-data-handling`.\n\n## Examples\n\n**Automated alerting on integration health**:\n\n```typescript\n\u002F\u002F Check health every 5 minutes, alert on failure\nimport cron from 'node-cron';\n\ncron.schedule('*\u002F5 * * * *', async () => {\n  try {\n    const res = await fetch('http:\u002F\u002Flocalhost:3000\u002Fhealth');\n    const health = await res.json();\n    if (health.status !== 'healthy') {\n      await sendPagerDutyAlert({\n        severity: 'critical',\n        summary: `MaintainX integration degraded: ${JSON.stringify(health.checks)}`,\n      });\n    }\n  } catch {\n    await sendPagerDutyAlert({\n      severity: 'critical',\n      summary: 'MaintainX integration service unreachable',\n    });\n  }\n});\n```\n","# MaintainX Incident Runbook\n\n## Overview\nStep-by-step procedures for responding to MaintainX integration incidents, from detection through resolution and post-mortem.\n\n## Prerequisites\n- Access to monitoring dashboards\n- MaintainX admin API credentials\n- On-call contact list\n\n## Severity Classification\n\n| Severity | Definition | Response Time |\n|----------|-----------|---------------|\n| **SEV-1** | Complete integration failure, no work orders processing | 15 min |\n| **SEV-2** | Partial failure, some endpoints degraded | 1 hour |\n| **SEV-3** | Performance degradation, slow responses | 4 hours |\n| **SEV-4** | Non-critical feature broken, workaround available | Next business day |\n\n## Instructions\n\n### Step 1: Immediate Triage (First 5 Minutes)\n\n```bash\n#!\u002Fbin\u002Fbash\necho \"=== MaintainX Incident Triage ===\"\necho \"Time: $(date -u)\"\n\n# Check MaintainX API status\necho -e \"\\n--- API Health ---\"\nfor endpoint in users workorders assets locations; do\n  CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    \"https:\u002F\u002Fapi.getmaintainx.com\u002Fv1\u002F$endpoint?limit=1\" \\\n    -H \"Authorization: Bearer $MAINTAINX_API_KEY\")\n  echo \"  \u002F$endpoint: HTTP $CODE\"\ndone\n\n# Check your integration service\necho -e \"\\n--- Integration Service ---\"\ncurl -s http:\u002F\u002Flocalhost:3000\u002Fhealth | jq . 2>\u002Fdev\u002Fnull || echo \"  Service unreachable\"\n\n# Check recent error logs\necho -e \"\\n--- Recent Errors (last 10 min) ---\"\n# Adjust for your log system:\n# journalctl -u maintainx-sync --since \"10 min ago\" --no-pager | grep -i error | tail -10\n```\n\n### Step 2: Determine Root Cause\n\n| Symptom | Likely Cause | Check |\n|---------|-------------|-------|\n| All endpoints return 401 | API key expired | `echo ${#MAINTAINX_API_KEY}` and test with curl |\n| All endpoints return 5xx | MaintainX platform outage | Check [status.getmaintainx.com](https:\u002F\u002Fstatus.getmaintainx.com) |\n| 429 on all requests | Rate limit exceeded | Review request volume in last hour |\n| Specific endpoint 404 | API path changed | Check [MaintainX changelog](https:\u002F\u002Fdeveloper.maintainx.com) |\n| Timeouts | Network issue | `curl -w \"Total: %time_total seconds\" ...` |\n| Your service crashes | Application error | Check container logs, OOM, disk space |\n\n### Step 3: Apply Mitigation\n\n**API Key Expired (SEV-1)**:\n```bash\n# Generate new key: MaintainX > Settings > Integrations > New Key\n# Update in production:\n# GCP Secret Manager:\necho -n \"NEW_KEY_HERE\" | gcloud secrets versions add maintainx-api-key --data-file=-\n# Restart service to pick up new key:\ngcloud run services update maintainx-integration --region us-central1 --no-traffic\n```\n\n**Rate Limited (SEV-2)**:\n```typescript\n\u002F\u002F Immediately reduce request volume\n\u002F\u002F 1. Enable emergency rate limiting\nprocess.env.MAINTAINX_MAX_REQUESTS_PER_SEC = '1';\n\u002F\u002F 2. Disable non-critical sync jobs\nawait disableScheduledJobs(['asset-sync', 'report-generator']);\n\u002F\u002F 3. Keep only critical work order processing\n```\n\n**MaintainX Platform Outage (SEV-1)**:\n```typescript\n\u002F\u002F Switch to queue-based processing\n\u002F\u002F Buffer all outgoing requests for replay after recovery\nconst queue: Array\u003C{ method: string; path: string; body: any }> = [];\n\nfunction bufferRequest(method: string, path: string, body?: any) {\n  queue.push({ method, path, body });\n  console.log(`Buffered: ${method} ${path} (queue size: ${queue.length})`);\n}\n\n\u002F\u002F When MaintainX recovers, replay buffered requests\nasync function replayQueue(client: MaintainXClient) {\n  console.log(`Replaying ${queue.length} buffered requests...`);\n  for (const req of queue) {\n    await withRetry(() => client.request(req.method, req.path, req.body));\n  }\n  queue.length = 0;\n}\n```\n\n### Step 4: Verify Resolution\n\n```bash\n# Run full health check\ncurl -s http:\u002F\u002Flocalhost:3000\u002Fhealth | jq .\n\n# Verify data flow\necho \"Work orders created in last hour:\"\ncurl -s \"https:\u002F\u002Fapi.getmaintainx.com\u002Fv1\u002Fworkorders?createdAtGte=$(date -u -d '1 hour ago' +%Y-%m-%dT%H:%M:%SZ)&limit=5\" \\\n  -H \"Authorization: Bearer $MAINTAINX_API_KEY\" | jq '.workOrders | length'\n\n# Check for data gaps\necho \"Checking sync state...\"\ncat .maintainx-sync-state.json 2>\u002Fdev\u002Fnull || echo \"No sync state file found\"\n```\n\n### Step 5: Post-Incident Documentation\n\n```markdown\n## Incident Report Template\n\n**Date**: YYYY-MM-DD\n**Severity**: SEV-X\n**Duration**: X hours Y minutes\n**Impact**: [What was affected - e.g., \"work order sync halted for 2 hours\"]\n\n### Timeline\n- HH:MM - Alert triggered\n- HH:MM - Triage started\n- HH:MM - Root cause identified\n- HH:MM - Mitigation applied\n- HH:MM - Full recovery confirmed\n\n### Root Cause\n[Technical explanation]\n\n### Resolution\n[What was done to fix it]\n\n### Action Items\n- [ ] Implement [specific improvement]\n- [ ] Add monitoring for [gap found]\n- [ ] Update runbook with [lesson learned]\n```\n\n## Output\n- Incident triaged and severity classified\n- Root cause identified using diagnostic steps\n- Mitigation applied (key rotation, rate reduction, or request buffering)\n- Recovery verified with health checks and data flow validation\n- Post-incident report documented\n\n## Error Handling\n| Scenario | Immediate Action |\n|----------|-----------------|\n| Total API failure | Buffer requests, check status page, escalate |\n| Intermittent 500s | Enable retry logic, reduce request rate |\n| Data sync gap | Note gap window, schedule backfill after recovery |\n| Webhook delivery failure | Fall back to polling, queue missed events |\n\n## Resources\n- [MaintainX Status Page](https:\u002F\u002Fstatus.getmaintainx.com)\n- [MaintainX API Reference](https:\u002F\u002Fdeveloper.maintainx.com\u002Freference)\n- [MaintainX Help Center](https:\u002F\u002Fhelp.getmaintainx.com)\n\n## Next Steps\nFor data handling patterns, see `maintainx-data-handling`.\n\n## Examples\n\n**Automated alerting on integration health**:\n\n```typescript\n\u002F\u002F Check health every 5 minutes, alert on failure\nimport cron from 'node-cron';\n\ncron.schedule('*\u002F5 * * * *', async () => {\n  try {\n    const res = await fetch('http:\u002F\u002Flocalhost:3000\u002Fhealth');\n    const health = await res.json();\n    if (health.status !== 'healthy') {\n      await sendPagerDutyAlert({\n        severity: 'critical',\n        summary: `MaintainX integration degraded: ${JSON.stringify(health.checks)}`,\n      });\n    }\n  } catch {\n    await sendPagerDutyAlert({\n      severity: 'critical',\n      summary: 'MaintainX integration service unreachable',\n    });\n  }\n});\n```\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","maintainx","incident-response","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Manage incident response for MaintainX integration failures.\nUse when experiencing outages, investigating issues,\nor responding to MaintainX integration incidents.\nTrigger with phrases like \"maintainx incident\", \"maintainx outage\",\n\"maintainx down\", \"maintainx emergency\", \"maintainx runbook\".\n","Read, Write, Edit, Bash(curl:*), Bash(npm:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--maintainx-pack--maintainx-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 maintainx-incident-runbook",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill maintainx-incident-runbook",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill maintainx-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--maintainx-pack--maintainx-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",[],[]]