data-quality-check

Audit CRM and CS platform data for completeness, staleness, and consistency.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill data-quality-check-t0ddc3by
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-quality-check
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/cs-ops/skills/data-quality-check
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill data-quality-check-t0ddc3by

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies missing, stale, and inconsistent data in your CRM and CS Platform so your reports and plans reflect reality—not silent coverage gaps.

Core Features & Use Cases

  • Completeness audit: Finds required-field gaps and quantifies how much ARR is affected.
  • Staleness audit: Flags fields (notably health scores and related signals) that haven’t updated within the configured threshold.
  • Consistency + orphan detection: Detects cross-field logic violations and identifies accounts that are effectively invisible to CS workflows (no CSM owner and no segment).

Quick Start

Run cs-ops data-quality-check in full mode by saying: /cs-ops:data-quality-check.

Frequently Asked Questions about data-quality-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit CRM data quality and quantify the ARR impact of missing fields?

To audit CRM data quality, run a completeness audit that identifies required-field gaps and quantifies how much ARR is affected. This ensures your reports reflect reality by surfacing missing data coverage gaps.

How do I check for stale health scores in my CS platform data?

Checking for stale health scores requires a staleness audit that flags fields not updated within configured thresholds. This detects outdated signals that can break CS workflows and analytics outputs.

What causes orphan accounts in CS workflows and how do I detect them?

Orphan accounts occur when accounts lack a CSM owner and segment, making them invisible to CS workflows. Consistency and orphan detection identifies these cross-field logic violations to prevent reporting gaps.

How do I validate CRM data readiness before a QBR or reporting cycle?

Validating CRM data readiness before a QBR involves running pre-reporting checks across completeness, staleness, and cross-field consistency. This surfaces report-breaking coverage gaps with ARR-weighted impact.

Does the data quality audit require write access to my CRM or CS platform?

No, the data quality audit operates strictly read-only. It computes findings with ARR-weighted impact using configured staleness thresholds and required-field definitions without modifying your CRM or CS platform data.