[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M795366HV98QBKNHX4CWK8FC":3,"skill-same:01M795366HV98QBKNHX4CWK8FC":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},"01M795366HV98QBKNHX4CWK8FC","replit-incident-runbook",null,"Execute Replit incident response: triage deployment failures, database issues, and platform outages.\nUse when responding to Replit-related outages, investigating deployment crashes,\nor running post-incident reviews for Replit app failures.\nTrigger with phrases like \"replit incident\", \"replit outage\",\n\"replit down\", \"replit emergency\", \"replit broken\", \"replit crash\".","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--replit-pack--replit-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: replit-incident-runbook\ndescription: |\n  Execute Replit incident response: triage deployment failures, database issues, and platform outages.\n  Use when responding to Replit-related outages, investigating deployment crashes,\n  or running post-incident reviews for Replit app failures.\n  Trigger with phrases like \"replit incident\", \"replit outage\",\n  \"replit down\", \"replit emergency\", \"replit broken\", \"replit crash\".\nallowed-tools: Read, Grep, Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, replit, incident-response, debugging]\n---\n# Replit Incident Runbook\n\n## Overview\nRapid incident response for Replit deployment failures, database issues, and platform outages. Covers triage, diagnosis, remediation, rollback, and communication.\n\n## Prerequisites\n- Access to Replit Workspace and Deployment settings\n- Deployment URL for health checks\n- Communication channel (Slack, email)\n- Rollback awareness (Deployment History)\n\n## Severity Levels\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | App returns 5xx, DB down |\n| P2 | Degraded service | \u003C 1 hour | Slow responses, intermittent errors |\n| P3 | Minor impact | \u003C 4 hours | Non-critical feature broken |\n| P4 | No user impact | Next business day | Monitoring gap |\n\n## Quick Triage (First 5 Minutes)\n\n```bash\nset -euo pipefail\nDEPLOY_URL=\"https:\u002F\u002Fyour-app.replit.app\"\n\necho \"=== TRIAGE ===\"\n\n# 1. Check Replit platform status\necho -n \"Replit Status: \"\ncurl -s https:\u002F\u002Fstatus.replit.com\u002Fapi\u002Fv2\u002Fsummary.json | \\\n  python3 -c \"import sys,json;print(json.load(sys.stdin)['status']['description'])\" 2>\u002Fdev\u002Fnull || \\\n  echo \"Check https:\u002F\u002Fstatus.replit.com\"\n\n# 2. Check your deployment health\necho -n \"App Health: \"\ncurl -s -o \u002Fdev\u002Fnull -w \"HTTP %{http_code} (%{time_total}s)\" \"$DEPLOY_URL\u002Fhealth\" 2>\u002Fdev\u002Fnull || echo \"UNREACHABLE\"\necho \"\"\n\n# 3. Get health details\necho \"Health Response:\"\ncurl -s \"$DEPLOY_URL\u002Fhealth\" 2>\u002Fdev\u002Fnull | python3 -m json.tool 2>\u002Fdev\u002Fnull || echo \"No response\"\n\n# 4. Check if it's a cold start issue (Autoscale)\necho -n \"Second request: \"\ncurl -s -o \u002Fdev\u002Fnull -w \"HTTP %{http_code} (%{time_total}s)\\n\" \"$DEPLOY_URL\u002Fhealth\"\n```\n\n## Decision Tree\n\n```\nApp not responding?\n├─ YES: Is status.replit.com reporting an incident?\n│   ├─ YES → Platform issue. Wait for Replit. Communicate to users.\n│   └─ NO → Your deployment issue. Continue below.\n│\n│   Can you access the Replit Workspace?\n│   ├─ YES → Check deployment logs:\n│   │   ├─ Build error → Fix code, redeploy\n│   │   ├─ Runtime crash → Check logs, fix, redeploy\n│   │   └─ Secret missing → Add to Secrets tab, redeploy\n│   └─ NO → Network\u002Fbrowser issue. Try incognito window.\n│\n└─ App responds but with errors?\n    ├─ 5xx errors → Check logs for crash\u002Fexception\n    ├─ Slow responses → Check database, cold start, memory\n    └─ Auth not working → Verify deployment domain, not dev URL\n```\n\n## Remediation by Error Type\n\n### Deployment Crash (5xx \u002F App Unreachable)\n```markdown\n1. Open Replit Workspace\n2. Go to Deployment Settings > Logs\n3. Look for the crash reason:\n   - \"Error: Cannot find module...\" → Missing dependency\n   - \"FATAL: Missing secrets...\" → Add to Secrets tab\n   - \"EADDRINUSE\" → Port conflict in .replit config\n   - \"JavaScript heap out of memory\" → Increase VM size or fix memory leak\n\n4. Fix the issue in code\n5. Click \"Deploy\" to redeploy\n6. If fix is unclear, ROLLBACK:\n   - Deployment Settings > History\n   - Click \"Rollback\" on last known-good version\n```\n\n### Database Connection Failure\n```markdown\n1. Check database status in Database pane\n2. Verify DATABASE_URL is set in Secrets\n3. Test connection:\n```\n```bash\n# From Replit Shell\nnode -e \"\nconst {Pool} = require('pg');\nconst pool = new Pool({connectionString: process.env.DATABASE_URL, ssl:{rejectUnauthorized:false}});\npool.query('SELECT NOW()').then(r => console.log('OK:', r.rows[0])).catch(e => console.error('FAIL:', e.message)).finally(() => pool.end());\n\"\n```\n```markdown\n4. If connection fails:\n   - Check if PostgreSQL is provisioned (Database pane)\n   - Try creating a new database\n   - Check for connection pool exhaustion (max connections)\n```\n\n### Cold Start Too Slow (Autoscale)\n```markdown\nIf cold starts exceed acceptable latency:\n1. Check deployment type: Autoscale scales to zero\n2. Options:\n   a. Switch to Reserved VM (always-on, no cold starts)\n   b. Set up external keep-alive (ping \u002Fhealth every 4 min)\n   c. Optimize startup: lazy imports, defer DB connection\n3. To switch:\n   - Update .replit: deploymentTarget = \"cloudrun\"\n   - Redeploy\n```\n\n### Secrets Missing After Deploy\n```markdown\n1. Open Secrets tab (lock icon in sidebar)\n2. Verify all required secrets are present\n3. Check Deployment Settings > Environment Variables\n4. Secrets should auto-sync (2025+), but if not:\n   - Remove and re-add the secret\n   - Redeploy\n5. For Account-level secrets:\n   - Account Settings > Secrets\n   - These apply to ALL Repls\n```\n\n## Rollback Procedure\n```markdown\nReplit supports one-click rollback to any previous deployment:\n\n1. Deployment Settings > History\n2. Find the last successful deployment\n3. Click \"Rollback to this version\"\n4. Verify health endpoint\n5. Investigate root cause before redeploying fix\n\nRollback restores:\n- Code at that deployment's commit\n- Deployment configuration at that time\n- Does NOT rollback database changes\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\nP[1-4] INCIDENT: [App Name] on Replit\nStatus: INVESTIGATING \u002F IDENTIFIED \u002F MONITORING \u002F RESOLVED\nImpact: [What users are experiencing]\nCause: [If known]\nAction: [What we're doing]\nETA: [When we expect resolution]\nNext update: [Time]\n```\n\n### External (Status Page)\n```\n[App Name] Service Disruption\n\nWe are experiencing issues with [specific feature\u002Fservice].\n[Describe user impact].\n\nWe have identified the cause and are working on a fix.\nEstimated resolution: [time].\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\nset -euo pipefail\n# Capture deployment logs\n# Go to Deployment Settings > Logs > Copy relevant entries\n\n# Capture timeline\necho \"Timeline of events:\" > incident-report.md\necho \"- [time] Issue detected\" >> incident-report.md\necho \"- [time] Investigation started\" >> incident-report.md\necho \"- [time] Root cause identified\" >> incident-report.md\necho \"- [time] Fix deployed \u002F rollback executed\" >> incident-report.md\necho \"- [time] Service restored\" >> incident-report.md\n```\n\n### Postmortem Template\n```markdown\n## Incident: [Title]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Root Cause\n[Technical explanation]\n\n### Timeline\n- HH:MM — First alert\n- HH:MM — Investigation started\n- HH:MM — Root cause found\n- HH:MM — Fix deployed \u002F rollback\n- HH:MM — Service restored\n\n### Impact\n- Users affected: [N]\n- Downtime: [duration]\n\n### Action Items\n- [ ] [Prevention measure] — Owner — Due date\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't access Workspace | Replit outage | Use status.replit.com, wait |\n| Rollback not available | No previous deployments | Fix forward, deploy fix |\n| Logs too short | Container restarted | Set up external log aggregator |\n| DB rollback needed | Bad migration | Restore from Replit DB snapshot |\n\n## Resources\n- [Replit Status](https:\u002F\u002Fstatus.replit.com)\n- [Deployment Rollbacks](https:\u002F\u002Fblog.replit.com\u002Fintroducing-deployment-rollbacks)\n- [Monitoring Deployments](https:\u002F\u002Fdocs.replit.com\u002Fcloud-services\u002Fdeployments\u002Fmonitoring-a-deployment)\n- [Replit Support](https:\u002F\u002Freplit.com\u002Fsupport)\n\n## Next Steps\nFor data handling patterns, see `replit-data-handling`.\n","# Replit Incident Runbook\n\n## Overview\nRapid incident response for Replit deployment failures, database issues, and platform outages. Covers triage, diagnosis, remediation, rollback, and communication.\n\n## Prerequisites\n- Access to Replit Workspace and Deployment settings\n- Deployment URL for health checks\n- Communication channel (Slack, email)\n- Rollback awareness (Deployment History)\n\n## Severity Levels\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | App returns 5xx, DB down |\n| P2 | Degraded service | \u003C 1 hour | Slow responses, intermittent errors |\n| P3 | Minor impact | \u003C 4 hours | Non-critical feature broken |\n| P4 | No user impact | Next business day | Monitoring gap |\n\n## Quick Triage (First 5 Minutes)\n\n```bash\nset -euo pipefail\nDEPLOY_URL=\"https:\u002F\u002Fyour-app.replit.app\"\n\necho \"=== TRIAGE ===\"\n\n# 1. Check Replit platform status\necho -n \"Replit Status: \"\ncurl -s https:\u002F\u002Fstatus.replit.com\u002Fapi\u002Fv2\u002Fsummary.json | \\\n  python3 -c \"import sys,json;print(json.load(sys.stdin)['status']['description'])\" 2>\u002Fdev\u002Fnull || \\\n  echo \"Check https:\u002F\u002Fstatus.replit.com\"\n\n# 2. Check your deployment health\necho -n \"App Health: \"\ncurl -s -o \u002Fdev\u002Fnull -w \"HTTP %{http_code} (%{time_total}s)\" \"$DEPLOY_URL\u002Fhealth\" 2>\u002Fdev\u002Fnull || echo \"UNREACHABLE\"\necho \"\"\n\n# 3. Get health details\necho \"Health Response:\"\ncurl -s \"$DEPLOY_URL\u002Fhealth\" 2>\u002Fdev\u002Fnull | python3 -m json.tool 2>\u002Fdev\u002Fnull || echo \"No response\"\n\n# 4. Check if it's a cold start issue (Autoscale)\necho -n \"Second request: \"\ncurl -s -o \u002Fdev\u002Fnull -w \"HTTP %{http_code} (%{time_total}s)\\n\" \"$DEPLOY_URL\u002Fhealth\"\n```\n\n## Decision Tree\n\n```\nApp not responding?\n├─ YES: Is status.replit.com reporting an incident?\n│   ├─ YES → Platform issue. Wait for Replit. Communicate to users.\n│   └─ NO → Your deployment issue. Continue below.\n│\n│   Can you access the Replit Workspace?\n│   ├─ YES → Check deployment logs:\n│   │   ├─ Build error → Fix code, redeploy\n│   │   ├─ Runtime crash → Check logs, fix, redeploy\n│   │   └─ Secret missing → Add to Secrets tab, redeploy\n│   └─ NO → Network\u002Fbrowser issue. Try incognito window.\n│\n└─ App responds but with errors?\n    ├─ 5xx errors → Check logs for crash\u002Fexception\n    ├─ Slow responses → Check database, cold start, memory\n    └─ Auth not working → Verify deployment domain, not dev URL\n```\n\n## Remediation by Error Type\n\n### Deployment Crash (5xx \u002F App Unreachable)\n```markdown\n1. Open Replit Workspace\n2. Go to Deployment Settings > Logs\n3. Look for the crash reason:\n   - \"Error: Cannot find module...\" → Missing dependency\n   - \"FATAL: Missing secrets...\" → Add to Secrets tab\n   - \"EADDRINUSE\" → Port conflict in .replit config\n   - \"JavaScript heap out of memory\" → Increase VM size or fix memory leak\n\n4. Fix the issue in code\n5. Click \"Deploy\" to redeploy\n6. If fix is unclear, ROLLBACK:\n   - Deployment Settings > History\n   - Click \"Rollback\" on last known-good version\n```\n\n### Database Connection Failure\n```markdown\n1. Check database status in Database pane\n2. Verify DATABASE_URL is set in Secrets\n3. Test connection:\n```\n```bash\n# From Replit Shell\nnode -e \"\nconst {Pool} = require('pg');\nconst pool = new Pool({connectionString: process.env.DATABASE_URL, ssl:{rejectUnauthorized:false}});\npool.query('SELECT NOW()').then(r => console.log('OK:', r.rows[0])).catch(e => console.error('FAIL:', e.message)).finally(() => pool.end());\n\"\n```\n```markdown\n4. If connection fails:\n   - Check if PostgreSQL is provisioned (Database pane)\n   - Try creating a new database\n   - Check for connection pool exhaustion (max connections)\n```\n\n### Cold Start Too Slow (Autoscale)\n```markdown\nIf cold starts exceed acceptable latency:\n1. Check deployment type: Autoscale scales to zero\n2. Options:\n   a. Switch to Reserved VM (always-on, no cold starts)\n   b. Set up external keep-alive (ping \u002Fhealth every 4 min)\n   c. Optimize startup: lazy imports, defer DB connection\n3. To switch:\n   - Update .replit: deploymentTarget = \"cloudrun\"\n   - Redeploy\n```\n\n### Secrets Missing After Deploy\n```markdown\n1. Open Secrets tab (lock icon in sidebar)\n2. Verify all required secrets are present\n3. Check Deployment Settings > Environment Variables\n4. Secrets should auto-sync (2025+), but if not:\n   - Remove and re-add the secret\n   - Redeploy\n5. For Account-level secrets:\n   - Account Settings > Secrets\n   - These apply to ALL Repls\n```\n\n## Rollback Procedure\n```markdown\nReplit supports one-click rollback to any previous deployment:\n\n1. Deployment Settings > History\n2. Find the last successful deployment\n3. Click \"Rollback to this version\"\n4. Verify health endpoint\n5. Investigate root cause before redeploying fix\n\nRollback restores:\n- Code at that deployment's commit\n- Deployment configuration at that time\n- Does NOT rollback database changes\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\nP[1-4] INCIDENT: [App Name] on Replit\nStatus: INVESTIGATING \u002F IDENTIFIED \u002F MONITORING \u002F RESOLVED\nImpact: [What users are experiencing]\nCause: [If known]\nAction: [What we're doing]\nETA: [When we expect resolution]\nNext update: [Time]\n```\n\n### External (Status Page)\n```\n[App Name] Service Disruption\n\nWe are experiencing issues with [specific feature\u002Fservice].\n[Describe user impact].\n\nWe have identified the cause and are working on a fix.\nEstimated resolution: [time].\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\nset -euo pipefail\n# Capture deployment logs\n# Go to Deployment Settings > Logs > Copy relevant entries\n\n# Capture timeline\necho \"Timeline of events:\" > incident-report.md\necho \"- [time] Issue detected\" >> incident-report.md\necho \"- [time] Investigation started\" >> incident-report.md\necho \"- [time] Root cause identified\" >> incident-report.md\necho \"- [time] Fix deployed \u002F rollback executed\" >> incident-report.md\necho \"- [time] Service restored\" >> incident-report.md\n```\n\n### Postmortem Template\n```markdown\n## Incident: [Title]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Root Cause\n[Technical explanation]\n\n### Timeline\n- HH:MM — First alert\n- HH:MM — Investigation started\n- HH:MM — Root cause found\n- HH:MM — Fix deployed \u002F rollback\n- HH:MM — Service restored\n\n### Impact\n- Users affected: [N]\n- Downtime: [duration]\n\n### Action Items\n- [ ] [Prevention measure] — Owner — Due date\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't access Workspace | Replit outage | Use status.replit.com, wait |\n| Rollback not available | No previous deployments | Fix forward, deploy fix |\n| Logs too short | Container restarted | Set up external log aggregator |\n| DB rollback needed | Bad migration | Restore from Replit DB snapshot |\n\n## Resources\n- [Replit Status](https:\u002F\u002Fstatus.replit.com)\n- [Deployment Rollbacks](https:\u002F\u002Fblog.replit.com\u002Fintroducing-deployment-rollbacks)\n- [Monitoring Deployments](https:\u002F\u002Fdocs.replit.com\u002Fcloud-services\u002Fdeployments\u002Fmonitoring-a-deployment)\n- [Replit Support](https:\u002F\u002Freplit.com\u002Fsupport)\n\n## Next Steps\nFor data handling patterns, see `replit-data-handling`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","replit","incident-response","debugging","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Replit incident response: triage deployment failures, database issues, and platform outages.\nUse when responding to Replit-related outages, investigating deployment crashes,\nor running post-incident reviews for Replit app failures.\nTrigger with phrases like \"replit incident\", \"replit outage\",\n\"replit down\", \"replit emergency\", \"replit broken\", \"replit crash\".\n","Read, Grep, Bash(curl:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--replit-pack--replit-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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill replit-incident-runbook",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill replit-incident-runbook",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill replit-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--replit-pack--replit-incident-runbook\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",[],[]]