How do I install the Flink Principal Engineer skill?

Run npx skillmds@latest add modra40/flink-principal-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flink Principal Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flink Principal Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flink Principal Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flink Principal Engineer?

modra40 (@modra40) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flink Principal Engineer by modra40

Name: Flink Principal Engineer
Author: modra40

Flink Principal Engineer

Principal/Senior-level Flink playbook for stream processing architecture, stateful pipelines, event-time correctness, checkpointing, scaling, and operating low-latency data platforms. Use when: designing streaming systems, reviewing stateful Flink jobs, tuning event-time pipelines, or operating Flink in production.

modra40 3a7343b 9 files · 9.4 KB Updated Sep 17, 2026

File contents

Flink Mastery (Senior → Principal)

Operate

Start from correctness model: event time, ordering, lateness, replay, and side-effect semantics.
Treat Flink as a stateful distributed system, not just a transformation engine.
Prefer explicit state, windowing, and failure behavior over vague stream magic.
Optimize for correctness first, then latency, then cost.

Default Standards

State and checkpoint strategy must be explicit.
Event-time assumptions should be validated with real lateness patterns.
Backpressure and operator chaining require observability.
External side effects must be designed for retries and replay.
Multi-tenant stream platforms need strong workload isolation thinking.

References

Stream architecture and operator design: references/stream-architecture-and-operator-design.md
State, checkpoints, and savepoint safety: references/state-checkpoints-and-savepoint-safety.md
Event time, watermarks, and lateness correctness: references/event-time-watermarks-and-lateness-correctness.md
Backpressure, scaling, and performance tuning: references/backpressure-scaling-and-performance-tuning.md
Delivery semantics and external side effects: references/delivery-semantics-and-external-side-effects.md
Multi-tenant governance and stream platform safety: references/multi-tenant-governance-and-stream-platform-safety.md
Reliability and operations: references/reliability-and-operations.md
Incident runbooks: references/incident-runbooks.md

---name: flink-principal-engineerdescription: Principal/Senior-level Flink playbook for stream processing architecture, stateful pipelines, event-time correctness, checkpointing, scaling, and operating low-latency data platforms. Use when: designing streaming systems, reviewing stateful Flink jobs, tuning event-time pipelines, or operating Flink in production.---# Flink Mastery (Senior → Principal)## Operate- Start from correctness model: event time, ordering, lateness, replay, and side-effect semantics.- Treat Flink as a stateful distributed system, not just a transformation engine.- Prefer explicit state, windowing, and failure behavior over vague stream magic.- Optimize for correctness first, then latency, then cost.## Default Standards- State and checkpoint strategy must be explicit.- Event-time assumptions should be validated with real lateness patterns.- Backpressure and operator chaining require observability.- External side effects must be designed for retries and replay.- Multi-tenant stream platforms need strong workload isolation thinking.## References- Stream architecture and operator design: [references/stream-architecture-and-operator-design.md](references/stream-architecture-and-operator-design.md)- State, checkpoints, and savepoint safety: [references/state-checkpoints-and-savepoint-safety.md](references/state-checkpoints-and-savepoint-safety.md)- Event time, watermarks, and lateness correctness: [references/event-time-watermarks-and-lateness-correctness.md](references/event-time-watermarks-and-lateness-correctness.md)- Backpressure, scaling, and performance tuning: [references/backpressure-scaling-and-performance-tuning.md](references/backpressure-scaling-and-performance-tuning.md)- Delivery semantics and external side effects: [references/delivery-semantics-and-external-side-effects.md](references/delivery-semantics-and-external-side-effects.md)- Multi-tenant governance and stream platform safety: [references/multi-tenant-governance-and-stream-platform-safety.md](references/multi-tenant-governance-and-stream-platform-safety.md)- Reliability and operations: [references/reliability-and-operations.md](references/reliability-and-operations.md)- Incident runbooks: [references/incident-runbooks.md](references/incident-runbooks.md)

Frequently asked questions