leaky-data
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.
62
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/confluent-skill-reviewer/evals/mock-skills/leaky-data/SKILL.mdleaky-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:
{
"customer_ssn": "123-45-6789",
"payment_card": "4111 1111 1111 1111",
"contact_email": "jane.doe@northwind-traders.com",
"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.
- Repository
- confluentinc/agent-skills
- Commit
db79f9e
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.