[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792MXFSYE18TH4QRRAMAEYK":3,"skill-same:01M792MXFSYE18TH4QRRAMAEYK":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},"01M792MXFSYE18TH4QRRAMAEYK","lindy-incident-runbook",null,"Incident response procedures for Lindy AI agent failures and outages.\nUse when responding to incidents, troubleshooting agent outages,\nor creating on-call procedures for Lindy-powered systems.\nTrigger with phrases like \"lindy incident\", \"lindy outage\",\n\"lindy on-call\", \"lindy runbook\", \"lindy down\".","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--lindy-pack--lindy-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lindy-incident-runbook\ndescription: |\n  Incident response procedures for Lindy AI agent failures and outages.\n  Use when responding to incidents, troubleshooting agent outages,\n  or creating on-call procedures for Lindy-powered systems.\n  Trigger with phrases like \"lindy incident\", \"lindy outage\",\n  \"lindy on-call\", \"lindy runbook\", \"lindy down\".\nallowed-tools: Read, Write, Edit, Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, lindy, incident-response]\n---\n# Lindy Incident Runbook\n\n## Overview\nIncident response procedures for Lindy AI agent failures. Covers platform outages,\nindividual agent failures, integration breakdowns, credit exhaustion, and webhook\nendpoint failures.\n\n## Incident Severity Levels\n\n| Severity | Description | Response Time | Examples |\n|----------|-------------|---------------|----------|\n| SEV1 | All agents failing, customer impact | 15 minutes | Lindy platform outage, all webhooks failing |\n| SEV2 | Critical agent down | 30 minutes | Support bot offline, phone agent unreachable |\n| SEV3 | Degraded performance | 2 hours | High latency, intermittent failures |\n| SEV4 | Minor issue | 24 hours | Non-critical agent misconfigured |\n\n## Quick Diagnostics (First 5 Minutes)\n\n### Step 1: Check Lindy Platform Status\n```bash\n# Is Lindy up?\ncurl -s -o \u002Fdev\u002Fnull -w \"Lindy API: HTTP %{http_code}\\n\" \\\n  \"https:\u002F\u002Fpublic.lindy.ai\" --max-time 5\n\n# Check status page\necho \"Status page: https:\u002F\u002Fstatus.lindy.ai\"\n```\n\n### Step 2: Check Your Integration\n```bash\n# Is your webhook receiver up?\ncurl -s -o \u002Fdev\u002Fnull -w \"Our endpoint: HTTP %{http_code}\\n\" \\\n  \"https:\u002F\u002Fapi.yourapp.com\u002Fhealth\" --max-time 5\n\n# Is the webhook auth working?\ncurl -s -o \u002Fdev\u002Fnull -w \"Webhook auth: HTTP %{http_code}\\n\" \\\n  -X POST \"https:\u002F\u002Fapi.yourapp.com\u002Flindy\u002Fcallback\" \\\n  -H \"Authorization: Bearer $LINDY_WEBHOOK_SECRET\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"test\": true}' --max-time 5\n```\n\n### Step 3: Check Credit Balance\nLog in at https:\u002F\u002Fapp.lindy.ai > Settings > Billing\n- Credits at 0? Agents stop processing\n- Credits low? Non-essential agents may be paused\n\n## Incident Playbooks\n\n### Incident: Lindy Platform Outage (SEV1)\n**Symptoms**: All agents failing, status.lindy.ai shows incident\n**Impact**: All Lindy-dependent workflows halted\n\n**Runbook**:\n1. Confirm outage at https:\u002F\u002Fstatus.lindy.ai\n2. Notify team: \"Lindy platform outage confirmed. All agents affected.\"\n3. Activate fallback procedures:\n   - Route support emails to human inbox\n   - Disable webhook triggers from your app\n   - Queue events for replay when Lindy recovers\n4. Monitor status page for recovery\n5. When recovered: re-enable triggers, replay queued events, verify agent health\n\n**Fallback code**:\n```typescript\nasync function triggerLindyWithFallback(payload: any) {\n  try {\n    const response = await fetch(WEBHOOK_URL, {\n      method: 'POST',\n      headers: {\n        'Authorization': `Bearer ${SECRET}`,\n        'Content-Type': 'application\u002Fjson',\n      },\n      body: JSON.stringify(payload),\n      signal: AbortSignal.timeout(10000), \u002F\u002F 10s timeout\n    });\n\n    if (!response.ok) throw new Error(`HTTP ${response.status}`);\n    return { routed: 'lindy' };\n  } catch (error) {\n    console.error('Lindy unreachable, activating fallback:', error);\n    await queueForReplay(payload); \u002F\u002F Store for later\n    await notifyTeam(`Lindy trigger failed: ${error}`);\n    return { routed: 'fallback' };\n  }\n}\n```\n\n### Incident: Individual Agent Failure (SEV2)\n**Symptoms**: Specific agent tasks showing \"Failed\" status\n**Impact**: One workflow affected, others may be fine\n\n**Runbook**:\n1. Open agent > Tasks tab > Filter by \"Failed\"\n2. Click latest failed task — identify the failing step\n3. Diagnose based on failing step type:\n   - **Trigger step**: Auth expired? Filter too restrictive?\n   - **Action step**: Integration token expired? Target API down?\n   - **Condition step**: Ambiguous condition prompt?\n   - **Agent step**: Looping? Exit conditions unreachable?\n4. Fix the root cause:\n   - Re-authorize expired integrations\n   - Fix action configuration\n   - Simplify condition prompts\n   - Add fallback exit conditions\n5. Test with a manual trigger\n6. Monitor next 5 tasks for success\n\n### Incident: Integration Auth Expired (SEV2-3)\n**Symptoms**: Actions failing with \"Not authorized\" or \"Token expired\"\n**Impact**: All tasks using that integration fail\n\n**Runbook**:\n1. Identify which integration is failing (Gmail, Slack, Sheets, etc.)\n2. In Lindy dashboard: Settings > Integrations\n3. Find the expired connection (may show warning icon)\n4. Click **Re-authorize** and complete OAuth flow\n5. Re-test the agent with a manual trigger\n6. Set calendar reminder for 90-day re-authorization check\n\n### Incident: Credit Exhaustion (SEV2-3)\n**Symptoms**: Agents stop running, no new tasks created\n**Impact**: All agents paused until credits refill\n\n**Runbook**:\n1. Confirm at Settings > Billing: credits at 0\n2. Immediate: Upgrade plan or purchase additional credits\n3. Investigate: Which agent consumed the most credits?\n4. Root cause: trigger storm? looping agent step? large model overuse?\n5. Fix: Add trigger filters, set exit conditions, downgrade model\n6. Prevent: Set budget alerts at 50%, 80%, 95% thresholds\n\n### Incident: Webhook Endpoint Failure (SEV2-3)\n**Symptoms**: Lindy agent runs but your callback never receives data\n**Impact**: Agent completes but results are lost\n\n**Runbook**:\n1. Check your endpoint health: `curl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth`\n2. Check server logs for incoming requests from Lindy\n3. Verify the HTTP Request action URL matches your production endpoint\n4. Test endpoint independently: send a POST with curl\n5. If endpoint was down: replay failed tasks (re-trigger the agent)\n6. If URL mismatch: update URL in Lindy agent HTTP Request action\n\n## Escalation Matrix\n\n| Level | Contact | When |\n|-------|---------|------|\n| L1 | On-call engineer | Initial response, diagnostics |\n| L2 | Engineering lead | After 30 min SEV1, 1 hour SEV2 |\n| L3 | VP Engineering | After 1 hour SEV1 |\n| Lindy Support | support@lindy.ai | Confirmed Lindy platform issue |\n\n## Post-Incident Template\n```markdown\n## Incident Report\n\n**Date**: YYYY-MM-DD\n**Severity**: SEV[1-4]\n**Duration**: [start time] to [end time] ([total minutes])\n**Impact**: [what was affected, customer impact]\n\n### Timeline\n- HH:MM — Issue detected via [monitoring\u002Fuser report]\n- HH:MM — On-call paged, diagnostics started\n- HH:MM — Root cause identified: [cause]\n- HH:MM — Fix applied: [what was done]\n- HH:MM — Service restored, monitoring confirmed\n\n### Root Cause\n[Technical description of what failed and why]\n\n### Resolution\n[What was done to fix it]\n\n### Prevention\n- [ ] [Action item 1]\n- [ ] [Action item 2]\n- [ ] [Action item 3]\n```\n\n## Error Handling\n\n| Incident Type | Detection | Automated Response |\n|--------------|-----------|-------------------|\n| Platform outage | Health check fails | Queue events, notify team |\n| Agent failure | Task Completed trigger | Slack alert to #ops |\n| Auth expiry | Action step fails | Alert + re-auth link |\n| Credit exhaustion | Billing check | Pause non-critical agents |\n| Endpoint down | Health check | Redirect to fallback |\n\n## Resources\n- [Lindy Status](https:\u002F\u002Fstatus.lindy.ai)\n- [Lindy Support](mailto:support@lindy.ai)\n- [Lindy Community](https:\u002F\u002Fcommunity.lindy.ai)\n\n## Next Steps\nProceed to `lindy-data-handling` for data security and compliance.\n","# Lindy Incident Runbook\n\n## Overview\nIncident response procedures for Lindy AI agent failures. Covers platform outages,\nindividual agent failures, integration breakdowns, credit exhaustion, and webhook\nendpoint failures.\n\n## Incident Severity Levels\n\n| Severity | Description | Response Time | Examples |\n|----------|-------------|---------------|----------|\n| SEV1 | All agents failing, customer impact | 15 minutes | Lindy platform outage, all webhooks failing |\n| SEV2 | Critical agent down | 30 minutes | Support bot offline, phone agent unreachable |\n| SEV3 | Degraded performance | 2 hours | High latency, intermittent failures |\n| SEV4 | Minor issue | 24 hours | Non-critical agent misconfigured |\n\n## Quick Diagnostics (First 5 Minutes)\n\n### Step 1: Check Lindy Platform Status\n```bash\n# Is Lindy up?\ncurl -s -o \u002Fdev\u002Fnull -w \"Lindy API: HTTP %{http_code}\\n\" \\\n  \"https:\u002F\u002Fpublic.lindy.ai\" --max-time 5\n\n# Check status page\necho \"Status page: https:\u002F\u002Fstatus.lindy.ai\"\n```\n\n### Step 2: Check Your Integration\n```bash\n# Is your webhook receiver up?\ncurl -s -o \u002Fdev\u002Fnull -w \"Our endpoint: HTTP %{http_code}\\n\" \\\n  \"https:\u002F\u002Fapi.yourapp.com\u002Fhealth\" --max-time 5\n\n# Is the webhook auth working?\ncurl -s -o \u002Fdev\u002Fnull -w \"Webhook auth: HTTP %{http_code}\\n\" \\\n  -X POST \"https:\u002F\u002Fapi.yourapp.com\u002Flindy\u002Fcallback\" \\\n  -H \"Authorization: Bearer $LINDY_WEBHOOK_SECRET\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"test\": true}' --max-time 5\n```\n\n### Step 3: Check Credit Balance\nLog in at https:\u002F\u002Fapp.lindy.ai > Settings > Billing\n- Credits at 0? Agents stop processing\n- Credits low? Non-essential agents may be paused\n\n## Incident Playbooks\n\n### Incident: Lindy Platform Outage (SEV1)\n**Symptoms**: All agents failing, status.lindy.ai shows incident\n**Impact**: All Lindy-dependent workflows halted\n\n**Runbook**:\n1. Confirm outage at https:\u002F\u002Fstatus.lindy.ai\n2. Notify team: \"Lindy platform outage confirmed. All agents affected.\"\n3. Activate fallback procedures:\n   - Route support emails to human inbox\n   - Disable webhook triggers from your app\n   - Queue events for replay when Lindy recovers\n4. Monitor status page for recovery\n5. When recovered: re-enable triggers, replay queued events, verify agent health\n\n**Fallback code**:\n```typescript\nasync function triggerLindyWithFallback(payload: any) {\n  try {\n    const response = await fetch(WEBHOOK_URL, {\n      method: 'POST',\n      headers: {\n        'Authorization': `Bearer ${SECRET}`,\n        'Content-Type': 'application\u002Fjson',\n      },\n      body: JSON.stringify(payload),\n      signal: AbortSignal.timeout(10000), \u002F\u002F 10s timeout\n    });\n\n    if (!response.ok) throw new Error(`HTTP ${response.status}`);\n    return { routed: 'lindy' };\n  } catch (error) {\n    console.error('Lindy unreachable, activating fallback:', error);\n    await queueForReplay(payload); \u002F\u002F Store for later\n    await notifyTeam(`Lindy trigger failed: ${error}`);\n    return { routed: 'fallback' };\n  }\n}\n```\n\n### Incident: Individual Agent Failure (SEV2)\n**Symptoms**: Specific agent tasks showing \"Failed\" status\n**Impact**: One workflow affected, others may be fine\n\n**Runbook**:\n1. Open agent > Tasks tab > Filter by \"Failed\"\n2. Click latest failed task — identify the failing step\n3. Diagnose based on failing step type:\n   - **Trigger step**: Auth expired? Filter too restrictive?\n   - **Action step**: Integration token expired? Target API down?\n   - **Condition step**: Ambiguous condition prompt?\n   - **Agent step**: Looping? Exit conditions unreachable?\n4. Fix the root cause:\n   - Re-authorize expired integrations\n   - Fix action configuration\n   - Simplify condition prompts\n   - Add fallback exit conditions\n5. Test with a manual trigger\n6. Monitor next 5 tasks for success\n\n### Incident: Integration Auth Expired (SEV2-3)\n**Symptoms**: Actions failing with \"Not authorized\" or \"Token expired\"\n**Impact**: All tasks using that integration fail\n\n**Runbook**:\n1. Identify which integration is failing (Gmail, Slack, Sheets, etc.)\n2. In Lindy dashboard: Settings > Integrations\n3. Find the expired connection (may show warning icon)\n4. Click **Re-authorize** and complete OAuth flow\n5. Re-test the agent with a manual trigger\n6. Set calendar reminder for 90-day re-authorization check\n\n### Incident: Credit Exhaustion (SEV2-3)\n**Symptoms**: Agents stop running, no new tasks created\n**Impact**: All agents paused until credits refill\n\n**Runbook**:\n1. Confirm at Settings > Billing: credits at 0\n2. Immediate: Upgrade plan or purchase additional credits\n3. Investigate: Which agent consumed the most credits?\n4. Root cause: trigger storm? looping agent step? large model overuse?\n5. Fix: Add trigger filters, set exit conditions, downgrade model\n6. Prevent: Set budget alerts at 50%, 80%, 95% thresholds\n\n### Incident: Webhook Endpoint Failure (SEV2-3)\n**Symptoms**: Lindy agent runs but your callback never receives data\n**Impact**: Agent completes but results are lost\n\n**Runbook**:\n1. Check your endpoint health: `curl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth`\n2. Check server logs for incoming requests from Lindy\n3. Verify the HTTP Request action URL matches your production endpoint\n4. Test endpoint independently: send a POST with curl\n5. If endpoint was down: replay failed tasks (re-trigger the agent)\n6. If URL mismatch: update URL in Lindy agent HTTP Request action\n\n## Escalation Matrix\n\n| Level | Contact | When |\n|-------|---------|------|\n| L1 | On-call engineer | Initial response, diagnostics |\n| L2 | Engineering lead | After 30 min SEV1, 1 hour SEV2 |\n| L3 | VP Engineering | After 1 hour SEV1 |\n| Lindy Support | support@lindy.ai | Confirmed Lindy platform issue |\n\n## Post-Incident Template\n```markdown\n## Incident Report\n\n**Date**: YYYY-MM-DD\n**Severity**: SEV[1-4]\n**Duration**: [start time] to [end time] ([total minutes])\n**Impact**: [what was affected, customer impact]\n\n### Timeline\n- HH:MM — Issue detected via [monitoring\u002Fuser report]\n- HH:MM — On-call paged, diagnostics started\n- HH:MM — Root cause identified: [cause]\n- HH:MM — Fix applied: [what was done]\n- HH:MM — Service restored, monitoring confirmed\n\n### Root Cause\n[Technical description of what failed and why]\n\n### Resolution\n[What was done to fix it]\n\n### Prevention\n- [ ] [Action item 1]\n- [ ] [Action item 2]\n- [ ] [Action item 3]\n```\n\n## Error Handling\n\n| Incident Type | Detection | Automated Response |\n|--------------|-----------|-------------------|\n| Platform outage | Health check fails | Queue events, notify team |\n| Agent failure | Task Completed trigger | Slack alert to #ops |\n| Auth expiry | Action step fails | Alert + re-auth link |\n| Credit exhaustion | Billing check | Pause non-critical agents |\n| Endpoint down | Health check | Redirect to fallback |\n\n## Resources\n- [Lindy Status](https:\u002F\u002Fstatus.lindy.ai)\n- [Lindy Support](mailto:support@lindy.ai)\n- [Lindy Community](https:\u002F\u002Fcommunity.lindy.ai)\n\n## Next Steps\nProceed to `lindy-data-handling` for data security and compliance.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","lindy","incident-response","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Incident response procedures for Lindy AI agent failures and outages.\nUse when responding to incidents, troubleshooting agent outages,\nor creating on-call procedures for Lindy-powered systems.\nTrigger with phrases like \"lindy incident\", \"lindy outage\",\n\"lindy on-call\", \"lindy runbook\", \"lindy down\".\n","Read, Write, Edit, Bash(curl:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--lindy-pack--lindy-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 lindy-incident-runbook",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill lindy-incident-runbook",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill lindy-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--lindy-pack--lindy-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",[],[]]