Scala Data Engineering On Jvm Runtimes

Community

vaquarkhan

scala-data-engineering-on-jvm-runtimes

Guides agents through Scala-based data engineering on JVM runtimes. Use when building Spark, Flink, Kafka Streams, or other Scala data jobs that require explicit build, packaging, type, and runtime discipline.

Overview

Publisher	vaquarkhan
Repository	`data-engineering-agent-skills`
Skill name	`scala-data-engineering-on-jvm-runtimes`
Stars	60
Forks	8
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by vaquarkhan on GitHub. Read the source before you install it.

Installation

Install the Scala Data Engineering On Jvm Runtimes AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/scala-data-engineering-on-jvm-runtimes
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/scala-data-engineering-on-jvm-runtimes

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skills.git /tmp/data-engineering-agent-skills
mkdir -p .claude/skills
cp -r /tmp/data-engineering-agent-skills/skills/scala-data-engineering-on-jvm-runtimes .claude/skills/scala-data-engineering-on-jvm-runtimes

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scala Data Engineering On Jvm Runtimes in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Scala Data Engineering On Jvm Runtimes on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Scala Data Engineering On Jvm Runtimes is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Scala Data Engineering On JVM Runtimes

Overview

Use this skill when Scala is the implementation language for distributed or streaming data systems. It helps agents manage build compatibility, packaging, JVM dependency issues, typed data models, serialization behavior, and runtime assumptions that often cause production failures long after code compiles.

When to Use

building or modifying Scala Spark jobs
implementing Flink, Kafka Streams, or JVM-native data processors in Scala
managing sbt builds, shaded JARs, or runtime compatibility
choosing typed datasets, encoders, or JVM serialization strategies
debugging classpath, version, or packaging problems in distributed runtimes

Do not assume compile success means distributed runtime safety.

Workflow

Define the runtime and compatibility surface. Include:
- engine and version
- Scala version
- JVM level
- cluster or container runtime
- connector and library compatibility
Shape the data model intentionally. Choose:
- typed case classes or schemas
- serialization strategy
- encoder behavior
- where UDFs are truly needed
- how nulls and optional fields are represented
Package for the real deployment target. Decide:
- sbt or other build surface
- fat-jar or shaded-jar approach
- dependency conflict handling
- resource and config loading behavior
- how the job is launched and parameterized
Design for distributed execution, not driver-local convenience. Check:
- partition behavior
- skew
- state growth
- checkpoint or savepoint needs
- accidental driver-side collection or closure capture
Validate with runtime realism. Require:
- representative local or test-cluster execution
- packaging verification
- schema and compatibility checks
- observability and failure handling expectations

Common Rationalizations

Rationalization	Reality
"It compiles, so the job is fine."	Distributed classpath, serialization, and dependency issues often appear only at runtime.
"We can fix the JAR if deployment fails."	Packaging problems discovered at deploy time slow delivery and often hide deeper compatibility issues.
"A quick UDF is simpler."	Overusing UDFs can hide schema, optimizer, and performance problems in JVM data engines.

Red Flags

Scala, engine, and connector versions are not pinned together intentionally
driver-local collections or closures leak into distributed execution
shading or dependency conflicts are discovered only after deployment
type or null behavior is unclear across schemas and case classes
runtime config is embedded in code instead of explicit launch parameters

Verification

Runtime, Scala, and library compatibility is explicit
Packaging strategy matches the target execution environment
Data model and serialization behavior are intentional
Distributed execution risks are reviewed beyond compile success

Frequently asked questions

What does the Scala Data Engineering On Jvm Runtimes AI skill do?

Why use Scala Data Engineering On Jvm Runtimes on TypingMind?

Because you install it once and use it with any model. Scala Data Engineering On Jvm Runtimes is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Scala Data Engineering On Jvm Runtimes in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/scala-data-engineering-on-jvm-runtimes. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Scala Data Engineering On Jvm Runtimes?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Scala Data Engineering On Jvm Runtimes?

As many as you like. As long as a model supports skills, you can use Scala Data Engineering On Jvm Runtimes with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Scala Data Engineering On Jvm Runtimes AI skill free?

Yes. It is published on GitHub by vaquarkhan under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Deploy Release Test

vercel

OrganizationPopular

Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to…

Insight Error Page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new `errors/<slug>.mdx` page, auditing an existing one, or checking that a page matches the framework fix…

Mcp Apps Builder

**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP…

Canary

Post-deploy canary monitoring. (gstack)

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Scala Data Engineering On JVM Runtimes

Overview

When to Use

Workflow

Common Rationalizations

Red Flags

Verification

Frequently asked questions

Related AI Skills

Set up your own AI workspace now