[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT2NGYJCR4FFHC6SYTJMQ1":3,"skill-same:01M6CT2NGYJCR4FFHC6SYTJMQ1":74},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6CT2NGYJCR4FFHC6SYTJMQ1","triage",null,"Triage and diagnose Sentry issues: root cause analysis, temporal pattern detection, severity scoring, and resolution recommendations","lucid-fdn\u002Flucid-plugins","lucid-fdn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93290671?v=4","01M6CT12EHKN5DWVD9NAK6WSXT","Lucid","01M6CT12K0ARYZ8D28MK4G89F8",0,"MIT","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-observability\u002Fskill\u002Freferences\u002Ftriage\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28],"diagnose","root cause analysis","pattern detection","issues","sentry","severity","detection","analysis","scoring","pattern","2026-11-10 10:12:30",false,"---\nname: triage\ndescription: \"Triage and diagnose Sentry issues: root cause analysis, temporal pattern detection, severity scoring, and resolution recommendations\"\nrequires:\n  mcps: [sentry]\n---\n\n# Triage\n\nDiagnose and triage Sentry issues using the official Sentry MCP server.\n\n## Prerequisites\n\nYou need the **Sentry MCP server** connected. The following Sentry MCP tools are used:\n- `list_issues` — list issues by project with search syntax\n- `get_issue_details` — full issue detail with stack trace, tags, contexts\n- `list_issue_events` — event history for an issue\n- `update_issue` — resolve, ignore, or unresolve an issue\n- `search_issues` — find issues by trace ID or other criteria\n- `get_project_stats` — error rate trends over time\n\n## Sentry Projects\n\nThe Lucid platform uses these Sentry projects:\n- `lucid-web` — Next.js frontend (Vercel)\n- `lucid-worker` — Worker service (Railway\u002FFastify)\n- `lucid-l2` — L2 gateway (Railway\u002FExpress)\n- `lucid-trustgate` — Trust gate (Railway\u002FFastify)\n- `lucid-mcpgate` — MCP gate (Railway\u002FFastify)\n- `javascript-nextjs` — Next.js SSR errors\n\nSentry org: `raijin-labs`\n\n## Triage Procedure\n\n### Step 1: Get Issue Details\n\nUse Sentry MCP `get_issue_details` with the issue ID. Focus on:\n- **Stack trace**: Last 15 frames, prioritize frames marked `[in_app]`\n- **Tags**: Look for `trace_id`, `run_id`, `service`, `environment`, `release`\n- **Breadcrumbs**: Last 10 breadcrumbs for event timeline context\n- **OTel context**: Check `contexts.otel` for trace correlation\n\n### Step 2: Analyze Temporal Pattern\n\nUse Sentry MCP `list_issue_events` (limit 25) and classify the event timing pattern:\n- See [references\u002Ftemporal-patterns.md](references\u002Ftemporal-patterns.md) for the classification algorithm\n- The pattern tells you whether this is a burst (deployment?), steady (systemic), regression (reintroduced), or sporadic (edge case)\n\n### Step 3: Check Cross-Service Correlation\n\nIf the issue has `trace_id` or `run_id` tags:\n- Use Sentry MCP `search_issues` with query `trace_id:{id}` across all 6 projects\n- If errors appear in >1 service → **cascade detected** — investigate the oldest error first\n- See the [correlation skill](..\u002Fcorrelation\u002FSKILL.md) for detailed cross-service procedure\n\n### Step 4: Match Diagnosis Pattern\n\nCompare the issue title, culprit, and stack trace against known patterns:\n- Check **Lucid-specific patterns first** (see [references\u002Fdiagnosis-patterns.md](references\u002Fdiagnosis-patterns.md))\n- Then check **built-in patterns** (network, timeout, auth, rate limit, database, validation, memory)\n- Matching is case-insensitive substring match on title + culprit + stack trace text\n\n### Step 5: Check Known Bugs\n\nCompare against [references\u002Fknown-bugs.md](references\u002Fknown-bugs.md):\n- If a known bug matches and `status: FIXED`, recommend verifying the fix is deployed\n- If a known bug matches and `status: OPEN`, link to the existing fix\n\n### Step 6: Score Severity and Recommend Action\n\nUse [references\u002Fseverity-matrix.md](references\u002Fseverity-matrix.md) to score:\n- **CRITICAL** → Immediate escalation, consider rollback\n- **HIGH** → Link to deploy diff, suggest revert if post-deployment\n- **MEDIUM** → Create investigation ticket\n- **LOW** → Monitor; auto-resolve if \u003C5 occurrences\u002Fday\n\n## Issue Resolution\n\nWhen to use Sentry MCP `update_issue`:\n- **Resolve**: Root cause identified AND fix deployed AND verified in production\n- **Ignore**: Known noise (e.g., bot traffic, expected transient errors). Set duration if temporary.\n- **Unresolve**: Previously resolved but still occurring — regression detected\n\n## Error Rate Analysis\n\nUse Sentry MCP `get_project_stats` to analyze trends:\n- `stat: received` — total errors ingested\n- `stat: rejected` — errors dropped by rate limits\n- `interval: 1h` for recent spikes, `1d` for weekly trends\n- `period: 7d` or `14d` for baseline comparison\n- Compare current rate to 7-day average — >2x is a spike, >5x is an incident\n","# Triage\n\nDiagnose and triage Sentry issues using the official Sentry MCP server.\n\n## Prerequisites\n\nYou need the **Sentry MCP server** connected. The following Sentry MCP tools are used:\n- `list_issues` — list issues by project with search syntax\n- `get_issue_details` — full issue detail with stack trace, tags, contexts\n- `list_issue_events` — event history for an issue\n- `update_issue` — resolve, ignore, or unresolve an issue\n- `search_issues` — find issues by trace ID or other criteria\n- `get_project_stats` — error rate trends over time\n\n## Sentry Projects\n\nThe Lucid platform uses these Sentry projects:\n- `lucid-web` — Next.js frontend (Vercel)\n- `lucid-worker` — Worker service (Railway\u002FFastify)\n- `lucid-l2` — L2 gateway (Railway\u002FExpress)\n- `lucid-trustgate` — Trust gate (Railway\u002FFastify)\n- `lucid-mcpgate` — MCP gate (Railway\u002FFastify)\n- `javascript-nextjs` — Next.js SSR errors\n\nSentry org: `raijin-labs`\n\n## Triage Procedure\n\n### Step 1: Get Issue Details\n\nUse Sentry MCP `get_issue_details` with the issue ID. Focus on:\n- **Stack trace**: Last 15 frames, prioritize frames marked `[in_app]`\n- **Tags**: Look for `trace_id`, `run_id`, `service`, `environment`, `release`\n- **Breadcrumbs**: Last 10 breadcrumbs for event timeline context\n- **OTel context**: Check `contexts.otel` for trace correlation\n\n### Step 2: Analyze Temporal Pattern\n\nUse Sentry MCP `list_issue_events` (limit 25) and classify the event timing pattern:\n- See [references\u002Ftemporal-patterns.md](references\u002Ftemporal-patterns.md) for the classification algorithm\n- The pattern tells you whether this is a burst (deployment?), steady (systemic), regression (reintroduced), or sporadic (edge case)\n\n### Step 3: Check Cross-Service Correlation\n\nIf the issue has `trace_id` or `run_id` tags:\n- Use Sentry MCP `search_issues` with query `trace_id:{id}` across all 6 projects\n- If errors appear in >1 service → **cascade detected** — investigate the oldest error first\n- See the [correlation skill](..\u002Fcorrelation\u002FSKILL.md) for detailed cross-service procedure\n\n### Step 4: Match Diagnosis Pattern\n\nCompare the issue title, culprit, and stack trace against known patterns:\n- Check **Lucid-specific patterns first** (see [references\u002Fdiagnosis-patterns.md](references\u002Fdiagnosis-patterns.md))\n- Then check **built-in patterns** (network, timeout, auth, rate limit, database, validation, memory)\n- Matching is case-insensitive substring match on title + culprit + stack trace text\n\n### Step 5: Check Known Bugs\n\nCompare against [references\u002Fknown-bugs.md](references\u002Fknown-bugs.md):\n- If a known bug matches and `status: FIXED`, recommend verifying the fix is deployed\n- If a known bug matches and `status: OPEN`, link to the existing fix\n\n### Step 6: Score Severity and Recommend Action\n\nUse [references\u002Fseverity-matrix.md](references\u002Fseverity-matrix.md) to score:\n- **CRITICAL** → Immediate escalation, consider rollback\n- **HIGH** → Link to deploy diff, suggest revert if post-deployment\n- **MEDIUM** → Create investigation ticket\n- **LOW** → Monitor; auto-resolve if \u003C5 occurrences\u002Fday\n\n## Issue Resolution\n\nWhen to use Sentry MCP `update_issue`:\n- **Resolve**: Root cause identified AND fix deployed AND verified in production\n- **Ignore**: Known noise (e.g., bot traffic, expected transient errors). Set duration if temporary.\n- **Unresolve**: Previously resolved but still occurring — regression detected\n\n## Error Rate Analysis\n\nUse Sentry MCP `get_project_stats` to analyze trends:\n- `stat: received` — total errors ingested\n- `stat: rejected` — errors dropped by rate limits\n- `interval: 1h` for recent spikes, `1d` for weekly trends\n- `period: 7d` or `14d` for baseline comparison\n- Compare current rate to 7-day average — >2x is a spike, >5x is an incident\n",{"name":5,"requires":34,"description":7},{"mcps":35},[23],"main","60a187a694df4ce725464b7578e08ad46a73340f","lucid-observability\u002Fskill\u002Freferences\u002Ftriage","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins","https:\u002F\u002Fgithub.com\u002Flucid-fdn","2026-03-26 06:06:06",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add lucid-fdn\u002Flucid-plugins --skill triage",{"tool":48,"command":49},"bunx","bunx skills add lucid-fdn\u002Flucid-plugins --skill triage",{"tool":51,"command":52},"pnpm","pnpm dlx skills add lucid-fdn\u002Flucid-plugins --skill triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-observability\u002Fskill\u002Freferences\u002Ftriage\u002FSKILL.md",true,[56,62,66,70],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fdiagnosis-patterns.md","REFERENCE","参考文档",4164,"https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-observability\u002Fskill\u002Freferences\u002Ftriage\u002Freferences\u002Fdiagnosis-patterns.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fknown-bugs.md",908,"https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-observability\u002Fskill\u002Freferences\u002Ftriage\u002Freferences\u002Fknown-bugs.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fseverity-matrix.md",1503,"https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-observability\u002Fskill\u002Freferences\u002Ftriage\u002Freferences\u002Fseverity-matrix.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ftemporal-patterns.md",1744,"https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-observability\u002Fskill\u002Freferences\u002Ftriage\u002Freferences\u002Ftemporal-patterns.md",[75,84,109,121,137,156],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":29},"01M6CT442ZA942TW2E4GM9B47B","lucid-PLUGIN_NAME","PLUGIN_DESCRIPTION","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Ftemplates\u002Fplugin-template\u002Fdocs\u002FSKILL.md",[],[82,83],"lucid PLUGIN NAME","plugin",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":100,"publishedAt":29},"01M6CT41PA1EKESRMFV5V775TW","social-content","Generate short-form video content optimized for social media platforms","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-video\u002Fskill\u002Freferences\u002Fsocial-content\u002FSKILL.md",[90,95],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[101,102,103,104,105,106,107,108],"social","social content","content","short","social media","Media","Video","generate",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":29},"01M6CT3Z4SPEJQYJNZ60ZBDKMF","personalized-outreach","Generate 1:1 personalized video for sales prospecting and customer success","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-video\u002Fskill\u002Freferences\u002Fpersonalized-outreach\u002FSKILL.md",[115],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[117,108,118,107,119,120],"personalized outreach","sales","prospecting","customer",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":29},"01M6CT3WH4C1TMMSWY25XBEM19","data-reports","Generate animated data report videos from KPIs, charts, and analytics","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-video\u002Fskill\u002Freferences\u002Fdata-reports\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000033","数据分析师",[131,132,133,134,135,108,136],"data","data reports","reports","Charts","report","analytics",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":147,"publishedAt":29},"01M6CT3TJTWDVGM0CY356RS99V","lucid-video","Agent-native video generation using Remotion — MCP server + OpenClaw plugin","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-video\u002Fskill\u002FSKILL.md",[143,144],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":145,"categoryName":146,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,107,149,150,151,152,153,154,155,83],"lucid video","server","MCP","openclaw","mcp server","openclaw plugin","video generation","Remotion",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":29},"01M6CT3RP3ZWEJBA5Q3X8J4XV4","lucid-veille","Content monitoring, AI digest generation, and multi-platform auto-publishing","https:\u002F\u002Fgithub.com\u002Flucid-fdn\u002Flucid-plugins\u002Fblob\u002Fmain\u002Flucid-veille\u002Fskill\u002Freferences\u002Flucid-veille\u002FSKILL.md",[],[163,164,165,166,167,168,103],"lucid veille","supabase","monitoring","auto","publishing","digest"]