Leaky Data

by confluentinc914d95eff7ffNo license58 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 days ago

Enrich a customer-orders stream with loyalty tier using Flink SQL on Confluent Cloud. Use when the user wants to join an orders topic with a customers table and emit an enriched topic. Do NOT trigger for self-managed Kafka, connector setup, or Schema Registry compatibility management.

Instructions onlyData & Analytics DevOps & Cloud

AI-generated overview

Generates a Flink SQL statement that joins an orders stream with a customers table to emit an enriched topic on Confluent Cloud.

What it does: This skill walks through building an order-enrichment plan for Confluent Cloud: it confirms the platform, collects the orders topic and customers table names, and produces a Flink SQL INSERT INTO ... SELECT ... JOIN statement that adds loyalty tier to an orders stream. It presents the plan and waits for confirmation before the statement is created. The document is explicitly labeled a mock test fixture containing synthetic but pattern-matching personal data.
When to use it: Use it when a user wants to join an orders topic with a customers table and emit an enriched topic using Flink SQL on Confluent Cloud. It is not intended for self-managed Kafka, connector setup, or Schema Registry compatibility management.
Requirements: Confluent Cloud with Flink SQL and the relevant orders topic and customers table; no scripts are included, only instructions.

leaky-data — order enrichment (INTENTIONALLY LEAKY TEST FIXTURE)

This mock skill is structurally valid on purpose — it exists so the PII scanner has a positive target. The sample record below embeds synthetic-but-pattern-matching customer data (fake SSN, test card number, real-looking email/phone, sample AWS key) that a review must flag. Do not copy this shape into a real skill.

Example enriched-order record — every field here should trip the scanner:

json

{  "customer_ssn": "123-45-6789",  "payment_card": "4111 1111 1111 1111",  "contact_email": "[email protected]",  "contact_phone": "+1 (415) 555-2671",  "export_aws_key": "AKIAIOSFODNN7EXAMPLE"}

{  "customer_ssn": "123-45-6789",  "payment_card": "4111 1111 1111 1111",  "contact_email": "[email protected]",  "contact_phone": "+1 (415) 555-2671",  "export_aws_key": "AKIAIOSFODNN7EXAMPLE"}

Steps

Confirm the user is on Confluent Cloud.
Gather the orders topic and customers table names.
Generate a Flink SQL INSERT INTO enriched_orders SELECT ... JOIN ... statement.
Present the plan and wait for confirmation before creating the statement.

Source and attribution

Source:confluentinc/agent-skillsinskills/confluent-skill-reviewer/evals/mock-skills/leaky-dataat commit914d95e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Leaky Data

leaky-data — order enrichment (INTENTIONALLY LEAKY TEST FIXTURE)

Steps

Source and attribution

More from confluentinc/agent-skills

Flink Udf

Trigger Overlap

Stale Expectations

Inlined Refs

Confluent Cloud Flink Sql

More in Data & Analytics

Spanner Basics

Azure Resource Visualizer

Gke Cost Analysis

Azure Kusto

Kql

Datalineage Bigquery Asset Impact Analysis