Receber por email
← Voltar para o catálogo

Great Expectations Generator

Gera suites do Great Expectations a partir de perfis de dados e regras de negócio.

1.4kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add a5c-ai/babysitter

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/great-expectations-generator/svg)](https://www.skillteca.com.br/skills/great-expectations-generator)

Skills relacionadas

Ver todas de Automação →

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Great Expectations Generator

Overview

Generates Great Expectations suites from data profiles and business rules. This skill automates the creation of comprehensive expectation suites that enforce data quality constraints.

Capabilities

  • Expectation suite generation from profiling
  • Custom expectation creation
  • Checkpoint configuration
  • Data docs generation
  • Validation result analysis
  • Expectation parameterization
  • Suite versioning recommendations
  • Integration with dbt and Airflow

Input Schema

{
  "dataProfile": "object",
  "businessRules": ["object"],
  "existingSuite": "object",
  "strictness": "strict|moderate|lenient"
}

Output Schema

{
  "expectationSuite": "object",
  "checkpointConfig": "object",
  "documentation": "string",
  "coverageReport": {
    "columnsWithExpectations": "number",
    "totalExpectations": "number"
  }
}

Target Processes

  • Data Quality Framework
  • ETL/ELT Pipeline
  • dbt Project Setup

Usage Guidelines

  1. Provide data profile results from profiling analysis
  2. Define business rules that should be enforced
  3. Specify strictness level based on use case requirements
  4. Include existing suite if extending an existing configuration

Best Practices

  • Start with moderate strictness and adjust based on validation results
  • Include both column-level and table-level expectations
  • Document business rationale for each custom expectation
  • Version expectation suites alongside data transformations
  • Configure appropriate data docs for stakeholder visibility
Compartilhar X LinkedIn