leaky-data

Generates Flink SQL statements joining orders topics with customers tables on Confluent Cloud.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill leaky-data-ricardolui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: leaky-data
Source: https://github.com/ricardolui/gcp-custom-agent-skills/tree/main/confluent-skill-reviewer/evals/mock-skills/leaky-data
Command: npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill leaky-data-ricardolui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a stream enrichment join between a Kafka orders topic and a customers table requires correct Flink SQL syntax and Confluent Cloud context, which this Skill guides step by step. ## Core Features & Use Cases - Stream Enrichment Planning: Confirms the user is on Confluent Cloud and gathers the orders topic and customers table names before generating SQL. - Flink SQL Generation: Produces an INSERT INTO enriched_orders SELECT ... JOIN ... statement for the enrichment pipeline. - Confirmation Gate: Presents the plan and waits for user confirmation before creating the statement. - Use Case: A data engineer wants to emit an enriched orders topic that includes each customer's loyalty tier by joining an orders topic with a customers table. ## Quick Start Ask the assistant to enrich your orders topic with loyalty tier data from your customers table using Flink SQL on Confluent Cloud.

Frequently Asked Questions about leaky-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I join a Kafka orders topic with a customers table using Flink SQL?

Use a Flink SQL INSERT INTO enriched_orders SELECT ... JOIN ... statement that joins the orders topic with the customers table. Confirm the topic and table names first, then review the generated statement before creating it.

How to enrich a Kafka stream with customer loyalty tier data?

Stream enrichment joins each order event with the corresponding customer record to append fields like loyalty tier. On Confluent Cloud, this is done with a Flink SQL join statement writing results to an enriched orders topic.

Does this Flink SQL enrichment work with self-managed Kafka?

No, this Skill explicitly targets Confluent Cloud and does not trigger for self-managed Kafka deployments. It also excludes connector setup and Schema Registry compatibility management.

When should I not use Flink SQL stream enrichment?

Avoid it when you are on self-managed Kafka, need connector configuration, or need Schema Registry compatibility management, since those scenarios are outside its scope. It is designed only for order-to-customer join enrichment on Confluent Cloud.