crm-hygiene-report

$npx mdskill add Significant-Gravitas/skills-catalog/crm-hygiene-report

Use this weekly or monthly, from dated exports compared with the last report.

SKILL.md

.github/skills/crm-hygiene-reportView on GitHub ↗
---
name: "crm-hygiene-report"
description: "Report CRM health for a period with counts, trends, owners, and the next fixes."
triggers: ["CRM hygiene", "data health report", "CRM report", "pipeline hygiene", "stale deals"]
version: "1"
---

# CRM hygiene report

Use this weekly or monthly, from dated exports compared with the last report.

## Headline counts

Open with the export dates and row counts, then give each count against the
last period:

- records with no owner;
- key fields below the agreed fill rate;
- likely duplicate pairs open;
- deals past close date or stale in stage;
- leads with no owner after a day.

Say which change matters most and which report it affects.

## By owner and object

Break the counts down by object and by owner. Show where problems cluster and
whether they are new or old. Keep the tone neutral; the aim is to fix the
data, not to rank people.

## Next fixes

List three to five fixes in order, each with the count it would clear, the
report it helps, the owner who must approve it, and a suggested date. Note
fixes from the last report that are still open.

Never guess a missing value to improve a count, and do not hide records to
make a trend look better. Do not merge, delete, reassign, or edit CRM records
yourself; the owners make each change.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.