TypingMindTypingMindThe best frontend for AI
Streaming And Messaging Systems logo

Streaming And Messaging Systems

Community
vaquarkhan
streaming-and-messaging-systems

Guides agents through event streaming and real-time data pipeline design. Use when working with Kafka, Kinesis, Flink, stream processing, windowing, stateful consumers, or near-real-time publish flows.

Overview

Publishervaquarkhan
Repositorydata-engineering-agent-skills
Skill namestreaming-and-messaging-systems
Stars
60
Forks
8
Bundled files
3
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • 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.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by vaquarkhan on GitHub. Read the source before you install it.

Installation

Install the Streaming And Messaging Systems AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/streaming-and-messaging-systems
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/streaming-and-messaging-systems .claude/skills/streaming-and-messaging-systems
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Streaming And Messaging Systems 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 Streaming And Messaging Systems 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 Streaming And Messaging Systems 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.

Streaming And Messaging Systems

Overview

Use this skill for continuous data movement and real-time processing. It helps agents design safe event pipelines around brokers and stream processors such as Kafka, Kinesis, and Flink, with attention to ordering, state, replay, schema evolution, and delivery guarantees.

When to Use

  • designing or modifying Kafka topics, consumers, or stream processors
  • using Kinesis for event ingestion or streaming delivery
  • implementing Flink jobs or stateful stream transformations
  • defining near-real-time pipelines, windows, watermarks, and replay behavior
  • handling schemas and contracts for event-driven systems

Do not use this when the workload is purely batch and does not require streaming semantics.

Workflow

  1. Define the event contract. Include:

    • event key
    • schema and versioning
    • ordering expectations
    • delivery guarantees
    • retention and replay policy

  2. Choose the right platform role.

    • Kafka: durable event backbone and broad ecosystem
    • Kinesis: AWS-native streaming ingestion and transport
    • Flink: stateful stream processing and event-time logic

  3. Design for state and late data. Account for:

    • watermarks
    • windows
    • deduplication
    • exactly-once or at-least-once semantics
    • checkpointing and recovery

  4. Make consumer behavior observable. Lag, failed checkpoints, poison messages, schema drift, and dead-letter handling should be planned, not discovered in production. For production Kafka hardening, load kafka-resilience-and-schema-evolution. For live lag or broker metadata before changes, load mcp-data-observability-integration.

  5. Treat replay as a first-class operation. Reprocessing events should not depend on manual guesswork.

Common Rationalizations

RationalizationReality
"Streaming just means faster batch."Streaming introduces ordering, state, replay, and time semantics that batch systems do not have.
"We can ignore schema evolution because events are small."Event size does not reduce contract risk; schema drift can break many downstream consumers.
"Exactly-once is automatic."Delivery semantics depend on end-to-end design, state handling, sinks, and replay behavior.

Red Flags

  • no explicit event contract or key strategy
  • replay and retention are undefined
  • time semantics are assumed instead of specified
  • consumer lag and dead-letter strategy are missing
  • stateful processing has no checkpoint or recovery plan

Verification

  • Event schema, keys, retention, and replay rules are defined
  • Platform responsibilities are clear across broker and processor layers
  • Time semantics, state, and recovery design are explicit
  • Operational visibility exists for lag, failures, and bad records

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Streaming And Messaging Systems AI skill do?

Guides agents through event streaming and real-time data pipeline design. Use when working with Kafka, Kinesis, Flink, stream processing, windowing, stateful consumers, or near-real-time publish flows.

Why use Streaming And Messaging Systems on TypingMind?

Because you install it once and use it with any model. Streaming And Messaging Systems 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 Streaming And Messaging Systems in TypingMind?

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

Which AI models can use Streaming And Messaging Systems?

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 Streaming And Messaging Systems?

As many as you like. As long as a model supports skills, you can use Streaming And Messaging Systems with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Streaming And Messaging Systems 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.

Related AI Skills

View all
affaan-m logo

Architecture Decision Records

affaan-m
CommunityPopular

コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。

39.1K
261.1K
Instructions
View
affaan-m logo

Automation Audit Ops

affaan-m
CommunityPopular

ECC用の証拠ベースの自動化インベントリとオーバーラップ監査ワークフロー。ユーザーがどのジョブ、フック、コネクタ、MCPサーバー、またはラッパーがライブか、壊れているか、冗長であるか、修正前に不足しているかを知りたい場合に使用します。

39.1K
261.1K
Instructions
View
NousResearch logo

Grok

NousResearch
OrganizationPopular

Delegate coding to xAI Grok Build CLI (features, PRs).

53.5K
250.4K
Instructions
View
NousResearch logo

Setup Wizard Generator

NousResearch
OrganizationPopular

Generate a bash wizard guiding a human through manual setup.

53.5K
250.4K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇