[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M752GGAHJSG7KFV8370R4M15":3,"skill-same:01M752GGAHJSG7KFV8370R4M15":55},{"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":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M752GGAHJSG7KFV8370R4M15","langfuse-incident-runbook",null,"Troubleshoot and respond to Langfuse-related incidents and outages.\nUse when experiencing Langfuse outages, debugging production issues,\nor responding to LLM observability incidents.\nTrigger with phrases like \"langfuse incident\", \"langfuse outage\",\n\"langfuse down\", \"langfuse production issue\", \"langfuse troubleshoot\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Flangfuse-incident-runbook\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: langfuse-incident-runbook\ndescription: |\n  Troubleshoot and respond to Langfuse-related incidents and outages.\n  Use when experiencing Langfuse outages, debugging production issues,\n  or responding to LLM observability incidents.\n  Trigger with phrases like \"langfuse incident\", \"langfuse outage\",\n  \"langfuse down\", \"langfuse production issue\", \"langfuse troubleshoot\".\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\n---\n# Langfuse Incident Runbook\n\n## Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nStep-by-step procedures for responding to Langfuse-related incidents, from initial triage through resolution and post-incident review.\n\n## Prerequisites\n- Access to Langfuse dashboard\n- Application logs access\n- Metrics\u002Fmonitoring dashboards\n- Escalation contacts\n\n## Instructions\n\n### Step 1: Initial Assessment (2 minutes)\nRun the quick diagnosis script: check Langfuse status page, API connectivity, auth test, and application metrics.\n\n### Step 2: Determine Incident Type\n| Symptom | Likely Cause | Action |\n|---------|--------------|--------|\n| No traces appearing | SDK not flushing | Check shutdown handlers, reduce batch size |\n| 401\u002F403 errors | Auth issue | Verify keys match project, check rotation |\n| High latency | Rate limits | Increase batching, implement circuit breaker |\n| Missing data | Partial failures | Ensure spans end in `finally` blocks |\n| Complete outage | Langfuse service | Enable fallback, queue locally |\n\n### Step 3: Apply Resolution\nFollow the section-specific resolution steps. For outages, activate graceful degradation mode.\n\n### Step 4: Post-Incident Review\nVerify traces appearing, check error rates normalized, schedule post-mortem for P1\u002FP2.\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Output\n- Incident severity classified\n- Root cause identified\n- Resolution applied\n- Post-incident checklist completed\n\n## Error Handling\n| Severity | Description | Response Time |\n|----------|-------------|---------------|\n| P1 | Complete outage | 15 min |\n| P2 | Degraded, partial loss | 1 hour |\n| P3 | Slow\u002Fdelayed traces | 4 hours |\n| P4 | Minor issues | 24 hours |\n\n## Examples\n\n### Escalation Contacts\n| Level | Contact | When |\n|-------|---------|------|\n| L1 | On-call engineer | All incidents |\n| L2 | Platform team lead | P1\u002FP2 unresolved 30min |\n| L3 | Langfuse support | Service-side issues |\n\n## Resources\n- [Langfuse Status](https:\u002F\u002Fstatus.langfuse.com)\n- [Langfuse Discord](https:\u002F\u002Flangfuse.com\u002Fdiscord)\n- [Langfuse GitHub Issues](https:\u002F\u002Fgithub.com\u002Flangfuse\u002Flangfuse\u002Fissues)","# Langfuse Incident Runbook\n\n## Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nStep-by-step procedures for responding to Langfuse-related incidents, from initial triage through resolution and post-incident review.\n\n## Prerequisites\n- Access to Langfuse dashboard\n- Application logs access\n- Metrics\u002Fmonitoring dashboards\n- Escalation contacts\n\n## Instructions\n\n### Step 1: Initial Assessment (2 minutes)\nRun the quick diagnosis script: check Langfuse status page, API connectivity, auth test, and application metrics.\n\n### Step 2: Determine Incident Type\n| Symptom | Likely Cause | Action |\n|---------|--------------|--------|\n| No traces appearing | SDK not flushing | Check shutdown handlers, reduce batch size |\n| 401\u002F403 errors | Auth issue | Verify keys match project, check rotation |\n| High latency | Rate limits | Increase batching, implement circuit breaker |\n| Missing data | Partial failures | Ensure spans end in `finally` blocks |\n| Complete outage | Langfuse service | Enable fallback, queue locally |\n\n### Step 3: Apply Resolution\nFollow the section-specific resolution steps. For outages, activate graceful degradation mode.\n\n### Step 4: Post-Incident Review\nVerify traces appearing, check error rates normalized, schedule post-mortem for P1\u002FP2.\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Output\n- Incident severity classified\n- Root cause identified\n- Resolution applied\n- Post-incident checklist completed\n\n## Error Handling\n| Severity | Description | Response Time |\n|----------|-------------|---------------|\n| P1 | Complete outage | 15 min |\n| P2 | Degraded, partial loss | 1 hour |\n| P3 | Slow\u002Fdelayed traces | 4 hours |\n| P4 | Minor issues | 24 hours |\n\n## Examples\n\n### Escalation Contacts\n| Level | Contact | When |\n|-------|---------|------|\n| L1 | On-call engineer | All incidents |\n| L2 | Platform team lead | P1\u002FP2 unresolved 30min |\n| L3 | Langfuse support | Service-side issues |\n\n## Resources\n- [Langfuse Status](https:\u002F\u002Fstatus.langfuse.com)\n- [Langfuse Discord](https:\u002F\u002Flangfuse.com\u002Fdiscord)\n- [Langfuse GitHub Issues](https:\u002F\u002Fgithub.com\u002Flangfuse\u002Flangfuse\u002Fissues)",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Troubleshoot and respond to Langfuse-related incidents and outages.\nUse when experiencing Langfuse outages, debugging production issues,\nor responding to LLM observability incidents.\nTrigger with phrases like \"langfuse incident\", \"langfuse outage\",\n\"langfuse down\", \"langfuse production issue\", \"langfuse troubleshoot\".\n","Read, Write, Edit, Bash(curl:*)","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill langfuse-incident-runbook",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill langfuse-incident-runbook",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill langfuse-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Flangfuse-incident-runbook\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fimplementation.md","REFERENCE","参考文档",3595,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Flangfuse-incident-runbook\u002Freferences\u002Fimplementation.md",[56,63,70,77,84,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]