Event Streaming Platform Design
Designs shared streaming platforms, topics, partitions, tenancy, retention and replay. Use when selecting or designing Kafka, Pulsar, or Event Hubs-style platforms.
Install
$ agentstack add skill-mmccalla-coding-agent-skill-library-event-streaming-platform-design ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mmccalla-coding-agent-skill-library-event-streaming-platform-design) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Event Streaming Platform Design
When to use
Use for Kafka, Pulsar, Event Hubs or similar streaming platform foundations.
Objective
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Procedure
- Define workloads and tenants.
- Define naming and environments.
- Define topic/stream lifecycle.
- Define partitioning and retention.
- Define schema registry policy.
- Define access controls and quotas.
- Define observability and support model.
- Define deprecation process.
Required outputs
- Platform model
- Topic strategy
- Partition/retention policy
- Schema/access policy
- Quotas
- Support model
Best-practice alignment
Apply event-driven best practice: business event semantics, producer/consumer ownership, schema contracts, compatibility, ordering, partitioning, idempotency, replay, retention, lineage, observability and operational SLOs. Prefer CloudEvents for interoperable envelopes and AsyncAPI (or registry-backed schemas) for channel and message contracts on the platform.
Quality checks
- Topics have owners.
- Partition strategy is explicit.
- Retention supports replay/compliance.
- Access is least privilege.
Avoid
Do not allow unowned shared topics.
Decision template
For each topic family, define naming convention, environment strategy, tenant, owner, partition key, retention, replay expectation, schema subject, access policy, quota, support tier and deprecation route. Reject unowned shared topics because they become hidden integration contracts with unclear cost, lineage and incident accountability.
References
Verification
- [ ] Required artefacts produced and linked to scope.
- [ ] Decisions, assumptions and risks stated explicitly.
- [ ] Quality checks or validation performed.
- [ ] Files changed reported with traceability preserved.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mmccalla
- Source: mmccalla/coding-agent-skill-library
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.