Cloudflare Basin R2 Data Catalog & Iceberg Streaming Skill

Stream high-volume event telemetry into Apache Iceberg tables on Cloudflare R2 using Basin Pipelines, Basin Catalog, and distributed SQL query engines.

---
name: basin
description: Stream high-volume event telemetry into Apache Iceberg tables on Cloudflare R2 using Basin Pipelines, Basin Catalog, and distributed SQL query engines. Use when working with Cloudflare R2, Apache Iceberg, Basin SQL, Data Pipelines.
triggers:
  - basin
  - cloudflare r2
  - apache iceberg
---

# Cloudflare Basin R2 Data Catalog & Iceberg Streaming Skill

## 1. When to Use This Skill
Load `skill-basin` whenever an engineering or operations task involves **Cloudflare R2, Apache Iceberg, Basin SQL, Data Pipelines**. Specifically:
- Stream high-volume event telemetry into Apache Iceberg tables on Cloudflare R2 using Basin Pipelines, Basin Catalog, and distributed SQL query engines.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Cloudflare R2, Apache Iceberg, Basin SQL, Data Pipelines
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://github.com/cloudflare/skills`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **Cloudflare R2**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
npx wrangler pipelines list
npx wrangler r2 bucket list
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide