[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F671G9XNHZK9SXSYHHV0ME":3,"skill-same:01M6F671G9XNHZK9SXSYHHV0ME":75},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6F671G9XNHZK9SXSYHHV0ME","databricks-incident-runbook",null,"Execute Databricks incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Databricks-related outages, investigating job failures,\nor running post-incident reviews for pipeline failures.\nTrigger with phrases like \"databricks incident\", \"databricks outage\",\n\"databricks down\", \"databricks on-call\", \"databricks emergency\", \"job failed\".","Dicklesworthstone\u002Fpi_agent_rust","Dicklesworthstone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35050222?v=4","01M6CG26AR942CSVMN1M5E3DSE","Jeff Emanuel","01M6CG26EPP71PSHW1VDS71121",1992,"MIT","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fdatabricks-pack\u002Fskills\u002Fdatabricks-incident-runbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"databricks","runbook","databricks incident runbook","incident","call","running","when","down","for","reviews","with","post","trigger","io","incident response","use","execute","read","grep","postmortem","Bash","post-incident","pipeline","triage","2026-11-10 10:12:30",false,"---\nname: databricks-incident-runbook\ndescription: |\n  Execute Databricks incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Databricks-related outages, investigating job failures,\n  or running post-incident reviews for pipeline failures.\n  Trigger with phrases like \"databricks incident\", \"databricks outage\",\n  \"databricks down\", \"databricks on-call\", \"databricks emergency\", \"job failed\".\nallowed-tools: Read, Grep, Bash(databricks:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Databricks Incident Runbook\n\n## Overview\nRapid incident response procedures for Databricks-related outages.\n\n## Prerequisites\n- Access to Databricks workspace\n- CLI configured with appropriate permissions\n- Access to monitoring dashboards\n- Communication channels (Slack, PagerDuty)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Production data pipeline down | \u003C 15 min | Critical ETL failed, data not updating |\n| P2 | Degraded performance | \u003C 1 hour | Slow queries, partial failures |\n| P3 | Non-critical issues | \u003C 4 hours | Dev cluster issues, delayed non-critical jobs |\n| P4 | No user impact | Next business day | Monitoring gaps, documentation |\n\n## Quick Triage\n\n```bash\n#!\u002Fbin\u002Fbash\n# quick-triage.sh - Run this first during any incident\n\necho \"=== Databricks Quick Triage ===\"\necho \"Time: $(date)\"\necho \"\"\n\n# 1. Check Databricks status\necho \"--- Databricks Status ---\"\ncurl -s https:\u002F\u002Fstatus.databricks.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status.description'\necho \"\"\n\n# 2. Check workspace connectivity\necho \"--- Workspace Connectivity ---\"\ndatabricks workspace list \u002F --output json | jq -r '.[] | .path' | head -5\nif [ $? -eq 0 ]; then\n    echo \"Workspace: CONNECTED\"\nelse\n    echo \"Workspace: CONNECTION FAILED\"\nfi\necho \"\"\n\n# 3. Check recent job failures\necho \"--- Recent Job Failures (last 1 hour) ---\"\ndatabricks runs list --limit 20 --output json | \\\n    jq -r '.runs[] | select(.state.result_state == \"FAILED\") | \"\\(.run_id): \\(.run_name) - \\(.state.state_message)\"'\necho \"\"\n\n# 4. Check cluster status\necho \"--- Running Clusters ---\"\ndatabricks clusters list --output json | \\\n    jq -r '.clusters[] | select(.state == \"RUNNING\" or .state == \"ERROR\") | \"\\(.cluster_id): \\(.cluster_name) [\\(.state)]\"'\necho \"\"\n\n# 5. Check for errors in last hour\necho \"--- Recent Errors ---\"\n# Query system tables via SQL warehouse or notebook\n```\n\n## Decision Tree\n\n```\nJob\u002FPipeline failing?\n├─ YES: Is it a single job or multiple?\n│   ├─ SINGLE JOB → Check job-specific issues\n│   │   ├─ Cluster failed to start → Check cluster events\n│   │   ├─ Code error → Check task output\u002Flogs\n│   │   ├─ Data issue → Check source data\n│   │   └─ Permission error → Check grants\n│   │\n│   └─ MULTIPLE JOBS → Likely infrastructure issue\n│       ├─ Check Databricks status page\n│       ├─ Check workspace quotas\n│       └─ Check network connectivity\n│\n└─ NO: Is it a performance issue?\n    ├─ Slow queries → Check query plan, cluster sizing\n    ├─ Slow cluster startup → Check instance availability\n    └─ Data freshness → Check upstream pipelines\n```\n\n## Immediate Actions by Error Type\n\n### Job Failed - Code Error\n\n```bash\n# 1. Get run details\nRUN_ID=\"your-run-id\"\ndatabricks runs get --run-id $RUN_ID\n\n# 2. Get detailed error output\ndatabricks runs get-output --run-id $RUN_ID | jq '.error'\n\n# 3. Check task-level errors\ndatabricks runs get --run-id $RUN_ID | jq '.tasks[] | select(.state.result_state == \"FAILED\") | {task: .task_key, error: .state.state_message}'\n\n# 4. If notebook task, get notebook output\n# (View in UI or use jobs API to get cell outputs)\n```\n\n### Cluster Failed to Start\n\n```bash\n# 1. Check cluster events\nCLUSTER_ID=\"your-cluster-id\"\ndatabricks clusters events --cluster-id $CLUSTER_ID --limit 20\n\n# 2. Common causes and fixes\n# - QUOTA_EXCEEDED: Terminate unused clusters\n# - CLOUD_PROVIDER_LAUNCH_ERROR: Check instance availability\n# - DRIVER_UNREACHABLE: Network\u002Ffirewall issue\n\n# 3. Quick fix - restart cluster\ndatabricks clusters restart --cluster-id $CLUSTER_ID\n\n# 4. Check cluster logs\ndatabricks clusters get --cluster-id $CLUSTER_ID | jq '.termination_reason'\n```\n\n### Permission\u002FAuth Errors\n\n```bash\n# 1. Check current user\ndatabricks current-user me\n\n# 2. Check job permissions\ndatabricks permissions get jobs --job-id $JOB_ID\n\n# 3. Check table permissions (run in notebook)\n# SHOW GRANTS ON TABLE catalog.schema.table\n\n# 4. Fix: Grant necessary permissions\ndatabricks permissions update jobs --job-id $JOB_ID --json '{\n  \"access_control_list\": [{\n    \"user_name\": \"user@company.com\",\n    \"permission_level\": \"CAN_MANAGE_RUN\"\n  }]\n}'\n```\n\n### Data Quality Failures\n\n```sql\n-- Quick data quality check\nSELECT\n    COUNT(*) as total_rows,\n    COUNT(DISTINCT id) as unique_ids,\n    SUM(CASE WHEN amount IS NULL THEN 1 ELSE 0 END) as null_amounts,\n    MIN(created_at) as oldest_record,\n    MAX(created_at) as newest_record\nFROM catalog.schema.table\nWHERE created_at > current_timestamp() - INTERVAL 1 DAY;\n\n-- Check for recent changes\nDESCRIBE HISTORY catalog.schema.table LIMIT 10;\n\n-- Restore to previous version if needed\nRESTORE TABLE catalog.schema.table TO VERSION AS OF 5;\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n:red_circle: **P1 INCIDENT: [Brief Description]**\n\n**Status:** INVESTIGATING\n**Impact:** [Describe user\u002Fbusiness impact]\n**Started:** [Time]\n**Current Action:** [What you're doing now]\n**Next Update:** [Time]\n\n**Incident Commander:** @[name]\n**Thread:** [link]\n```\n\n### External (Status Page)\n```\n**Data Pipeline Delay**\n\nWe are experiencing delays in data processing. Some reports may show stale data.\n\n**Impact:** Dashboard data may be up to [X] hours delayed\n**Started:** [Time] UTC\n**Current Status:** Our team is actively investigating\n\nWe will provide updates every 30 minutes.\n\nLast updated: [Timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n\n```bash\n#!\u002Fbin\u002Fbash\n# collect-incident-evidence.sh\n\nINCIDENT_ID=$1\nRUN_ID=$2\nCLUSTER_ID=$3\n\nmkdir -p \"incident-$INCIDENT_ID\"\n\n# Job run details\ndatabricks runs get --run-id $RUN_ID > \"incident-$INCIDENT_ID\u002Frun_details.json\"\ndatabricks runs get-output --run-id $RUN_ID > \"incident-$INCIDENT_ID\u002Frun_output.json\"\n\n# Cluster info\nif [ -n \"$CLUSTER_ID\" ]; then\n    databricks clusters get --cluster-id $CLUSTER_ID > \"incident-$INCIDENT_ID\u002Fcluster_info.json\"\n    databricks clusters events --cluster-id $CLUSTER_ID --limit 50 > \"incident-$INCIDENT_ID\u002Fcluster_events.json\"\nfi\n\n# Create summary\ncat \u003C\u003C EOF > \"incident-$INCIDENT_ID\u002Fsummary.md\"\n# Incident $INCIDENT_ID\n\n**Date:** $(date)\n**Run ID:** $RUN_ID\n**Cluster ID:** $CLUSTER_ID\n\n## Evidence Collected\n- run_details.json\n- run_output.json\n- cluster_info.json\n- cluster_events.json\nEOF\n\ntar -czf \"incident-$INCIDENT_ID.tar.gz\" \"incident-$INCIDENT_ID\"\necho \"Evidence collected: incident-$INCIDENT_ID.tar.gz\"\n```\n\n### Postmortem Template\n\n```markdown\n## Incident: [Title]\n\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n**Incident Commander:** [Name]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Timeline (UTC)\n| Time | Event |\n|------|-------|\n| HH:MM | [First alert\u002Fdetection] |\n| HH:MM | [Investigation started] |\n| HH:MM | [Root cause identified] |\n| HH:MM | [Mitigation applied] |\n| HH:MM | [Incident resolved] |\n\n### Root Cause\n[Technical explanation of what went wrong]\n\n### Impact\n- **Data Impact:** [Tables affected, rows impacted]\n- **Users Affected:** [Number, types]\n- **Duration:** [How long data was unavailable\u002Fstale]\n- **Financial Impact:** [If applicable]\n\n### Detection\n- **How detected:** [Alert, user report, monitoring]\n- **Time to detect:** [Minutes from issue start]\n- **Detection gap:** [What could have caught this sooner]\n\n### Response\n- **Time to respond:** [Minutes from detection]\n- **What worked:** [Effective response actions]\n- **What didn't:** [Ineffective actions, dead ends]\n\n### Action Items\n| Priority | Action | Owner | Due Date |\n|----------|--------|-------|----------|\n| P1 | [Preventive measure] | [Name] | [Date] |\n| P2 | [Monitoring improvement] | [Name] | [Date] |\n| P3 | [Documentation update] | [Name] | [Date] |\n\n### Lessons Learned\n1. [Key learning 1]\n2. [Key learning 2]\n3. [Key learning 3]\n```\n\n## Instructions\n\n### Step 1: Quick Triage\nRun the triage script to identify the issue source.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Databricks-side or code\u002Fdata issue.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders.\n\n### Step 5: Collect Evidence\nDocument everything for postmortem.\n\n## Output\n- Issue identified and categorized\n- Remediation applied\n- Stakeholders notified\n- Evidence collected for postmortem\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't access workspace | Token expired | Re-authenticate |\n| CLI commands fail | Network issue | Check VPN |\n| Logs unavailable | Cluster terminated | Check cluster events |\n| Restore fails | Retention exceeded | Check vacuum settings |\n\n## Examples\n\n### One-Line Job Health Check\n```bash\ndatabricks runs list --job-id $JOB_ID --limit 5 --output json | \\\n    jq -r '.runs[] | \"\\(.start_time): \\(.state.result_state)\"'\n```\n\n### Quick Cluster Restart\n```bash\ndatabricks clusters restart --cluster-id $CLUSTER_ID && \\\n    echo \"Cluster restart initiated\"\n```\n\n## Resources\n- [Databricks Status Page](https:\u002F\u002Fstatus.databricks.com)\n- [Databricks Support](https:\u002F\u002Fhelp.databricks.com)\n- [Community Forum](https:\u002F\u002Fcommunity.databricks.com)\n\n## Next Steps\nFor data handling, see `databricks-data-handling`.\n","# Databricks Incident Runbook\n\n## Overview\nRapid incident response procedures for Databricks-related outages.\n\n## Prerequisites\n- Access to Databricks workspace\n- CLI configured with appropriate permissions\n- Access to monitoring dashboards\n- Communication channels (Slack, PagerDuty)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Production data pipeline down | \u003C 15 min | Critical ETL failed, data not updating |\n| P2 | Degraded performance | \u003C 1 hour | Slow queries, partial failures |\n| P3 | Non-critical issues | \u003C 4 hours | Dev cluster issues, delayed non-critical jobs |\n| P4 | No user impact | Next business day | Monitoring gaps, documentation |\n\n## Quick Triage\n\n```bash\n#!\u002Fbin\u002Fbash\n# quick-triage.sh - Run this first during any incident\n\necho \"=== Databricks Quick Triage ===\"\necho \"Time: $(date)\"\necho \"\"\n\n# 1. Check Databricks status\necho \"--- Databricks Status ---\"\ncurl -s https:\u002F\u002Fstatus.databricks.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status.description'\necho \"\"\n\n# 2. Check workspace connectivity\necho \"--- Workspace Connectivity ---\"\ndatabricks workspace list \u002F --output json | jq -r '.[] | .path' | head -5\nif [ $? -eq 0 ]; then\n    echo \"Workspace: CONNECTED\"\nelse\n    echo \"Workspace: CONNECTION FAILED\"\nfi\necho \"\"\n\n# 3. Check recent job failures\necho \"--- Recent Job Failures (last 1 hour) ---\"\ndatabricks runs list --limit 20 --output json | \\\n    jq -r '.runs[] | select(.state.result_state == \"FAILED\") | \"\\(.run_id): \\(.run_name) - \\(.state.state_message)\"'\necho \"\"\n\n# 4. Check cluster status\necho \"--- Running Clusters ---\"\ndatabricks clusters list --output json | \\\n    jq -r '.clusters[] | select(.state == \"RUNNING\" or .state == \"ERROR\") | \"\\(.cluster_id): \\(.cluster_name) [\\(.state)]\"'\necho \"\"\n\n# 5. Check for errors in last hour\necho \"--- Recent Errors ---\"\n# Query system tables via SQL warehouse or notebook\n```\n\n## Decision Tree\n\n```\nJob\u002FPipeline failing?\n├─ YES: Is it a single job or multiple?\n│   ├─ SINGLE JOB → Check job-specific issues\n│   │   ├─ Cluster failed to start → Check cluster events\n│   │   ├─ Code error → Check task output\u002Flogs\n│   │   ├─ Data issue → Check source data\n│   │   └─ Permission error → Check grants\n│   │\n│   └─ MULTIPLE JOBS → Likely infrastructure issue\n│       ├─ Check Databricks status page\n│       ├─ Check workspace quotas\n│       └─ Check network connectivity\n│\n└─ NO: Is it a performance issue?\n    ├─ Slow queries → Check query plan, cluster sizing\n    ├─ Slow cluster startup → Check instance availability\n    └─ Data freshness → Check upstream pipelines\n```\n\n## Immediate Actions by Error Type\n\n### Job Failed - Code Error\n\n```bash\n# 1. Get run details\nRUN_ID=\"your-run-id\"\ndatabricks runs get --run-id $RUN_ID\n\n# 2. Get detailed error output\ndatabricks runs get-output --run-id $RUN_ID | jq '.error'\n\n# 3. Check task-level errors\ndatabricks runs get --run-id $RUN_ID | jq '.tasks[] | select(.state.result_state == \"FAILED\") | {task: .task_key, error: .state.state_message}'\n\n# 4. If notebook task, get notebook output\n# (View in UI or use jobs API to get cell outputs)\n```\n\n### Cluster Failed to Start\n\n```bash\n# 1. Check cluster events\nCLUSTER_ID=\"your-cluster-id\"\ndatabricks clusters events --cluster-id $CLUSTER_ID --limit 20\n\n# 2. Common causes and fixes\n# - QUOTA_EXCEEDED: Terminate unused clusters\n# - CLOUD_PROVIDER_LAUNCH_ERROR: Check instance availability\n# - DRIVER_UNREACHABLE: Network\u002Ffirewall issue\n\n# 3. Quick fix - restart cluster\ndatabricks clusters restart --cluster-id $CLUSTER_ID\n\n# 4. Check cluster logs\ndatabricks clusters get --cluster-id $CLUSTER_ID | jq '.termination_reason'\n```\n\n### Permission\u002FAuth Errors\n\n```bash\n# 1. Check current user\ndatabricks current-user me\n\n# 2. Check job permissions\ndatabricks permissions get jobs --job-id $JOB_ID\n\n# 3. Check table permissions (run in notebook)\n# SHOW GRANTS ON TABLE catalog.schema.table\n\n# 4. Fix: Grant necessary permissions\ndatabricks permissions update jobs --job-id $JOB_ID --json '{\n  \"access_control_list\": [{\n    \"user_name\": \"user@company.com\",\n    \"permission_level\": \"CAN_MANAGE_RUN\"\n  }]\n}'\n```\n\n### Data Quality Failures\n\n```sql\n-- Quick data quality check\nSELECT\n    COUNT(*) as total_rows,\n    COUNT(DISTINCT id) as unique_ids,\n    SUM(CASE WHEN amount IS NULL THEN 1 ELSE 0 END) as null_amounts,\n    MIN(created_at) as oldest_record,\n    MAX(created_at) as newest_record\nFROM catalog.schema.table\nWHERE created_at > current_timestamp() - INTERVAL 1 DAY;\n\n-- Check for recent changes\nDESCRIBE HISTORY catalog.schema.table LIMIT 10;\n\n-- Restore to previous version if needed\nRESTORE TABLE catalog.schema.table TO VERSION AS OF 5;\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n:red_circle: **P1 INCIDENT: [Brief Description]**\n\n**Status:** INVESTIGATING\n**Impact:** [Describe user\u002Fbusiness impact]\n**Started:** [Time]\n**Current Action:** [What you're doing now]\n**Next Update:** [Time]\n\n**Incident Commander:** @[name]\n**Thread:** [link]\n```\n\n### External (Status Page)\n```\n**Data Pipeline Delay**\n\nWe are experiencing delays in data processing. Some reports may show stale data.\n\n**Impact:** Dashboard data may be up to [X] hours delayed\n**Started:** [Time] UTC\n**Current Status:** Our team is actively investigating\n\nWe will provide updates every 30 minutes.\n\nLast updated: [Timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n\n```bash\n#!\u002Fbin\u002Fbash\n# collect-incident-evidence.sh\n\nINCIDENT_ID=$1\nRUN_ID=$2\nCLUSTER_ID=$3\n\nmkdir -p \"incident-$INCIDENT_ID\"\n\n# Job run details\ndatabricks runs get --run-id $RUN_ID > \"incident-$INCIDENT_ID\u002Frun_details.json\"\ndatabricks runs get-output --run-id $RUN_ID > \"incident-$INCIDENT_ID\u002Frun_output.json\"\n\n# Cluster info\nif [ -n \"$CLUSTER_ID\" ]; then\n    databricks clusters get --cluster-id $CLUSTER_ID > \"incident-$INCIDENT_ID\u002Fcluster_info.json\"\n    databricks clusters events --cluster-id $CLUSTER_ID --limit 50 > \"incident-$INCIDENT_ID\u002Fcluster_events.json\"\nfi\n\n# Create summary\ncat \u003C\u003C EOF > \"incident-$INCIDENT_ID\u002Fsummary.md\"\n# Incident $INCIDENT_ID\n\n**Date:** $(date)\n**Run ID:** $RUN_ID\n**Cluster ID:** $CLUSTER_ID\n\n## Evidence Collected\n- run_details.json\n- run_output.json\n- cluster_info.json\n- cluster_events.json\nEOF\n\ntar -czf \"incident-$INCIDENT_ID.tar.gz\" \"incident-$INCIDENT_ID\"\necho \"Evidence collected: incident-$INCIDENT_ID.tar.gz\"\n```\n\n### Postmortem Template\n\n```markdown\n## Incident: [Title]\n\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n**Incident Commander:** [Name]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Timeline (UTC)\n| Time | Event |\n|------|-------|\n| HH:MM | [First alert\u002Fdetection] |\n| HH:MM | [Investigation started] |\n| HH:MM | [Root cause identified] |\n| HH:MM | [Mitigation applied] |\n| HH:MM | [Incident resolved] |\n\n### Root Cause\n[Technical explanation of what went wrong]\n\n### Impact\n- **Data Impact:** [Tables affected, rows impacted]\n- **Users Affected:** [Number, types]\n- **Duration:** [How long data was unavailable\u002Fstale]\n- **Financial Impact:** [If applicable]\n\n### Detection\n- **How detected:** [Alert, user report, monitoring]\n- **Time to detect:** [Minutes from issue start]\n- **Detection gap:** [What could have caught this sooner]\n\n### Response\n- **Time to respond:** [Minutes from detection]\n- **What worked:** [Effective response actions]\n- **What didn't:** [Ineffective actions, dead ends]\n\n### Action Items\n| Priority | Action | Owner | Due Date |\n|----------|--------|-------|----------|\n| P1 | [Preventive measure] | [Name] | [Date] |\n| P2 | [Monitoring improvement] | [Name] | [Date] |\n| P3 | [Documentation update] | [Name] | [Date] |\n\n### Lessons Learned\n1. [Key learning 1]\n2. [Key learning 2]\n3. [Key learning 3]\n```\n\n## Instructions\n\n### Step 1: Quick Triage\nRun the triage script to identify the issue source.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Databricks-side or code\u002Fdata issue.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders.\n\n### Step 5: Collect Evidence\nDocument everything for postmortem.\n\n## Output\n- Issue identified and categorized\n- Remediation applied\n- Stakeholders notified\n- Evidence collected for postmortem\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't access workspace | Token expired | Re-authenticate |\n| CLI commands fail | Network issue | Check VPN |\n| Logs unavailable | Cluster terminated | Check cluster events |\n| Restore fails | Retention exceeded | Check vacuum settings |\n\n## Examples\n\n### One-Line Job Health Check\n```bash\ndatabricks runs list --job-id $JOB_ID --limit 5 --output json | \\\n    jq -r '.runs[] | \"\\(.start_time): \\(.state.result_state)\"'\n```\n\n### Quick Cluster Restart\n```bash\ndatabricks clusters restart --cluster-id $CLUSTER_ID && \\\n    echo \"Cluster restart initiated\"\n```\n\n## Resources\n- [Databricks Status Page](https:\u002F\u002Fstatus.databricks.com)\n- [Databricks Support](https:\u002F\u002Fhelp.databricks.com)\n- [Community Forum](https:\u002F\u002Fcommunity.databricks.com)\n\n## Next Steps\nFor data handling, see `databricks-data-handling`.\n",{"name":5,"author":48,"license":15,"version":49,"description":50,"allowed-tools":51},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Databricks incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Databricks-related outages, investigating job failures,\nor running post-incident reviews for pipeline failures.\nTrigger with phrases like \"databricks incident\", \"databricks outage\",\n\"databricks down\", \"databricks on-call\", \"databricks emergency\", \"job failed\".\n","Read, Grep, Bash(databricks:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fdatabricks-pack\u002Fskills\u002Fdatabricks-incident-runbook",233,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust","https:\u002F\u002Fgithub.com\u002FDicklesworthstone","https:\u002F\u002Fwww.jeffreyemanuel.com\u002F","Building in NY","2026-11-15 01:54:15",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill databricks-incident-runbook",{"tool":67,"command":68},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill databricks-incident-runbook",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill databricks-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fdatabricks-pack\u002Fskills\u002Fdatabricks-incident-runbook\u002FSKILL.md",true,[],[76,109,143,166,192,219],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":108},"01M6FCR7G5A005P364Z6ZWCJDP","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,29,106,107],"theme factory","factory","theme","docs","toolkit","generate","artifacts","SET","fly","slides","landing","html","styling","artifact","pages","themes","you","fonts","2026-11-11 15:11:14",{"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":80,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":43},"01M6FEGPPK0ZTKCCM0R3E3KS33","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000009","前端开发",[120,121,96,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,34,101,137,138,139,140,27,141,142],"web artifacts builder","web","artifacts builder","builder","frontend","css","components","react","component","routing","state management","state","shadcn","file","ui","Tools","Tailwind","single-file","simple","ui components","multi","jsx","suite",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":154,"publishedAt":43},"01M6FEE9VTK1W4GY21AKREJXRG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":117,"categoryName":118,"taxonomyType":87,"taxonomyTypeDesc":88},[155,156,157,124,158,159,121,160,94,161,134,162,163,164,165,29,27],"testing","webapp testing","webapp","screenshots","playwright","debugging","browser","logs","applications","behavior","local",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":43},"01M6FE20F7ZTQBFWKF4MPJ2SBX","neuropixels-analysis","Neuropixels neural recording analysis. Load SpikeGLX\u002FOpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen\u002FIBL curation, AI-assisted visual analysis, for Neuropixels 1.0\u002F2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,34,182,183,184,185,186,187,188,29,189,190,191,27,25],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":202,"publishedAt":43},"01M6FDP0PDK6F1GGX395C7625Z","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FSKILL.md",[199],{"categoryNo":200,"categoryName":201,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[203,204,205,206,207,208,209,210,211,212,213,214,215,216,29,27,217,25,218],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":227,"publishedAt":43},"01M6FDM8Y7VK7NYG9SM7QPA3PW","notebooklm","Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FSKILL.md",[226],{"categoryNo":200,"categoryName":201,"taxonomyType":87,"taxonomyTypeDesc":88},[221,228,229,230,231,232,233,161,234,235,34,236,237,238,239,27,240],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source"]