Systems Lab

Agent skill

crm-hygiene

Audit and maintain CRM data quality — required-field gates, dedup, normalization, stale-record flagging, and orphan cleanup.

slowingNeeds a keyActs undeclared403 words

Filed under CRM and RevOps.

From devangk003/gtm-agent-skills · 32 skills · 0 · pushed 2026-06-18

What it does when it runs

Audit and maintain CRM data quality — required-field gates, dedup, normalization, stale-record flagging, and orphan cleanup. Use when the user says "run hygiene audit", "dedup CRM", "normalize industries", or "pipeline gate failed on missing fields.

Read from the skill and the 4 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
  • AGENTIC_APP_TOKEN
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It does act, so it runs under whatever permissions your session already grants.
Actions present in the files
shell

Ask about crm-hygiene

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/devangk003/gtm-agent-skills.git /tmp/gtm-agent-skills
git -C /tmp/gtm-agent-skills sparse-checkout set "crm-hygiene"
mkdir -p ~/.claude/skills/crm-hygiene
cp -R "/tmp/gtm-agent-skills/crm-hygiene/." ~/.claude/skills/crm-hygiene/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Before you install: this skill will not complete its job on a bare agent. It needs AGENTIC_APP_TOKEN, which you have to obtain separately.

The skill

Source on GitHub ↗

Reproduced in full from devangk003/gtm-agent-skills/blob/6b9a1b0094ffd83d6c02bc03b7ce1610661a1644/crm-hygiene/SKILL.md, which is licensed MIT (skill frontmatter). 403 words, 6 headings.

CRM Hygiene

Audit and maintain CRM data quality using Wang & Strong's four operationally critical dimensions: Accuracy, Completeness, Timeliness, Consistency. Surfaces required-field violations, dedup candidates, normalization fixes, stale records, and orphaned interactions. Hard rule: never auto-merge or auto-delete without user authorization.

When to Use

  • Weekly hygiene audit on the CRM
  • Pipeline stage advance failed on missing required fields
  • 3 records for the same person — dedup
  • Industry tagging inconsistent — normalize
  • Bulk import validation before scoring
  • User says "run hygiene audit" or "dedup CRM"

Quick Reference

ConceptValue
Quality dimensions (Wang & Strong, 1996)Accuracy / Completeness / Timeliness / Consistency
Dedup priority — personlinkedin_url > email > phone
Dedup priority — companycompany_domain (apex; strip www.)
Freshness windowsEmail 90d / Phone 12mo / Title 6mo
Severity tiersP0 (blocks scoring/forecasting) / P1 (degrades) / P2 (cosmetic)
Auto-fix scopeNormalization + orphan cleanup only. Dedup merges ALWAYS require user OK

Procedure

  1. Define audit scope. Full CRM or targeted record set. Pull entity counts. See ${HERMES_SKILL_DIR}/references/quality-dimensions.md.
  2. Completeness audit. Per entity, check required fields per stage. List violations with severity. P0 first.
  3. Dedup audit. Group by linkedin_url → email → phone (person); domain (company). Surface merge candidates with priority-based recommendation. See ${HERMES_SKILL_DIR}/references/dedup-rules.md.
  4. Consistency audit. Industry vs Apollo taxonomy; title normalization; domain cleanup. Propose fixes.
  5. Timeliness audit. Email >90d → flag for re-verification. Phone >12mo. Title >6mo. Signal half-life.
  6. Orphaned-interaction cleanup. Find interactions with missing parent person/company. Re-link or archive.
  7. Compile violation report. Group by severity P0/P1/P2. Each with fix + auto-fix-eligibility.
  8. Apply auto-fix + push. Normalization + orphans auto-apply. Dedup merges deferred for user authorization. See ${HERMES_SKILL_DIR}/scripts/push_to_crm.py.

Pitfalls

  • Auto-merging without user authorization — merges destroy data
  • Auto-deleting stale records — flag for re-verify, don't archive
  • Aggressive normalization losing information — preserve raw alongside normalized
  • Dedup priority ignored — use linkedin_url > email > phone per function-2 conventions
  • Treating freshness as binary — 95-day email isn't dead, it's likely-stale

Verification

  1. Every violation traces to a real record + field
  2. Dedup merge plans use documented priority
  3. Normalization preserves originals alongside normalized
  4. Auto-applied fixes have audit-log entries
  5. Deferred actions surfaced for explicit user authorization

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what crm-hygiene does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.