Agent skill · Backend & API

databricks-cluster-forensics

Diagnose broken or unexplained Databricks compute — slow cold starts, failed cluster launches, Photon paying its premium without the speedup, DBR-upgrade landmines, and spot-interruption shuffle aborts — by correlating a cluster's live event stream across API surfaces. Use when a Databricks cluster won't start, died mid-run, is randomly slow to start, when planning a Databricks Runtime upgrade, or when a job keeps failing on spot loss. Trigger with "databricks cluster won't start", "cluster failed", "why is my cluster slow", "NPIP_TUNNEL_SETUP_FAILURE", "databricks runtime upgrade", "photon

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-codecan modify filesships scriptsMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill databricks-cluster-forensics --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 16
SKILL.md size: 13 KB
Bundled scripts: yes
Version: 2.27.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(databricks:*)Bash(jq:*)Bash(python3:*)Bash(bash:*)Globmcp__databricks-workspace-mcp__clusters_getmcp__databricks-workspace-mcp__clusters_eventsmcp__databricks-workspace-mcp__clusters_list
Requires: Designed for Claude Code, also compatible with Codex
Path: skills/.curated/databricks-cluster-forensics/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Databricks Cluster Forensics The operational SRE spine of the pack — what a Databricks engineer reaches for at 2 AM when the compute layer is broken or unexplained. It correlates a cluster's live event stream across API surfaces to name the failure with its **actual error code** and its **version-specific mitigation**, not "network problem, try again". ## Overview Six real compute-layer failures

More from claude-code-plugins-plus-skills
All skills →
building-automl-pipelinesBuild automated machine learning pipelines with feature engineering, model selection, and…Data & Analyticsprocessing-computer-vision-tasksProcess images using object detection, classification, and segmentation. Use when requesting…AI & Agentsvalidating-ai-ethics-and-fairnessValidate AI/ML models and datasets for bias, fairness, and ethical concerns. Use when auditing AI…AI & Agentsorchestrating-multi-agent-systemsExecute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers.…Workflow & Productivityrunning-clustering-algorithmsAnalyze datasets by running clustering algorithms (K-means, DBSCAN, hierarchical) to identify data…Data & Analyticspreprocessing-data-with-automated-pipelinesProcess automate data cleaning, transformation, and validation for ML tasks. Use when requesting…Data & Analytics
About this skill
What does the databricks-cluster-forensics skill do?

Diagnose broken or unexplained Databricks compute — slow cold starts, failed cluster launches, Photon paying its premium without the speedup, DBR-upgrade landmines, and spot-interruption shuffle aborts — by correlating a cluster's live event stream across API surfaces. Use when a Databricks cluster won't start, died mid-run, is randomly slow to start, when planning a Databricks Runtime upgrade, or when a job keeps failing on spot loss. Trigger with "databricks cluster won't start", "cluster failed", "why is my cluster slow", "NPIP_TUNNEL_SETUP_FAILURE", "databricks runtime upgrade", "photon

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill databricks-cluster-forensics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.