debug-spark-failure
From the author
Diagnose failed Apache Spark and PySpark applications from History Server evidence, logs, and cluster-manager state. Use for driver or executor crashes, out-of-memory errors, fetch failures, task exceptions, timeouts, repeated retries, aborted stages, and intermittent production failures.
Install
npx skills add EmbrasureAI/spark-observability-skills --skill debug-spark-failure -a claude-code
Installs to .claude/skills/debug-spark-failure/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 74
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- debug-slow-spark-jobEmbrasureAI/spark-observability-skillsDiagnose slow, expensive, or regressed Apache Spark and PySpark applications by comparing runtime evidence against a healthy run. Use for long stages, stragglers, skew, shuffle, spill, garbage collection, poor parallelism, small files, slow scans, scheduler delay, executor imbalance, and unexplained compute-cost growth.Engineering★ 54
- spark-engineerJeffallan/claude-skillsUse when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure executor memory, process .parquet files, handle data partitioning, or build structured streaming analytics.Data★ 12.1K
- mini-program-debugging-skillNocodeMrLi/mini-program-engineering-skill-suiteDiagnose and fix mini-program failures through reproducible, evidence-driven root-cause analysis across source, state, asynchronous timing, caches, mock data, build versions, platform behavior, devices, cloud calls, and external services. Use when users report white screens, crashes, stale or jumping values, missing data, intermittent behavior, permission failures, performance stalls, device-only defects, API or cloud-function errors, source-versus-build mismatches, or regressions whose cause is not yet established. Freezes the observation environment, ranks competing hypotheses, runs discriminating checks, creates a failing regression test before repair, covers analogous states, and never hides a known failure with longer waits, swallowed errors, forced success, or cosmetic patches.Engineering★ 91
- pytest-triageGoldziher/ai-rulezDiagnoses failing pytest runs from the output the user pastes or the last local run. Use when tests fail and the cause is unclear; not for writing new tests.Testing★ 163
- debug-flowmicrosoft/power-platform-skillsDebug a failed Power Automate flow run. Use when a flow failed, has errors, or the user wants to troubleshoot a run.Engineering★ 1.1K
- systematic-debuggingjnMetaCode/superpowers-zh遇到任何 bug、测试失败或异常行为时使用，在提出修复方案之前执行Engineering★ 8.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in