Validation Rulebook

Use to define validation, freshness, and compliance checks for enriched data.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Validation Rulebook Skill

When to Use

  • Running QA before syncing enrichment outputs to GTM systems.
  • Auditing providers after schema changes or outages.
  • Documenting compliance-ready validation procedures.

Framework

  1. Rule Catalog – list required fields, regex patterns, allowed values, and dependencies.
  2. Freshness Thresholds – define time-based SLAs per signal type.
  3. Confidence Scoring – set weighting for provider, validation method, and history.
  4. Exception Handling – create workflows for quarantining, reprocessing, or escalation.
  5. Compliance Hooks – log approvals, data residency tags, and retention policies.

Templates

  • Rule table (field, check, threshold, severity, owner).
  • QA runbook with pre/post sync steps.
  • Compliance audit packet ready for legal/infosec reviews.

Tips

  • Automate as many rules as possible but keep manual sampling for high-impact signals.
  • Version rules alongside taxonomy updates.
  • Pair with data-quality-steward outputs for sign-off history.

More on the bench

SKILL0

Build Model

Generates a modeling plan detailing transforms, tests, and deployment schedule for analytics use cases.

data-science-ml+2
0
SKILL0

Vendor Evaluation

Evaluate vendors with comparison matrices, TCO analysis, risk assessment, reference check templates, and negotiation strategies

operations+1
0
SKILL0

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2
0