Agent Plugins Marketplace
All plugins

data-streaming-engineering

v0.3.4

Data-streaming-engineering team — agents (streaming-architect, kafka-pipeline-engineer, stream-processing-engineer) for REAL-TIME data: streaming-vs-batch decision and topology, event streaming + CDC (Kafka/Pulsar/Kinesis, topics/partitioning, schema registry + evolution, the outbox/Debezium CDC pattern), delivery semantics (at-least-once vs exactly-once, idempotency, transactional outbox), and stream processing (Flink/Kafka-Streams: event-time vs processing-time, windowing, watermarks, state, joins, backpressure). skills, a decision-tree knowledge bank (streaming-vs-batch + delivery-semantics trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Distinct from data-platform (batch ELT) and microsoft-fabric (RTI/Eventstream). Seams: batch ELT -> data-platform, AsyncAPI contracts -> api-engineering, Fabric RTI -> microsoft-fabric, app-side messaging -> backend-engineering. Requires ravenclaude-core@>=0.7.0.

Claude Code7 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes
Claude Code
Parsed components
7 skill or MCP entries
Source updated
Sep 15, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology

Install data-streaming-engineering for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install data-streaming-engineering@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/data-streaming-engineering/.

Plugin files

plugins/data-streaming-engineering/
├── .claude-plugin/plugin.json
├── skills/cdc-pipeline-setup/SKILL.md
├── skills/consumer-lag-triage/SKILL.md
├── skills/kafka-platform/SKILL.md
├── skills/schema-evolution-playbook/SKILL.md
├── skills/schema-registry-evolution/SKILL.md
├── skills/stream-processing/SKILL.md
└── skills/streaming-vs-batch/SKILL.md

Included Skills7

cdc-pipeline-setupskills/cdc-pipeline-setup/SKILL.md

Step-by-step playbook for standing up a Change Data Capture pipeline with Debezium — source connector configuration, slot management, snapshot strategy, and handling common failure modes.

consumer-lag-triageskills/consumer-lag-triage/SKILL.md

Structured triage procedure for diagnosing and resolving Kafka consumer group lag — distinguishes slow consumer, under-partitioned topic, rebalance storm, and broker-side causes.

kafka-platformskills/kafka-platform/SKILL.md

Run the streaming platform reliably: partition for the ordering you need (order is per-partition; the key is the guarantee), govern schemas with a registry + compatibility rules, configure producer durability (acks/idempotence) and consumer offsets/idempotency, and ingest via CDC not dual-writes.

schema-evolution-playbookskills/schema-evolution-playbook/SKILL.md

Step-by-step playbook for evolving Avro/Protobuf/JSON Schema event schemas without breaking consumers, covering compatibility modes, migration patterns, and registry operations.

schema-registry-evolutionskills/schema-registry-evolution/SKILL.md

Playbook for managing Avro/Protobuf/JSON Schema schemas in a registry — choosing a compatibility mode, executing safe schema changes, and handling breaking changes without consumer downtime.

stream-processingskills/stream-processing/SKILL.md

Process streams correctly: aggregate on event-time with watermarks (not processing-time), window deliberately (tumbling/sliding/session), handle late data explicitly, checkpoint and TTL-bound state, join with aligned time, and design for backpressure.

streaming-vs-batchskills/streaming-vs-batch/SKILL.md

Decide streaming vs batch honestly by the real latency need (sub-minute reaction -> streaming; hourly/daily -> batch via data-platform), then design the topology, platform choice, and delivery semantics if streaming is justified.

Plugin manifests1

plugins/data-streaming-engineering/.claude-plugin/plugin.json
{
  "name": "data-streaming-engineering",
  "version": "0.3.4",
  "description": "Data-streaming-engineering team — agents (streaming-architect, kafka-pipeline-engineer, stream-processing-engineer) for REAL-TIME data: streaming-vs-batch decision and topology, event streaming + CDC (Kafka/Pulsar/Kinesis, topics/partitioning, schema registry + evolution, the outbox/Debezium CDC pattern), delivery semantics (at-least-once vs exactly-once, idempotency, transactional outbox), and stream processing (Flink/Kafka-Streams: event-time vs processing-time, windowing, watermarks, state, joins, backpressure). skills, a decision-tree knowledge bank (streaming-vs-batch + delivery-semantics trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Distinct from data-platform (batch ELT) and microsoft-fabric (RTI/Eventstream). Seams: batch ELT -> data-platform, AsyncAPI contracts -> api-engineering, Fabric RTI -> microsoft-fabric, app-side messaging -> backend-engineering. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "streaming",
    "kafka",
    "pulsar",
    "kinesis",
    "cdc",
    "debezium",
    "flink",
    "kafka-streams",
    "event-time",
    "windowing",
    "watermarks",
    "exactly-once",
    "schema-registry",
    "backpressure",
    "event-driven"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  },
  "lspServers": "./.lsp.json"
}

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[data-streaming-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/data-streaming-engineering)