apache-spark-data-processing — Claude Code skill for Apache Spark
A skill that feeds your agent working knowledge of Apache Spark: RDDs, DataFrames, Spark SQL, streaming, MLlib and production deployment.
npx skills add manutej/luxor-claude-marketplace --skill apache-spark-data-processing -a claude-codeWhat apache-spark-data-processing does
The skill walks through Spark layer by layer. It starts with RDDs as the base abstraction, where transformations stay lazy and actions fire the job, then moves to DataFrames and Datasets and the Catalyst optimizer that rewrites your queries. Spark SQL, broadcast variables and accumulators, streaming and MLlib each get their own section. Your agent leans on this when you ask it to build a pipeline or read someone else's Spark code.
Partitioning and caching are covered in detail, including storage levels from MEMORY_ONLY down to DISK_ONLY. The material also says when caching hurts: data read once, or a dataset too big for cluster memory, is a bad candidate.
The skill does not run Spark for you and does not stand in for a cluster. It supplies context to the agent, so it earns its keep only if you already have a working Spark setup and know where your jobs execute. For datasets under 100 GB, plain CRUD work and latency below 10 ms, the guide points elsewhere.
What it helps with
- Write a PySpark processing pipeline from scratch
- Decide between RDDs and DataFrames for a job
- Tune partitioning and caching for a workload
- Set up streaming over a live data feed
- Train a model on a large dataset with MLlib
Example prompts for the agent
- Build a PySpark pipeline that reads Parquet, cleans the rows and computes daily aggregates
- My join is slow — check the partitioning and tell me what to change
- Rewrite this RDD code as DataFrames and explain what Catalyst does with it
How to install apache-spark-data-processing
1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill apache-spark-data-processing -a claude-code2Manually: put the files in place
~/.claude/skills/apache-spark-data-processing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/apache-spark-data-processing/
1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill apache-spark-data-processing -a codex2Manually: put the files in place
.agents/skills/apache-spark-data-processing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill apache-spark-data-processing -a cursor2Manually: put the files in place
.cursor/skills/apache-spark-data-processing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install manutej/luxor-claude-marketplace apache-spark-data-processing2Manually: put the files in place
.github/skills/apache-spark-data-processing/SKILL.md1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill apache-spark-data-processing -a gemini-cli2Platform CLI
gemini skills install https://github.com/manutej/luxor-claude-marketplace --path plugins/luxor-data-engineering/skills/apache-spark-data-processingManually: put the files in place
.devin/skills/apache-spark-data-processing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill apache-spark-data-processing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about apache-spark-data-processing
How do I install apache-spark-data-processing in Claude Code?
Run npx skills add manutej/luxor-claude-marketplace --skill apache-spark-data-processing -a claude-code. The skill file then sits at ~/.claude/skills/apache-spark-data-processing/SKILL.md.
What does apache-spark-data-processing do?
It gives the agent a reference on Apache Spark: RDDs, DataFrames, Spark SQL, streaming, MLlib and deployment. The agent pulls from it while you write or review data processing code.
When should you avoid Spark?
For datasets under 100 GB, simple CRUD operations and workloads needing latency below 10 ms. The guide recommends other tools in those cases.