Tools and patterns for building and debugging Kafka-based event-driven systems on Nais.
Install
mkdir -p .claude/skills/kafka && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18974" && unzip -o skill.zip -d .claude/skills/kafka && rm skill.zipInstalls to .claude/skills/kafka
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Rapids & Rivers, eventdrevet arkitektur, Kafka-mønstre og schema-design for Nav-applikasjonerKey capabilities
- →Set up Kafka in a Nais application
- →Implement a Rapids & Rivers consumer
- →Design event schemas
- →Test event-driven code with TestRapid
- →Troubleshoot Kafka connectivity
- →Troubleshoot consumer lag
How it works
The skill provides patterns, templates, and procedures for building event-driven systems using Kafka on Nais, focusing on the Rapids & Rivers framework and event schema design. It guides setting up Nais manifests and Kotlin application code.
Inputs & outputs
When to use kafka
- →Setting up Kafka in Nais
- →Implementing event consumers
- →Designing event schemas
- →Troubleshooting Kafka connectivity
About kafka
Assists with setting up Kafka manifests, implementing Rapids & Rivers consumers, designing event schemas, and troubleshooting connectivity or consumer lag.
Rapids & Rivers, eventdrevet arkitektur, Kafka-mønstre og schema-design for Nav-applikasjoner
When not to use it
- →Creating new Kafka topics without asking first
- →Changing consumer group IDs without a migration plan
- →Publishing PII in event payloads without encryption
Limitations
- →Requires a Kotlin/JVM application with Kafka on Nais
- →Does not support imperative event names
- →Does not allow skipping the `@id` field for events
How it compares
This skill offers specific guidance and code examples for implementing event-driven systems with Kafka within the Nais platform, unlike general Kafka documentation.
Compared to similar skills
kafka side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| kafka (this skill) | 0 | 2mo | Review | Intermediate |
| android-kotlin-development | 268 | 6mo | Review | Advanced |
| nostr-expert | 3 | 3mo | Review | Advanced |
| mqtt-kmp | 0 | 4mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by navikt
View all by navikt →You might also like
android-kotlin-development
aj-geddes
Develop native Android apps with Kotlin. Covers MVVM with Jetpack, Compose for modern UI, Retrofit for API calls, Room for local storage, and navigation architecture.
nostr-expert
vitorpamplona
Nostr protocol implementation patterns in Quartz (AmethystMultiplatform's KMP Nostr library). Use when working with: (1) Nostr events (creating, parsing, signing), (2) Event kinds and tags, (3) NIP implementations (57 NIPs in quartz/), (4) Event builders and TagArrayBuilder DSL, (5) Nostr cryptography (secp256k1, NIP-44 encryption), (6) Relay communication patterns, (7) Bech32 encoding (npub, nsec, note, nevent). Complements nostr-protocol agent (NIP specs) - this skill provides Quartz codebase patterns and implementation details.
mqtt-kmp
meshtastic
MQTTastic Client KMP — Kotlin Multiplatform MQTT 5.0 client library project knowledge
kotlin-ktor
navikt
Ktor-applikasjoner i Kotlin — routes, plugins, Koin DI, JWT-claims som NAVident, CallLogging/MDC, StatusPages/ApiError, paginering og input-validering. Brukes via /kotlin-ktor ved Ktor-arbeid.
vertigram-telegram-api-bump
gagarski
Update Vertigram's vertigram-telegram-client module for a requested Telegram Bot API version. Use when the user asks to bump supported Telegram Bot API versions, apply Telegram Bot API changelog entries, add Telegram API types/methods/json body definitions, update Telegram markup builders, or add se
kotlin-multiplatform
vitorpamplona
Platform abstraction decision-making for Amethyst KMP project. Guides when to abstract vs keep platform-specific, source set placement (commonMain, jvmAndroid, platform-specific), expect/actual patterns. Covers primary targets (Android, JVM/Desktop, iOS) with web/wasm future considerations. Integrates with gradle-expert for dependency issues. Triggers on: abstraction decisions ("should I share this?"), source set placement questions, expect/actual creation, build.gradle.kts work, incorrect placement detection, KMP dependency suggestions.