Menü
Place Assert and Schema Validation nodes as gates that halt a chain when data is wrong, so bad data never reaches the output. Use when the pipeline must guarantee correctness before exporting or loading downstream.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Sequence cleaning steps in a chain — trim/case/replace, null handling, deduplication, and type casting — in the right order. Use when raw ingested data needs cleaning before joins or aggregation.
Choose the right sink format, compression, and destination for a chain's output, and decide between exporting a file vs creating a table. Use at the end of a pipeline when deciding how to persist results.
Best practices for loading files into a chain — single file, folder globs, type detection, and union of many files. Use when the pipeline starts from CSV/Parquet/JSON/Excel files or a folder of files.
Decide between Merge (stack rows / UNION) and Join (match on a key) when a chain has multiple inputs, and set keys and join type correctly. Use when a pipeline combines two or more upstream tables.
Descompone un objetivo de procesamiento en un flujo de nodos Chains (source → transform → sink). Use when the user wants to build a data pipeline / chain, or describes an end-to-end "load X, clean it, summarize, export" goal.
Framework de razonamiento para convertir resultados de análisis en una narrativa visual clara y convincente
| name | Puertas de Calidad |
| description | Place Assert and Schema Validation nodes as gates that halt a chain when data is wrong, so bad data never reaches the output. Use when the pipeline must guarantee correctness before exporting or loading downstream. |
| keywords | assert, validación, validar, calidad, gate, puerta, schema, esquema, detener, halt, garantía, integridad, checks, contrato |
| next | export-strategy |
| scope | engineering |
Activa cuando el flujo debe garantizar que los datos son correctos antes de producir su salida. Una puerta detiene el chain si la condición falla — mejor fallar fuerte que exportar basura.
not_empty — la tabla tiene filas (detecta ingestas/joins vacíos).row_count_gt — al menos N filas (detecta cargas truncadas).no_nulls en una columna — clave/métrica sin nulos.unique en una columna — sin duplicados en la PK.custom_query — cualquier regla SQL (devuelve ≥1 fila = pasa).Con las puertas puestas, define la salida con [[export-strategy]].