[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792R7RZMQEPP2RFCEARDJBQ":3,"skill-same:01M792R7RZMQEPP2RFCEARDJBQ":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},"01M792R7RZMQEPP2RFCEARDJBQ","linear-incident-runbook",null,"Production incident response procedures for Linear integrations.\nUse when handling production issues, diagnosing outages,\nor responding to Linear-related incidents.\nTrigger: \"linear incident\", \"linear outage\", \"linear production issue\",\n\"debug linear production\", \"linear down\", \"linear 500\".","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--linear-pack--linear-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linear-incident-runbook\ndescription: |\n  Production incident response procedures for Linear integrations.\n  Use when handling production issues, diagnosing outages,\n  or responding to Linear-related incidents.\n  Trigger: \"linear incident\", \"linear outage\", \"linear production issue\",\n  \"debug linear production\", \"linear down\", \"linear 500\".\nallowed-tools: Read, Write, Edit, Bash(curl:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, linear, debugging, incident-response]\n---\n# Linear Incident Runbook\n\n## Overview\nStep-by-step runbooks for handling production incidents with Linear integrations. Covers API authentication failures, rate limiting, webhook issues, and Linear platform outages.\n\n## Incident Classification\n\n| Severity | Impact | Response | Examples |\n|----------|--------|----------|----------|\n| SEV1 | Complete integration outage | \u003C 15 min | Auth broken, API unreachable |\n| SEV2 | Major degradation | \u003C 30 min | High error rate, rate limited |\n| SEV3 | Minor issues | \u003C 2 hours | Some features affected |\n| SEV4 | Low impact | \u003C 24 hours | Warnings, non-critical |\n\n## Immediate Actions (All Incidents)\n\n### Step 1: Confirm the Issue\n```bash\nset -euo pipefail\n\n# 1. Check Linear platform status\ncurl -s https:\u002F\u002Fstatus.linear.app\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# 2. Test your API key\ncurl -s -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { name email } }\"}' | jq .\n\n# 3. Check rate limit status\ncurl -s -I -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { id } }\"}' 2>&1 | grep -i ratelimit\n\n# 4. Check your app health endpoint\ncurl -s https:\u002F\u002Fyourapp.com\u002Fhealth\u002Flinear | jq .\n```\n\n### Step 2: Gather Diagnostic Info\n```typescript\n\u002F\u002F scripts\u002Fincident-diagnostic.ts\nimport { LinearClient } from \"@linear\u002Fsdk\";\n\nasync function diagnose() {\n  console.log(\"=== Linear Incident Diagnostic ===\\n\");\n\n  \u002F\u002F 1. Auth check\n  console.log(\"1. Authentication:\");\n  try {\n    const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\n    const viewer = await client.viewer;\n    console.log(`   OK: ${viewer.name} (${viewer.email})`);\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  \u002F\u002F 2. Team access\n  console.log(\"\\n2. Team Access:\");\n  try {\n    const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\n    const teams = await client.teams();\n    console.log(`   OK: ${teams.nodes.length} teams accessible`);\n    teams.nodes.forEach(t => console.log(`     ${t.key}: ${t.name}`));\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  \u002F\u002F 3. Write test\n  console.log(\"\\n3. Write Capability:\");\n  try {\n    const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\n    const teams = await client.teams();\n    const result = await client.createIssue({\n      teamId: teams.nodes[0].id,\n      title: \"[INCIDENT-DIAG] Safe to delete\",\n    });\n    if (result.success) {\n      const issue = await result.issue;\n      await issue?.delete();\n      console.log(\"   OK: Created and deleted test issue\");\n    }\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  \u002F\u002F 4. Rate limit check\n  console.log(\"\\n4. Rate Limits:\");\n  try {\n    const resp = await fetch(\"https:\u002F\u002Fapi.linear.app\u002Fgraphql\", {\n      method: \"POST\",\n      headers: {\n        Authorization: process.env.LINEAR_API_KEY!,\n        \"Content-Type\": \"application\u002Fjson\",\n      },\n      body: JSON.stringify({ query: \"{ viewer { id } }\" }),\n    });\n    const remaining = resp.headers.get(\"x-ratelimit-requests-remaining\");\n    const limit = resp.headers.get(\"x-ratelimit-requests-limit\");\n    console.log(`   Requests: ${remaining}\u002F${limit}`);\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  console.log(\"\\n=== End Diagnostic ===\");\n}\n\ndiagnose();\n```\n\n## Runbook: API Authentication Failure\n\n**Symptoms:** All API calls returning 401\u002F403, \"Authentication required\" errors\n\n**Diagnosis:**\n```bash\nset -euo pipefail\n# Verify API key format\necho $LINEAR_API_KEY | head -c 8\n# Should output: lin_api_\n\n# Test directly\ncurl -s -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { id } }\"}' | jq .errors\n```\n\n**Resolution:**\n1. Verify key is loaded: `[ -n \"$LINEAR_API_KEY\" ] && echo \"Set\" || echo \"NOT set\"`\n2. Check if rotated: Linear Settings > Account > API > Personal API keys\n3. Generate new key if needed, update secret manager\n4. Restart affected services\n5. If recent deploy caused it: `git revert HEAD && npm run deploy`\n\n## Runbook: Rate Limiting (HTTP 429)\n\n**Symptoms:** HTTP 429 responses, \"Rate limit exceeded\", degraded performance\n\n**Diagnosis:**\n```bash\nset -euo pipefail\ncurl -s -I -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { id } }\"}' 2>&1 | grep -i ratelimit\n```\n\n**Resolution:**\n1. **Emergency throttle** -- add 5s delay between all requests:\n   ```typescript\n   const EMERGENCY_DELAY_MS = 5000;\n   async function emergencyThrottle\u003CT>(fn: () => Promise\u003CT>): Promise\u003CT> {\n     await new Promise(r => setTimeout(r, EMERGENCY_DELAY_MS));\n     return fn();\n   }\n   ```\n2. Stop non-critical background jobs (polling, sync)\n3. Disable bulk operations\n4. Wait for bucket refill (Linear uses leaky bucket, refills continuously)\n5. Post-incident: implement proper request queue and caching\n\n## Runbook: Webhook Failures\n\n**Symptoms:** Events not received, signature validation errors, processing timeouts\n\n**Diagnosis:**\n```bash\nset -euo pipefail\n# Check endpoint is reachable\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fyourapp.com\u002Fwebhooks\u002Flinear\n\n# Verify secret length\necho -n \"$LINEAR_WEBHOOK_SECRET\" | wc -c\n# Should be > 20 characters\n```\n\n**Resolution:**\n1. **Endpoint unreachable:** Check DNS, SSL cert, firewall, load balancer health\n2. **Signature mismatch:** Verify `LINEAR_WEBHOOK_SECRET` matches webhook config in Linear Settings > API > Webhooks\n3. **Body parsing issue:** Ensure using `express.raw()` not `express.json()`\n4. **Processing timeout:** Respond 200 immediately, process async\n5. **Recreate webhook:** Linear Settings > API > Webhooks > delete + recreate\n\n## Runbook: Linear Platform Outage\n\n**Symptoms:** All API calls failing, status.linear.app reports issues\n\n**Resolution:**\n1. Confirm at https:\u002F\u002Fstatus.linear.app\n2. Enable graceful degradation in your app\n3. Queue write operations for replay when API recovers\n4. Serve cached data for read operations\n5. Monitor status page for resolution\n6. After recovery: run consistency check to detect missed webhook events\n\n## Communication Templates\n\n### Initial Announcement\n```\nINCIDENT: Linear Integration Issue\nSeverity: SEVX\nStatus: Investigating\nImpact: [description]\nStart: [UTC timestamp]\n\nInvestigating issues with Linear integration. Updates to follow.\n```\n\n### Resolution\n```\nRESOLVED: Linear Integration Issue\nDuration: X hours Y minutes\nRoot Cause: [brief]\nImpact: [what was affected]\n\nPost-mortem within 48 hours.\n```\n\n## Post-Incident Checklist\n```\n[ ] All systems verified healthy\n[ ] Stuck\u002Fqueued jobs cleared\n[ ] Data consistency validated\n[ ] Stakeholders notified of resolution\n[ ] Timeline documented\n[ ] Root cause identified\n[ ] Action items assigned\n[ ] Monitoring gaps addressed\n```\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Auth failure | Expired\u002Frotated key | Regenerate and update secret manager |\n| Rate limit | Budget exceeded | Emergency throttle, stop background jobs |\n| Webhook failure | Secret mismatch or endpoint down | Verify secret, check endpoint health |\n| Platform outage | Linear infrastructure issue | Graceful degradation, serve cached data |\n\n## Resources\n- [Linear Status Page](https:\u002F\u002Fstatus.linear.app)\n- [Linear API Documentation](https:\u002F\u002Flinear.app\u002Fdevelopers)\n- [Rate Limiting](https:\u002F\u002Flinear.app\u002Fdevelopers\u002Frate-limiting)\n","# Linear Incident Runbook\n\n## Overview\nStep-by-step runbooks for handling production incidents with Linear integrations. Covers API authentication failures, rate limiting, webhook issues, and Linear platform outages.\n\n## Incident Classification\n\n| Severity | Impact | Response | Examples |\n|----------|--------|----------|----------|\n| SEV1 | Complete integration outage | \u003C 15 min | Auth broken, API unreachable |\n| SEV2 | Major degradation | \u003C 30 min | High error rate, rate limited |\n| SEV3 | Minor issues | \u003C 2 hours | Some features affected |\n| SEV4 | Low impact | \u003C 24 hours | Warnings, non-critical |\n\n## Immediate Actions (All Incidents)\n\n### Step 1: Confirm the Issue\n```bash\nset -euo pipefail\n\n# 1. Check Linear platform status\ncurl -s https:\u002F\u002Fstatus.linear.app\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# 2. Test your API key\ncurl -s -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { name email } }\"}' | jq .\n\n# 3. Check rate limit status\ncurl -s -I -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { id } }\"}' 2>&1 | grep -i ratelimit\n\n# 4. Check your app health endpoint\ncurl -s https:\u002F\u002Fyourapp.com\u002Fhealth\u002Flinear | jq .\n```\n\n### Step 2: Gather Diagnostic Info\n```typescript\n\u002F\u002F scripts\u002Fincident-diagnostic.ts\nimport { LinearClient } from \"@linear\u002Fsdk\";\n\nasync function diagnose() {\n  console.log(\"=== Linear Incident Diagnostic ===\\n\");\n\n  \u002F\u002F 1. Auth check\n  console.log(\"1. Authentication:\");\n  try {\n    const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\n    const viewer = await client.viewer;\n    console.log(`   OK: ${viewer.name} (${viewer.email})`);\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  \u002F\u002F 2. Team access\n  console.log(\"\\n2. Team Access:\");\n  try {\n    const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\n    const teams = await client.teams();\n    console.log(`   OK: ${teams.nodes.length} teams accessible`);\n    teams.nodes.forEach(t => console.log(`     ${t.key}: ${t.name}`));\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  \u002F\u002F 3. Write test\n  console.log(\"\\n3. Write Capability:\");\n  try {\n    const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\n    const teams = await client.teams();\n    const result = await client.createIssue({\n      teamId: teams.nodes[0].id,\n      title: \"[INCIDENT-DIAG] Safe to delete\",\n    });\n    if (result.success) {\n      const issue = await result.issue;\n      await issue?.delete();\n      console.log(\"   OK: Created and deleted test issue\");\n    }\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  \u002F\u002F 4. Rate limit check\n  console.log(\"\\n4. Rate Limits:\");\n  try {\n    const resp = await fetch(\"https:\u002F\u002Fapi.linear.app\u002Fgraphql\", {\n      method: \"POST\",\n      headers: {\n        Authorization: process.env.LINEAR_API_KEY!,\n        \"Content-Type\": \"application\u002Fjson\",\n      },\n      body: JSON.stringify({ query: \"{ viewer { id } }\" }),\n    });\n    const remaining = resp.headers.get(\"x-ratelimit-requests-remaining\");\n    const limit = resp.headers.get(\"x-ratelimit-requests-limit\");\n    console.log(`   Requests: ${remaining}\u002F${limit}`);\n  } catch (error: any) {\n    console.log(`   FAILED: ${error.message}`);\n  }\n\n  console.log(\"\\n=== End Diagnostic ===\");\n}\n\ndiagnose();\n```\n\n## Runbook: API Authentication Failure\n\n**Symptoms:** All API calls returning 401\u002F403, \"Authentication required\" errors\n\n**Diagnosis:**\n```bash\nset -euo pipefail\n# Verify API key format\necho $LINEAR_API_KEY | head -c 8\n# Should output: lin_api_\n\n# Test directly\ncurl -s -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { id } }\"}' | jq .errors\n```\n\n**Resolution:**\n1. Verify key is loaded: `[ -n \"$LINEAR_API_KEY\" ] && echo \"Set\" || echo \"NOT set\"`\n2. Check if rotated: Linear Settings > Account > API > Personal API keys\n3. Generate new key if needed, update secret manager\n4. Restart affected services\n5. If recent deploy caused it: `git revert HEAD && npm run deploy`\n\n## Runbook: Rate Limiting (HTTP 429)\n\n**Symptoms:** HTTP 429 responses, \"Rate limit exceeded\", degraded performance\n\n**Diagnosis:**\n```bash\nset -euo pipefail\ncurl -s -I -X POST https:\u002F\u002Fapi.linear.app\u002Fgraphql \\\n  -H \"Authorization: $LINEAR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"{ viewer { id } }\"}' 2>&1 | grep -i ratelimit\n```\n\n**Resolution:**\n1. **Emergency throttle** -- add 5s delay between all requests:\n   ```typescript\n   const EMERGENCY_DELAY_MS = 5000;\n   async function emergencyThrottle\u003CT>(fn: () => Promise\u003CT>): Promise\u003CT> {\n     await new Promise(r => setTimeout(r, EMERGENCY_DELAY_MS));\n     return fn();\n   }\n   ```\n2. Stop non-critical background jobs (polling, sync)\n3. Disable bulk operations\n4. Wait for bucket refill (Linear uses leaky bucket, refills continuously)\n5. Post-incident: implement proper request queue and caching\n\n## Runbook: Webhook Failures\n\n**Symptoms:** Events not received, signature validation errors, processing timeouts\n\n**Diagnosis:**\n```bash\nset -euo pipefail\n# Check endpoint is reachable\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fyourapp.com\u002Fwebhooks\u002Flinear\n\n# Verify secret length\necho -n \"$LINEAR_WEBHOOK_SECRET\" | wc -c\n# Should be > 20 characters\n```\n\n**Resolution:**\n1. **Endpoint unreachable:** Check DNS, SSL cert, firewall, load balancer health\n2. **Signature mismatch:** Verify `LINEAR_WEBHOOK_SECRET` matches webhook config in Linear Settings > API > Webhooks\n3. **Body parsing issue:** Ensure using `express.raw()` not `express.json()`\n4. **Processing timeout:** Respond 200 immediately, process async\n5. **Recreate webhook:** Linear Settings > API > Webhooks > delete + recreate\n\n## Runbook: Linear Platform Outage\n\n**Symptoms:** All API calls failing, status.linear.app reports issues\n\n**Resolution:**\n1. Confirm at https:\u002F\u002Fstatus.linear.app\n2. Enable graceful degradation in your app\n3. Queue write operations for replay when API recovers\n4. Serve cached data for read operations\n5. Monitor status page for resolution\n6. After recovery: run consistency check to detect missed webhook events\n\n## Communication Templates\n\n### Initial Announcement\n```\nINCIDENT: Linear Integration Issue\nSeverity: SEVX\nStatus: Investigating\nImpact: [description]\nStart: [UTC timestamp]\n\nInvestigating issues with Linear integration. Updates to follow.\n```\n\n### Resolution\n```\nRESOLVED: Linear Integration Issue\nDuration: X hours Y minutes\nRoot Cause: [brief]\nImpact: [what was affected]\n\nPost-mortem within 48 hours.\n```\n\n## Post-Incident Checklist\n```\n[ ] All systems verified healthy\n[ ] Stuck\u002Fqueued jobs cleared\n[ ] Data consistency validated\n[ ] Stakeholders notified of resolution\n[ ] Timeline documented\n[ ] Root cause identified\n[ ] Action items assigned\n[ ] Monitoring gaps addressed\n```\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Auth failure | Expired\u002Frotated key | Regenerate and update secret manager |\n| Rate limit | Budget exceeded | Emergency throttle, stop background jobs |\n| Webhook failure | Secret mismatch or endpoint down | Verify secret, check endpoint health |\n| Platform outage | Linear infrastructure issue | Graceful degradation, serve cached data |\n\n## Resources\n- [Linear Status Page](https:\u002F\u002Fstatus.linear.app)\n- [Linear API Documentation](https:\u002F\u002Flinear.app\u002Fdevelopers)\n- [Rate Limiting](https:\u002F\u002Flinear.app\u002Fdevelopers\u002Frate-limiting)\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","linear","debugging","incident-response","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Production incident response procedures for Linear integrations.\nUse when handling production issues, diagnosing outages,\nor responding to Linear-related incidents.\nTrigger: \"linear incident\", \"linear outage\", \"linear production issue\",\n\"debug linear production\", \"linear down\", \"linear 500\".\n","Read, Write, Edit, Bash(curl:*), Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--linear-pack--linear-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 linear-incident-runbook",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill linear-incident-runbook",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill linear-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--linear-pack--linear-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",[],[]]