Agent skill

Pyspark Etl

by Mindrally in Mindrally/skills

Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg.

Apache-2.0Auto-check passedData & Analytics

Install Pyspark Etl

skills CLI
$ npx skills add Mindrally/skills --skill pyspark-etl -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Mindrally/skills pyspark-etl --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pyspark-etl .claude/skills/pyspark-etl && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pyspark-etl
GitHub stars
271
Token cost
~2.5k tokens
SKILL.md length
853 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
Apache-2.0

At a glance

Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg.

  • Works in 8 steps: Scaffold the job class — Create a class… → Define config via a factory function —… → Read source data with a shared,… → …
  • Reviewing PySpark jobs
  • SKILL.md covers Workflow for Building a…, Project Structure, Code Style and Joins, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pyspark Etl is an agent skill from Mindrally/skills. Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg. Use when writing or reviewing PySpark jobs, designing joins and window functions, working with map/array higher-order functions, or building idempotent cumulative/snapshot table merges.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Data & Analytics, covering Data pipelines and ETL and SQL. It works with Apache Spark. The repository describes itself as: 265+ Claude Code skills for every major framework and language. Install with: npx skills add Mindrally/skills. The licence is Apache-2.0.

When your agent uses it

  • Reviewing PySpark jobs
  • Designing joins and window functions
  • Working with map/array higher-order functions
  • Building idempotent cumulative/snapshot table merges

Example prompts

  • “/pyspark-etl”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Scaffold the job class — Create a class that manages the SparkSession lifecycle, accepts an injectable session for testing, and exposes an…
  2. Define config via a factory function — Keep config as a plain dataclass; parse CLI args in a separate factory function so tests can…
  3. Read source data with a shared, partition-aware reader — Use a generic reader utility for date filters, hour ranges, and latest-partition…
  4. Compose the pipeline with .transform() — Chain named methods (read_source().transform(self.enrich).transform(self.merge_with_existing)) so…
  5. Apply transformations idiomatically — Use select over withColumn chains, explicit join types, explicit window frames, and native functions…
  6. Write with schema-evolution safety — Use .byName() when writing to Iceberg tables so column order doesn't matter.
  7. Validate output — Check primary-key uniqueness and null counts on key columns after every write.
  8. Test locally — Unit test transformation methods against a local SparkSession with small, hand-built DataFrames.

What it can do on your machine

Read from SKILL.md and the folder at commit 7682ca7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pyspark Etl loads about 2.5k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 853 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Mindrally/skills at commit 7682ca7, republished under its Apache-2.0 licence (© Mindrally). 853 words, ~2,458 tokens.

Download SKILL.mdSave it as .claude/skills/pyspark-etl/SKILL.md (or your agent's skills folder).
name
pyspark-etl
description
Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg. Use when writing or reviewing PySpark jobs, designing joins and window functions, working with map/array higher-order functions, or building idempotent cumulative/snapshot table merges.
metadata.maintainer
Mindrally
metadata.source
https://github.com/Mindrally/skills

PySpark ETL

This skill covers patterns for building production-grade, testable ETL pipelines with PySpark, Spark SQL, and Apache Iceberg, including project structure, join and window-function idioms, and safe cumulative-table merge patterns.

Workflow for Building a PySpark ETL Job

  1. Scaffold the job class — Create a class that manages the SparkSession lifecycle, accepts an injectable session for testing, and exposes an abstract run_job method.
  2. Define config via a factory function — Keep config as a plain dataclass; parse CLI args in a separate factory function so tests can construct configs without touching sys.argv.
  3. Read source data with a shared, partition-aware reader — Use a generic reader utility for date filters, hour ranges, and latest-partition lookups; keep business filters in the ETL class.
  4. Compose the pipeline with .transform() — Chain named methods (read_source().transform(self.enrich).transform(self.merge_with_existing)) so run_job stays pure orchestration.
  5. Apply transformations idiomatically — Use select over withColumn chains, explicit join types, explicit window frames, and native functions instead of UDFs.
  6. Write with schema-evolution safety — Use .byName() when writing to Iceberg tables so column order doesn't matter.
  7. Validate output — Check primary-key uniqueness and null counts on key columns after every write.
  8. Test locally — Unit test transformation methods against a local SparkSession with small, hand-built DataFrames.

Project Structure

ETL class scaffold
python
from abc import ABC, abstractmethod
import logging
from pyspark.sql import SparkSession

class BaseETL(ABC):
    def __init__(self, config, app_name="ETL Job", spark_session=None):
        self.spark = spark_session or SparkSession.builder.appName(app_name).getOrCreate()
        self.config = config
        self.logger = logging.getLogger(self.__class__.__name__)

    @abstractmethod
    def run_job(self): ...

    def stop(self):
        self.spark.stop()
Config as a factory function

Keep the dataclass as pure data; put CLI parsing in a standalone factory so configs are easy to build in tests.

python
import argparse
from dataclasses import dataclass

@dataclass
class MyConfig:
    read_date: int = 20260101

def create_config() -> MyConfig:
    parser = argparse.ArgumentParser()
    parser.add_argument("--read_date", type=int, default=20260101)
    args = parser.parse_args()
    return MyConfig(read_date=args.read_date)
Partition-aware shared reader

Build one generic reader for partition mechanics; keep domain-specific filters visible in the ETL, not buried in a one-off reader class.

python
import pyspark.sql.functions as F

class PartitionedReader:
    @staticmethod
    def read_latest(spark, table_name, partition_col):
        row = spark.read.table(table_name).agg(F.max(partition_col)).first()
        if row is None or row[0] is None:
            return spark.createDataFrame([], spark.read.table(table_name).schema)
        return spark.read.table(table_name).filter(F.col(partition_col) == row[0])

    @staticmethod
    def read_by_date(spark, table_name, partition_col, date_value):
        return spark.read.table(table_name).filter(F.col(partition_col) == date_value)

events = PartitionedReader.read_by_date(spark, "catalog.my_table", "event_date", 20260319)
events = events.filter(F.col("event_type").isin("login", "purchase"))

Code Style

  • Import functions as import pyspark.sql.functions as F and always use F.col() instead of df.colA attribute access — attribute access binds a column to a specific DataFrame variable and breaks after joins or reassignment.
  • Extract complex boolean logic inside .filter() or F.when() into named variables once it exceeds 3 expressions.
  • Prefer select over chains of withColumn — select states the output schema in one pass, while each withColumn call adds a projection to the query plan.
  • Use .alias() instead of withColumnRenamed.
  • Limit chained method calls to 5 per statement; separate select/filter chains from withColumn chains from join chains by operation type.
python
# BAD — 3 intermediate DataFrames, one projection per call
df = df.withColumn("a", F.col("a").cast("double"))
df = df.withColumn("b", F.upper(F.col("b")))
df = df.withColumn("c", F.lit(1))

# GOOD — one DataFrame, explicit schema contract
df = df.select(
    F.col("a").cast("double"),
    F.upper(F.col("b")).alias("b"),
    F.lit(1).alias("c"),
)

Joins

  • Always specify how= explicitly — never rely on the default.
  • Prefer left joins over right joins for readability; flip DataFrame order instead of using how="right".
  • Alias whole DataFrames for disambiguation after joins rather than renaming every column with withColumnRenamed.
  • Wrap small dimension/lookup tables in F.broadcast() when joining against a large fact table, especially after filters or transformations that prevent Spark from inferring the size automatically (spark.sql.autoBroadcastJoinThreshold only auto-broadcasts tables Spark can size, typically under 10MB). Confirm with df.explain() — look for BroadcastHashJoin vs SortMergeJoin.
  • Never reach for .dropDuplicates() to mask unexpected duplicate rows — find the root cause; it also adds shuffle overhead.
python
flights = flights.alias("f")
parking = parking.alias("p")
result = flights.join(F.broadcast(parking), "code", how="left").select(
    F.col("f.start_time").alias("flight_start"),
    F.col("p.total_time").alias("parking_total"),
)

Window Functions

Use from pyspark.sql import Window as W.

  • Always specify an explicit frame — without one, F.sum().over(w) behaves differently depending on whether orderBy is present (running sum vs. total).
  • Know the difference between row_number() + filter (drops rows, keeps the best one) and first() over a window (overwrites a column, keeps all rows).
  • Pass ignorenulls=True to F.first()/F.last() — otherwise a null in the first row of a partition nulls the entire partition's result.
  • Avoid empty partitionBy(); it forces all data into a single partition. Use .agg() for global aggregations instead.
python
w = W.partitionBy("key").orderBy("num").rowsBetween(W.unboundedPreceding, W.unboundedFollowing)
df = df.withColumn("version", F.first("version", ignorenulls=True).over(w))
Show full SKILL.md (305 more words)Show less

Map & Array Higher-Order Functions

  • Use map_zip_with instead of map_concat when merging maps needs per-key conflict resolution (e.g., keep the entry with the later timestamp) rather than one side blindly winning.
  • Use transform + array_max/array_min to extract values out of nested structs without a UDF.
  • Avoid UDFs — check for a built-in Spark function or higher-order function first. UDFs break Catalyst optimization and add serialization overhead.
python
merged = F.map_zip_with(
    new_map, existing_map,
    lambda key, v1, v2: (
        F.when(v1.isNull(), v2)
        .when(v2.isNull(), v1)
        .otherwise(F.when(v1.event_ts >= v2.event_ts, v1).otherwise(v2))
    ),
)

Cumulative / Snapshot Table Patterns

  • Merges must be idempotent — re-running with the same input data must not create duplicates.
  • Merges must be order-independent — backfilling old data must never overwrite newer data. Resolve conflicts with an explicit criterion (event timestamp, version number, partition date), never positional precedence like coalesce argument order.
  • Validate primary-key uniqueness and null counts on key columns as an audit step after every write.

Data Quality & Performance

  • Use F.lit(None) for empty columns — never empty strings or sentinel values like "NA".
  • Avoid .otherwise() as a catch-all in F.when() chains for categorical mappings; an unmapped value should surface as null, not silently collapse into "Other".
  • Never leave .show(), .collect(), or .printSchema() in production code — they force full materialization or add driver overhead. .count() is fine when used intentionally for row-count logging or to force materialization before a DAG fork.
  • Use .persist() only when a DataFrame is referenced by multiple subsequent actions. Choose the storage level deliberately: MEMORY_AND_DISK (safe default), MEMORY_ONLY (fastest, risks recompute on eviction), DISK_ONLY (for DataFrames too large for memory).

Iceberg Write Patterns

  • Use .byName() when writing so Spark matches columns by name, not position — this keeps writes safe across schema evolution.
python
df.write.byName().mode("overwrite").insertInto("catalog.my_table")
  • Use the __partitions Iceberg metadata table to find the latest snapshot instead of scanning the full table:
python
partition_df = spark.read.table("catalog.my_table__partitions").select(
    "partition.partition_date", "partition.partition_hour"
)
max_partition = partition_df.orderBy(
    F.col("partition_date").desc(), F.col("partition_hour").desc()
).first()
if max_partition is None:
    raise ValueError("No partitions found in catalog.my_table")
  • Choose write.distribution-mode deliberately: "none" (fastest, no re-shuffle, file sizes depend on upstream partitioning), "hash" (shuffles by partition key for evenly sized files), "range" (sorts before writing, best scan performance but most expensive).

© Mindrally, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in pyspark-etl of Mindrally/skills.

Open the folder on GitHubat commit 7682ca7

Compare with similar skills

Pyspark Etl next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pyspark Etl compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pyspark Etl this skillMindrally/skills271—~2.5kAutomated safety check: PassApache-2.0
Apache Spark EngineerJeffallan/claude-skills12k1 repos~1.7kAutomated safety check: PassMIT
Optimizing Databricks SQLAltimateAI/data-engineering-skills128—~6.7kAutomated safety check: PassMIT
Migrate Glue Devendpoint To Interactive Sessionsaws-samples/aws-glue-samples1.5k—~3.6kAutomated safety check: PassMIT-0
Datafusion Pythonapache/datafusion-python607—~7.8kAutomated safety check: PassApache-2.0
Dinobase Business Data Querieskappa90/dinobase263—~1.5kAutomated safety check: PassCustom licence

Similar skills

  • Apache Spark Engineer

    Jeffallan/claude-skills

    Guides writing and tuning Apache Spark jobs: DataFrame and RDD code, Spark SQL, partitioning, caching, shuffle tuning and structured streaming.

    12k GitHub starsUsed in 1 repo~1.7k tokens
    Data & AnalyticsAuto-check passed
  • Optimizing Databricks SQL

    AltimateAI/data-engineering-skills

    Analyze DBSQL queries, including SQL embedded in notebooks (spark.sql(...), %sql cells), for anti-patterns, lint issues, and performance problems, using Databricks-specific dialect and platform…

    128 GitHub stars~6.7k tokensUpdated 3 days ago
    DatabasesAuto-check passed
  • Official

    Migrate a legacy AWS Glue development endpoint to a Glue interactive session, following the official AWS migration checklist.

    1.5k GitHub stars~3.6k tokensUpdated 1 mo ago
    Data & AnalyticsAuto-check passed
  • Datafusion Python

    apache/datafusion-python

    A skill your agent uses when the user is writing datafusion-python (Apache DataFusion Python bindings) DataFrame or SQL code.

    607 GitHub stars~7.8k tokensUpdated 2 days ago
    Data & AnalyticsAuto-check passed
  • Sets up Dinobase, a local DuckDB database that syncs data from 100+ business sources, then answers questions across them with SQL joins and previewed write-backs.

    263 GitHub stars~1.5k tokensUpdated 3 mo ago
    Data & AnalyticsAuto-check passed
  • dbt Model Builder

    AltimateAI/data-engineering-skills

    Creates or modifies dbt models in line with a project's own conventions, then runs dbt build and dbt show to check the output instead of stopping at compile.

    128 GitHub stars~890 tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed

More from Mindrally/skills

All 34 skills in this repo
  • Analytics Data Analysis

    Mindrally/skills

    Best practices for analytics, data analysis, and visualization using Python, pandas, matplotlib, seaborn, and Jupyter notebooks.

    271 GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed
  • Best practices for AutoML and hyperparameter search with Optuna, Ray Tune, and PyCaret, covering search-space design, validation splits, and leakage prevention.

    271 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed
  • Blender Python Addon

    Mindrally/skills

    Best practices for writing Blender Python add-ons using the bpy API, covering operators, panels, properties, registration, and API-safe scripting.

    271 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed
  • Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices.

    271 GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed
  • Clean Code

    Mindrally/skills

    Clean, maintainable, human-readable code principles combined with anti-over-engineering discipline: naming, single responsibility, DRY, and scoping changes to exactly what was requested.

    271 GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed
  • Design Systems

    Mindrally/skills

    Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries.

    271 GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Pyspark Etl

What does Pyspark Etl do?

Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg. Pyspark Etl is an agent skill from Mindrally/skills. Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg.

When should I use Pyspark Etl?

Pyspark Etl fits situations like: reviewing PySpark jobs; designing joins and window functions; working with map/array higher-order functions; building idempotent cumulative/snapshot table merges.

How do I install Pyspark Etl in Claude Code?

Run `npx skills add Mindrally/skills --skill pyspark-etl -a claude-code`. Or copy the skill folder (pyspark-etl in Mindrally/skills) into .claude/skills/pyspark-etl in your project. Claude Code loads it when a task matches its description.

How do I install Pyspark Etl in Codex?

Run `npx skills add Mindrally/skills --skill pyspark-etl -a codex`. Or copy the skill folder (pyspark-etl in Mindrally/skills) into .agents/skills/pyspark-etl in your project. Codex loads it when a task matches its description.

Can I use Pyspark Etl in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mindrally/skills --skill pyspark-etl -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pyspark-etl, .gemini/skills/pyspark-etl, .github/skills/pyspark-etl and .opencode/skills/pyspark-etl in your project.

What does Pyspark Etl need to run?

SKILL.md names no scripts, command-line tools or credentials: Pyspark Etl is instructions for the agent only. Our summary lists: Python 3.

Does Pyspark Etl access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pyspark Etl safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pyspark Etl use?

Pyspark Etl is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pyspark Etl use?

About 2.5k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pyspark Etl?

Skills that share tags, products or a category with Pyspark Etl: Apache Spark Engineer (Jeffallan/claude-skills, 12k stars), Optimizing Databricks SQL (AltimateAI/data-engineering-skills, 128 stars), Migrate Glue Devendpoint To Interactive Sessions (aws-samples/aws-glue-samples, 1.5k stars) and Datafusion Python (apache/datafusion-python, 607 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pyspark Etl?

Mindrally (a GitHub organization) maintains it in Mindrally/skills, which has 271 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 8, 2026.

Source: Mindrally/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.