How does it handle integration sync issues?

It compares record counts across platforms and flags variances higher than 1%, triggering an investigation workflow to identify mapping or sync failures.

What is the primary use of the Data Quality Operations Framework?

It is used for ongoing, recurring data-quality management in Salesforce, including monitoring field population, integration health, and responding to data anomalies.

How does this differ from the Operations Readiness Framework?

This skill is designed for continuous, daily operations, whereas the Operations Readiness Framework is intended for one-time preflight environment audits.

Can this skill help with Salesforce deduplication?

While it monitors duplicate rates, it is not an execution tool for deduplication. You should use the /dedup command for actual merging operations.

What metrics does this skill track?

It tracks field population rates, duplicate rates, orphan records (e.g., Contacts without Accounts), stale records, and integration sync variance.

Salesforce Data Quality Operations

Name: Salesforce Data Quality Operations
Author: RevPalSFDC

byRevPalSFDC

•

Gestión de Bases de Datos

Manages recurring Salesforce data-quality monitoring, field population health, and integration sync integrity.

The Data Quality Operations Framework is a specialized Claude Code skill designed for continuous Salesforce maintenance and RevOps oversight. Unlike one-time audit tools, it focuses on the long-term health of your CRM by automating the monitoring of critical field population rates, identifying data anomalies like sudden null spikes, and maintaining integration health between Salesforce and external platforms. By implementing standardized null-handling governance and anomaly response loops, this skill ensures that commercial data remains reliable, consistent, and ready for high-level business intelligence.

Características Principales

01Standardized null-handling governance for required and optional fields

021 GitHub stars

03Continuous monitoring of field population rates across critical Salesforce objects

04Proactive anomaly response workflows for sudden data quality deviations

05Integration health tracking to detect sync drift and record count variances

06Automated reporting for orphan records, stale leads, and duplicate surges

Casos de Uso

01Setting up recurring health checks to ensure Sales teams are populating critical Account fields

02Investigating sudden data drift between Salesforce and integrated platforms like HubSpot or Marketo

03Managing enterprise-wide data governance policies to prevent record orphaned and stale data

Características Principales

01Standardized null-handling governance for required and optional fields

021 GitHub stars

03Continuous monitoring of field population rates across critical Salesforce objects

04Proactive anomaly response workflows for sudden data quality deviations

05Integration health tracking to detect sync drift and record count variances

06Automated reporting for orphan records, stale leads, and duplicate surges

Casos de Uso

01Setting up recurring health checks to ensure Sales teams are populating critical Account fields

02Investigating sudden data drift between Salesforce and integrated platforms like HubSpot or Marketo

03Managing enterprise-wide data governance policies to prevent record orphaned and stale data