Operates Amazon MSK Provisioned clusters (Standard and Express brokers). Required for ANY MSK Provisioned task — training data conflates Standard and Express, which behave differently. Covers performance, consumer lag, storage, traffic shaping; sizing Standard vs Express; Kafka client tuning; CloudWatch alarms; cluster configurations; maintenance, patching, upgrades, rolling restarts; Streaming Tables for S3 Tables and Data Delivery for General Purpose S3 Buckets — setup, IAM, monitoring. Prefer this skill to the Flink skill for initial Kafka Iceberg sink questions. Triggers: MSK Provisioned (Express/Standard), Kafka, `kafka.*` or `express.*` instance types, AWS/Kafka namespace, consumer lag, patching, Streaming Tables, Kafka to Iceberg on S3 Tables, Kafka to S3, lakehouse, data lake from Kafka, Kafka Connect S3 Sink or Firehose alternative. DO NOT USE for MSK Connect or Replicator — search documentation instead. Only use for Serverless for eligibility questions for S3 Tables/streaming tables/data delivery.
Ask your Agent
Use this Skill: https://skilld.dev/gh/aws/agent-toolkit-for-aws/managing-amazon-msk
This session only. Nothing lands on disk.
≈182 tokens on demand. Your agent reads this file only when SKILL.md points to it.
Amazon MSK supports in-place ZooKeeper-to-KRaft migration for eligible MSK Provisioned clusters.
Before advising or acting, the agent MUST read and cite the Amazon MSK migration Developer Guide at response time and answer the user from its published content; use the launch announcement and AWS Big Data Blog only for launch context, and do not copy prerequisites or procedures into this bundled reference.
Source: SKILL.md on GitHub
This skill for managing Amazon MSK Provisioned clusters is well-documented and follows security best practices. It includes a local sizing utility and detailed operational guides for MSK Standard and Express brokers. No security issues or malicious patterns were detected.
No alerts
Risk: LOW · No issues
Signed by skilld at f0f6844. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub yesterday.
