streaming-and-messaging-systems — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited streaming-and-messaging-systems (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
Kafka topics, consumers, or stream processorsKinesis for event ingestion or streaming deliveryFlink jobs or stateful stream transformationsDo not use this when the workload is purely batch and does not require streaming semantics.
Include:
Kafka: durable event backbone and broad ecosystemKinesis: AWS-native streaming ingestion and transportFlink: stateful stream processing and event-time logicAccount for:
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.
Reprocessing events should not depend on manual guesswork.
| Rationalization | Reality |
|---|---|
| "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. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.