Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Spark Engineer

  • 2.8k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

spark-engineer is an agent skill for writing and optimizing Apache Spark DataFrame pipelines, Spark SQL, and distributed ETL with performance tuning guidance.

About

Spark Engineer is a senior Apache Spark agent skill for high-performance distributed data processing and production ETL pipelines. The core workflow analyzes requirements, designs DataFrame pipelines with partitioning and broadcast opportunities, implements optimized transformations with caching discipline, tunes shuffle partitions and skew, and validates results against Spark UI metrics. It mandates DataFrame API over RDD for structured data, explicit schemas in production, broadcast joins for small dimension tables under 200 MB, and salting strategies for skewed keys. Code examples cover PySpark quick-start pipelines, broadcast joins, skew salting, and correct cache-unpersist patterns. Constraints forbid collect on large datasets, schema inference in production, unnecessary UDFs, and ignoring shuffle spill warnings. Output templates include complete Spark code, configuration recommendations, partitioning strategy, performance analysis, and monitoring guidance. Developers invoke it when writing Spark jobs, debugging performance issues, configuring cluster settings, processing parquet files, or building structured streaming analytics.

  • Five-step workflow from requirements through Spark UI validation and skew fixes.
  • PySpark examples include explicit schemas, broadcast joins, and skew salting.
  • MUST rules favor DataFrame API, broadcast joins, and production-scale testing.
  • Reference files cover Spark SQL, RDD ops, partitioning, tuning, and streaming.
  • Output templates include config, partitioning strategy, and UI monitoring metrics.

Spark Engineer by the numbers

  • 2,764 all-time installs (skills.sh)
  • +80 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #33 of 2,066 Data Science & ML skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

spark-engineer capabilities & compatibility

Capabilities
dataframe pipelines · broadcast joins · skew handling · partition tuning · spark sql · structured streaming · performance tuning · schema definition
Works with
aws · databricks · kafka
Use cases
data analysis · api development
From the docs

What spark-engineer says it does

Use DataFrame API over RDD for structured data processing
SKILL.md
Use broadcast joins for small dimension tables (<200MB)
SKILL.md
Check Spark UI for shuffle spill before proceeding
SKILL.md
npx skills add https://github.com/jeffallan/claude-skills --skill spark-engineer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.8k
repo stars10.8k
Security audit3 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

How do I implement and tune a Spark job without OOM, shuffle spill, or data skew on production volumes?

Write, tune, and debug Apache Spark DataFrame pipelines with explicit schemas, partitioning, broadcast joins, and skew handling.

Who is it for?

Data engineers building or debugging Spark ETL, aggregations, and structured streaming on large parquet datasets.

Skip if: Small pandas-sized datasets or teams without a Spark cluster or managed Spark runtime.

When should I use this skill?

Use when writing Spark jobs, debugging Spark performance, configuring cluster settings, processing parquet files, handling partitioning, or building structured streaming analytics.

What you get

Production-ready PySpark or Scala code with explicit schemas, partitioning plan, and Spark UI metrics to monitor.

  • optimized partition config
  • cache strategy recommendations
  • join shuffle reduction plan

By the numbers

  • Recommends 2-4 partitions per CPU core
  • Targets 128MB partition size
  • Example cluster guidance for 100 executor cores yields 200-400 partitions

Files

SKILL.mdMarkdownGitHub ↗

Spark Engineer

Senior Apache Spark engineer specializing in high-performance distributed data processing, optimizing large-scale ETL pipelines, and building production-grade Spark applications.

Core Workflow

1. Analyze requirements - Understand data volume, transformations, latency requirements, cluster resources 2. Design pipeline - Choose DataFrame vs RDD, plan partitioning strategy, identify broadcast opportunities 3. Implement - Write Spark code with optimized transformations, appropriate caching, proper error handling 4. Optimize - Analyze Spark UI, tune shuffle partitions, eliminate skew, optimize joins and aggregations 5. Validate - Check Spark UI for shuffle spill before proceeding; verify partition count with df.rdd.getNumPartitions(); if spill or skew detected, return to step 4; test with production-scale data, monitor resource usage, verify performance targets

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Spark SQL & DataFramesreferences/spark-sql-dataframes.mdDataFrame API, Spark SQL, schemas, joins, aggregations
RDD Operationsreferences/rdd-operations.mdTransformations, actions, pair RDDs, custom partitioners
Partitioning & Cachingreferences/partitioning-caching.mdData partitioning, persistence levels, broadcast variables
Performance Tuningreferences/performance-tuning.mdConfiguration, memory tuning, shuffle optimization, skew handling
Streaming Patternsreferences/streaming-patterns.mdStructured Streaming, watermarks, stateful operations, sinks

Code Examples

Quick-Start Mini-Pipeline (PySpark)

from pyspark.sql import SparkSession
from pyspark.sql import functions as F
from pyspark.sql.types import StructType, StructField, StringType, LongType, DoubleType

spark = SparkSession.builder \
    .appName("example-pipeline") \
    .config("spark.sql.shuffle.partitions", "400") \
    .config("spark.sql.adaptive.enabled", "true") \
    .getOrCreate()

# Always define explicit schemas in production
schema = StructType([
    StructField("user_id", StringType(), False),
    StructField("event_ts", LongType(), False),
    StructField("amount", DoubleType(), True),
])

df = spark.read.schema(schema).parquet("s3://bucket/events/")

result = df \
    .filter(F.col("amount").isNotNull()) \
    .groupBy("user_id") \
    .agg(F.sum("amount").alias("total_amount"), F.count("*").alias("event_count"))

# Verify partition count before writing
print(f"Partition count: {result.rdd.getNumPartitions()}")

result.write.mode("overwrite").parquet("s3://bucket/output/")

Broadcast Join (small dimension table < 200 MB)

from pyspark.sql.functions import broadcast

# Spark will automatically broadcast dim_table; hint makes intent explicit
enriched = large_fact_df.join(broadcast(dim_df), on="product_id", how="left")

Handling Data Skew with Salting

import pyspark.sql.functions as F

SALT_BUCKETS = 50

# Add salt to the skewed key on both sides
skewed_df = skewed_df.withColumn("salt", (F.rand() * SALT_BUCKETS).cast("int")) \
    .withColumn("salted_key", F.concat(F.col("skewed_key"), F.lit("_"), F.col("salt")))

other_df = other_df.withColumn("salt", F.explode(F.array([F.lit(i) for i in range(SALT_BUCKETS)]))) \
    .withColumn("salted_key", F.concat(F.col("skewed_key"), F.lit("_"), F.col("salt")))

result = skewed_df.join(other_df, on="salted_key", how="inner") \
    .drop("salt", "salted_key")

Correct Caching Pattern

# Cache ONLY when the DataFrame is reused multiple times
df_cleaned = df.filter(...).withColumn(...).cache()
df_cleaned.count()  # Materialize immediately; check Spark UI for spill

report_a = df_cleaned.groupBy("region").agg(...)
report_b = df_cleaned.groupBy("product").agg(...)

df_cleaned.unpersist()  # Release when done

Constraints

MUST DO

  • Use DataFrame API over RDD for structured data processing
  • Define explicit schemas for production pipelines
  • Partition data appropriately (200-1000 partitions per executor core)
  • Cache intermediate results only when reused multiple times
  • Use broadcast joins for small dimension tables (<200MB)
  • Handle data skew with salting or custom partitioning
  • Monitor Spark UI for shuffle, spill, and GC metrics
  • Test with production-scale data volumes

MUST NOT DO

  • Use collect() on large datasets (causes OOM)
  • Skip schema definition and rely on inference in production
  • Cache every DataFrame without measuring benefit
  • Ignore shuffle partition tuning (default 200 often wrong)
  • Use UDFs when built-in functions available (10-100x slower)
  • Process small files without coalescing (small file problem)
  • Run transformations without understanding lazy evaluation
  • Ignore data skew warnings in Spark UI

Output Templates

When implementing Spark solutions, provide: 1. Complete Spark code (PySpark or Scala) with type hints/types 2. Configuration recommendations (executors, memory, shuffle partitions) 3. Partitioning strategy explanation 4. Performance analysis (expected shuffle size, memory usage) 5. Monitoring recommendations (key Spark UI metrics to watch)

Knowledge Reference

Spark DataFrame API, Spark SQL, RDD transformations/actions, catalyst optimizer, tungsten execution engine, partitioning strategies, broadcast variables, accumulators, structured streaming, watermarks, checkpointing, Spark UI analysis, memory management, shuffle optimization

Documentation

Related skills

How it compares

Use spark-engineer for distributed PySpark cluster tuning; use data-analysis for local DuckDB queries on Excel or CSV files.

FAQ

Should production pipelines rely on schema inference?

No. Always define explicit schemas for production pipelines instead of inferring types.

When should broadcast joins be used?

Use broadcast joins for small dimension tables under 200 MB to avoid expensive shuffles.

What must be checked before calling a job done?

Check Spark UI for shuffle spill, verify partition count, and test with production-scale data volumes.

Is Spark Engineer safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Data Science & MLpipelinesanalytics

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.