[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M794MN879JS6A5DTW23Y17DS":3,"skill-same:01M794MN879JS6A5DTW23Y17DS":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},"01M794MN879JS6A5DTW23Y17DS","posthog-incident-runbook",null,"PostHog incident response: triage decision tree, immediate actions for\n401\u002F429\u002F500 errors, graceful degradation, evidence collection, and postmortem.\nTrigger: \"posthog incident\", \"posthog outage\", \"posthog down\",\n\"posthog on-call\", \"posthog emergency\", \"posthog broken production\".","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--posthog-pack--posthog-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: posthog-incident-runbook\ndescription: |\n  PostHog incident response: triage decision tree, immediate actions for\n  401\u002F429\u002F500 errors, graceful degradation, evidence collection, and postmortem.\n  Trigger: \"posthog incident\", \"posthog outage\", \"posthog down\",\n  \"posthog on-call\", \"posthog emergency\", \"posthog broken production\".\nallowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, posthog, incident-response]\n---\n\n# PostHog Incident Runbook\n\n## Overview\n\nRapid incident response for PostHog integration failures. PostHog Cloud has its own status page (status.posthog.com) — the first step is always determining whether the issue is PostHog-side or your integration.\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Analytics completely down | \u003C 15 min | All capture calls failing, feature flags returning defaults |\n| P2 | Degraded analytics | \u003C 1 hour | High latency, partial event loss, slow flag eval |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, specific event type missing |\n| P4 | No user impact | Next day | Monitoring gaps, dashboard stale data |\n\n## Quick Triage (Run First)\n\n```bash\nset -euo pipefail\necho \"=== PostHog Triage ===\"\necho \"\"\n\n# 1. Is PostHog Cloud up?\necho -n \"PostHog US Cloud: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fus.i.posthog.com\u002Fhealthz || echo \"UNREACHABLE\"\necho \"\"\n\n# 2. Can we capture events?\necho -n \"Event capture: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fcapture\u002F' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"${NEXT_PUBLIC_POSTHOG_KEY}\\\",\\\"event\\\":\\\"triage_test\\\",\\\"distinct_id\\\":\\\"triage\\\"}\" || echo \"FAILED\"\necho \"\"\n\n# 3. Can we evaluate flags?\necho -n \"Flag evaluation: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fdecide\u002F?v=3' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"${NEXT_PUBLIC_POSTHOG_KEY}\\\",\\\"distinct_id\\\":\\\"triage\\\"}\" || echo \"FAILED\"\necho \"\"\n\n# 4. Can we access admin API?\nif [ -n \"${POSTHOG_PERSONAL_API_KEY:-}\" ]; then\n  echo -n \"Admin API: \"\n  curl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \"https:\u002F\u002Fapp.posthog.com\u002Fapi\u002Fprojects\u002F\" \\\n    -H \"Authorization: Bearer $POSTHOG_PERSONAL_API_KEY\" || echo \"FAILED\"\n  echo \"\"\nfi\n\n# 5. Check our integration health\necho -n \"Our health endpoint: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \"https:\u002F\u002Fyour-app.com\u002Fapi\u002Fhealth\" || echo \"UNREACHABLE\"\necho \"\"\n```\n\n## Decision Tree\n\n```\nIs PostHog Cloud healthy (status.posthog.com)?\n├── NO → PostHog outage\n│   ├── Enable graceful degradation (feature flags return defaults)\n│   ├── Monitor status.posthog.com for resolution\n│   └── Events will be lost during outage (capture is fire-and-forget)\n│\n└── YES → Our integration issue\n    ├── Are we getting 401? → API key issue (see Error 401 below)\n    ├── Are we getting 429? → Rate limited (see Error 429 below)\n    ├── Are events just not appearing? → Check flush\u002Fshutdown (see below)\n    └── Are flags returning defaults? → Check personalApiKey (see below)\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 — Authentication Failed\n\n```bash\nset -euo pipefail\n# Verify API key type and validity\necho \"Project key prefix: $(echo \"$NEXT_PUBLIC_POSTHOG_KEY\" | head -c 4)\"\necho \"Personal key prefix: $(echo \"$POSTHOG_PERSONAL_API_KEY\" | head -c 4)\"\n\n# Test project key (should return HTTP 200)\ncurl -s -o \u002Fdev\u002Fnull -w \"Capture: %{http_code}\\n\" -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fcapture\u002F' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"$NEXT_PUBLIC_POSTHOG_KEY\\\",\\\"event\\\":\\\"test\\\",\\\"distinct_id\\\":\\\"test\\\"}\"\n\n# Test personal key (should return project list)\ncurl -s -o \u002Fdev\u002Fnull -w \"Admin: %{http_code}\\n\" \"https:\u002F\u002Fapp.posthog.com\u002Fapi\u002Fprojects\u002F\" \\\n  -H \"Authorization: Bearer $POSTHOG_PERSONAL_API_KEY\"\n\n# Fix: If key is invalid, rotate in PostHog dashboard and update secrets\n```\n\n### 429 — Rate Limited\n\n```bash\nset -euo pipefail\n# PostHog rate limits (private API only):\n# - Analytics endpoints: 240\u002Fmin, 1200\u002Fhour\n# - HogQL query: 1200\u002Fhour\n# - Local flag eval polling: 600\u002Fmin\n# - Capture endpoints: NO LIMIT\n\n# Immediate: Cache API responses, reduce polling frequency\n# Long-term: See posthog-rate-limits skill\n```\n\n### Events Not Appearing\n\n```bash\nset -euo pipefail\n# Most common cause: not calling flush\u002Fshutdown in serverless\n\n# Check 1: Is capture endpoint reachable?\ncurl -s -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fcapture\u002F' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"$NEXT_PUBLIC_POSTHOG_KEY\\\",\\\"event\\\":\\\"debug_test\\\",\\\"distinct_id\\\":\\\"debug-$(date +%s)\\\"}\" | jq .\n# Expected: {\"status\": 1}\n\n# Check 2: Verify API host is correct (common mistake)\n# WRONG: https:\u002F\u002Fapp.posthog.com (this is the UI)\n# RIGHT: https:\u002F\u002Fus.i.posthog.com (this is the ingest endpoint)\n```\n\n### Feature Flags Returning Defaults\n\n```typescript\n\u002F\u002F Most common causes:\n\u002F\u002F 1. No personalApiKey → falls back to remote eval which may fail\n\u002F\u002F 2. Flags not loaded yet → check timing\n\u002F\u002F 3. Wrong project key → flags from different project\n\n\u002F\u002F Fix 1: Add personalApiKey\nconst posthog = new PostHog(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {\n  personalApiKey: process.env.POSTHOG_PERSONAL_API_KEY, \u002F\u002F Required for local eval\n});\n\n\u002F\u002F Fix 2: Wait for flags in browser\nposthog.onFeatureFlags(() => {\n  \u002F\u002F Now flags are loaded\n  const value = posthog.isFeatureEnabled('my-flag');\n});\n```\n\n## Graceful Degradation Pattern\n\n```typescript\n\u002F\u002F PostHog should NEVER crash your app\nfunction safeCapture(distinctId: string, event: string, props?: Record\u003Cstring, any>) {\n  try {\n    posthog.capture({ distinctId, event, properties: props });\n  } catch {\n    \u002F\u002F Swallow error — analytics failure should never impact users\n  }\n}\n\nasync function safeFlag(key: string, userId: string, fallback: boolean = false): Promise\u003Cboolean> {\n  try {\n    const result = await posthog.isFeatureEnabled(key, userId);\n    return result ?? fallback;\n  } catch {\n    return fallback; \u002F\u002F Return safe default\n  }\n}\n```\n\n## Post-Incident Evidence Collection\n\n```bash\nset -euo pipefail\nINCIDENT_DIR=\"posthog-incident-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$INCIDENT_DIR\"\n\n# Collect diagnostics\necho \"Incident: $(date -u)\" > \"$INCIDENT_DIR\u002Ftimeline.txt\"\ncurl -s https:\u002F\u002Fus.i.posthog.com\u002Fhealthz > \"$INCIDENT_DIR\u002Fhealthz.json\" 2>&1\nenv | grep -i posthog | sed 's\u002F=.*\u002F=***\u002F' > \"$INCIDENT_DIR\u002Fenv-redacted.txt\"\nnpm list posthog-js posthog-node 2>\u002Fdev\u002Fnull > \"$INCIDENT_DIR\u002Fversions.txt\"\n\ntar -czf \"$INCIDENT_DIR.tar.gz\" \"$INCIDENT_DIR\"\necho \"Evidence collected: $INCIDENT_DIR.tar.gz\"\n```\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Complete analytics outage | PostHog Cloud down | Enable graceful degradation, monitor status page |\n| Partial event loss | Serverless not flushing | Add `await posthog.shutdown()` |\n| All flags return false | `personalApiKey` missing or expired | Add\u002Frotate personal API key |\n| Admin API 401 | Personal key revoked | Generate new key in PostHog settings |\n| High latency | Network path to PostHog | Check reverse proxy, try direct connection |\n\n## Output\n\n- Triage commands identifying issue source\n- Immediate remediation for each error type\n- Graceful degradation wrappers\n- Post-incident evidence bundle\n\n## Resources\n\n- [PostHog Status Page](https:\u002F\u002Fstatus.posthog.com)\n- [PostHog Support](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsupport)\n- [PostHog API Overview](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fapi)\n\n## Next Steps\n\nFor data handling, see `posthog-data-handling`.\n","# PostHog Incident Runbook\n\n## Overview\n\nRapid incident response for PostHog integration failures. PostHog Cloud has its own status page (status.posthog.com) — the first step is always determining whether the issue is PostHog-side or your integration.\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Analytics completely down | \u003C 15 min | All capture calls failing, feature flags returning defaults |\n| P2 | Degraded analytics | \u003C 1 hour | High latency, partial event loss, slow flag eval |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, specific event type missing |\n| P4 | No user impact | Next day | Monitoring gaps, dashboard stale data |\n\n## Quick Triage (Run First)\n\n```bash\nset -euo pipefail\necho \"=== PostHog Triage ===\"\necho \"\"\n\n# 1. Is PostHog Cloud up?\necho -n \"PostHog US Cloud: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fus.i.posthog.com\u002Fhealthz || echo \"UNREACHABLE\"\necho \"\"\n\n# 2. Can we capture events?\necho -n \"Event capture: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fcapture\u002F' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"${NEXT_PUBLIC_POSTHOG_KEY}\\\",\\\"event\\\":\\\"triage_test\\\",\\\"distinct_id\\\":\\\"triage\\\"}\" || echo \"FAILED\"\necho \"\"\n\n# 3. Can we evaluate flags?\necho -n \"Flag evaluation: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fdecide\u002F?v=3' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"${NEXT_PUBLIC_POSTHOG_KEY}\\\",\\\"distinct_id\\\":\\\"triage\\\"}\" || echo \"FAILED\"\necho \"\"\n\n# 4. Can we access admin API?\nif [ -n \"${POSTHOG_PERSONAL_API_KEY:-}\" ]; then\n  echo -n \"Admin API: \"\n  curl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \"https:\u002F\u002Fapp.posthog.com\u002Fapi\u002Fprojects\u002F\" \\\n    -H \"Authorization: Bearer $POSTHOG_PERSONAL_API_KEY\" || echo \"FAILED\"\n  echo \"\"\nfi\n\n# 5. Check our integration health\necho -n \"Our health endpoint: \"\ncurl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \"https:\u002F\u002Fyour-app.com\u002Fapi\u002Fhealth\" || echo \"UNREACHABLE\"\necho \"\"\n```\n\n## Decision Tree\n\n```\nIs PostHog Cloud healthy (status.posthog.com)?\n├── NO → PostHog outage\n│   ├── Enable graceful degradation (feature flags return defaults)\n│   ├── Monitor status.posthog.com for resolution\n│   └── Events will be lost during outage (capture is fire-and-forget)\n│\n└── YES → Our integration issue\n    ├── Are we getting 401? → API key issue (see Error 401 below)\n    ├── Are we getting 429? → Rate limited (see Error 429 below)\n    ├── Are events just not appearing? → Check flush\u002Fshutdown (see below)\n    └── Are flags returning defaults? → Check personalApiKey (see below)\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 — Authentication Failed\n\n```bash\nset -euo pipefail\n# Verify API key type and validity\necho \"Project key prefix: $(echo \"$NEXT_PUBLIC_POSTHOG_KEY\" | head -c 4)\"\necho \"Personal key prefix: $(echo \"$POSTHOG_PERSONAL_API_KEY\" | head -c 4)\"\n\n# Test project key (should return HTTP 200)\ncurl -s -o \u002Fdev\u002Fnull -w \"Capture: %{http_code}\\n\" -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fcapture\u002F' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"$NEXT_PUBLIC_POSTHOG_KEY\\\",\\\"event\\\":\\\"test\\\",\\\"distinct_id\\\":\\\"test\\\"}\"\n\n# Test personal key (should return project list)\ncurl -s -o \u002Fdev\u002Fnull -w \"Admin: %{http_code}\\n\" \"https:\u002F\u002Fapp.posthog.com\u002Fapi\u002Fprojects\u002F\" \\\n  -H \"Authorization: Bearer $POSTHOG_PERSONAL_API_KEY\"\n\n# Fix: If key is invalid, rotate in PostHog dashboard and update secrets\n```\n\n### 429 — Rate Limited\n\n```bash\nset -euo pipefail\n# PostHog rate limits (private API only):\n# - Analytics endpoints: 240\u002Fmin, 1200\u002Fhour\n# - HogQL query: 1200\u002Fhour\n# - Local flag eval polling: 600\u002Fmin\n# - Capture endpoints: NO LIMIT\n\n# Immediate: Cache API responses, reduce polling frequency\n# Long-term: See posthog-rate-limits skill\n```\n\n### Events Not Appearing\n\n```bash\nset -euo pipefail\n# Most common cause: not calling flush\u002Fshutdown in serverless\n\n# Check 1: Is capture endpoint reachable?\ncurl -s -X POST 'https:\u002F\u002Fus.i.posthog.com\u002Fcapture\u002F' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d \"{\\\"api_key\\\":\\\"$NEXT_PUBLIC_POSTHOG_KEY\\\",\\\"event\\\":\\\"debug_test\\\",\\\"distinct_id\\\":\\\"debug-$(date +%s)\\\"}\" | jq .\n# Expected: {\"status\": 1}\n\n# Check 2: Verify API host is correct (common mistake)\n# WRONG: https:\u002F\u002Fapp.posthog.com (this is the UI)\n# RIGHT: https:\u002F\u002Fus.i.posthog.com (this is the ingest endpoint)\n```\n\n### Feature Flags Returning Defaults\n\n```typescript\n\u002F\u002F Most common causes:\n\u002F\u002F 1. No personalApiKey → falls back to remote eval which may fail\n\u002F\u002F 2. Flags not loaded yet → check timing\n\u002F\u002F 3. Wrong project key → flags from different project\n\n\u002F\u002F Fix 1: Add personalApiKey\nconst posthog = new PostHog(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {\n  personalApiKey: process.env.POSTHOG_PERSONAL_API_KEY, \u002F\u002F Required for local eval\n});\n\n\u002F\u002F Fix 2: Wait for flags in browser\nposthog.onFeatureFlags(() => {\n  \u002F\u002F Now flags are loaded\n  const value = posthog.isFeatureEnabled('my-flag');\n});\n```\n\n## Graceful Degradation Pattern\n\n```typescript\n\u002F\u002F PostHog should NEVER crash your app\nfunction safeCapture(distinctId: string, event: string, props?: Record\u003Cstring, any>) {\n  try {\n    posthog.capture({ distinctId, event, properties: props });\n  } catch {\n    \u002F\u002F Swallow error — analytics failure should never impact users\n  }\n}\n\nasync function safeFlag(key: string, userId: string, fallback: boolean = false): Promise\u003Cboolean> {\n  try {\n    const result = await posthog.isFeatureEnabled(key, userId);\n    return result ?? fallback;\n  } catch {\n    return fallback; \u002F\u002F Return safe default\n  }\n}\n```\n\n## Post-Incident Evidence Collection\n\n```bash\nset -euo pipefail\nINCIDENT_DIR=\"posthog-incident-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$INCIDENT_DIR\"\n\n# Collect diagnostics\necho \"Incident: $(date -u)\" > \"$INCIDENT_DIR\u002Ftimeline.txt\"\ncurl -s https:\u002F\u002Fus.i.posthog.com\u002Fhealthz > \"$INCIDENT_DIR\u002Fhealthz.json\" 2>&1\nenv | grep -i posthog | sed 's\u002F=.*\u002F=***\u002F' > \"$INCIDENT_DIR\u002Fenv-redacted.txt\"\nnpm list posthog-js posthog-node 2>\u002Fdev\u002Fnull > \"$INCIDENT_DIR\u002Fversions.txt\"\n\ntar -czf \"$INCIDENT_DIR.tar.gz\" \"$INCIDENT_DIR\"\necho \"Evidence collected: $INCIDENT_DIR.tar.gz\"\n```\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Complete analytics outage | PostHog Cloud down | Enable graceful degradation, monitor status page |\n| Partial event loss | Serverless not flushing | Add `await posthog.shutdown()` |\n| All flags return false | `personalApiKey` missing or expired | Add\u002Frotate personal API key |\n| Admin API 401 | Personal key revoked | Generate new key in PostHog settings |\n| High latency | Network path to PostHog | Check reverse proxy, try direct connection |\n\n## Output\n\n- Triage commands identifying issue source\n- Immediate remediation for each error type\n- Graceful degradation wrappers\n- Post-incident evidence bundle\n\n## Resources\n\n- [PostHog Status Page](https:\u002F\u002Fstatus.posthog.com)\n- [PostHog Support](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsupport)\n- [PostHog API Overview](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fapi)\n\n## Next Steps\n\nFor data handling, see `posthog-data-handling`.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","posthog","incident-response","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","PostHog incident response: triage decision tree, immediate actions for\n401\u002F429\u002F500 errors, graceful degradation, evidence collection, and postmortem.\nTrigger: \"posthog incident\", \"posthog outage\", \"posthog down\",\n\"posthog on-call\", \"posthog emergency\", \"posthog broken production\".\n","Read, Grep, Bash(kubectl:*), Bash(curl:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--posthog-pack--posthog-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 posthog-incident-runbook",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill posthog-incident-runbook",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill posthog-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--posthog-pack--posthog-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",[],[]]