What problem does it solve? Migrating a self-managed Apache Kafka cluster to Amazon MSK Express requires inventorying brokers, topics, configs, and security settings, then checking them against Express's compatibility rules and sizing constraints — a manual, error-prone process. ## Core Features & Use Cases - Discovery: Builds a cluster-config.json inventory from IaC files (Terraform, CDK, Docker Compose, Kubernetes), Kafka CLI output, or manual input. - Compatibility Assessment: Runs a five-pillar check (topology, Kafka version, configs, auth, quotas) against MSK Express rules and emits INFO/ADVISORY/ACTION_REQUIRED verdicts. - Sizing & Costing: Fills the AWS-published MSK Sizing/Pricing workbook with workload inputs to produce broker count and monthly cost recommendations. - Simulation: Optionally deploys a temporary MSK Express cluster with load-testing infrastructure and a CloudWatch dashboard. - Use Case: A platform team with an on-premises Kafka 3.6 cluster points the skill at their Terraform directory, receives a compatibility report flagging an unsupported Kerberos auth mechanism, and gets a filled sizing workbook recommending an Express instance type. ## Quick Start Ask the assistant to migrate your Kafka cluster to MSK Express and point it at your infrastructure code directory to start discovery.