hubspot-crm-data-hygiene
$
npx mdskill add openai/plugins/hubspot-crm-data-hygieneAudits HubSpot CRM data quality for cleanup and consistency
- Identifies missing fields, stale records, duplicates, and broken associations
- Uses HubSpot API to search, count, and fetch CRM objects and properties
- Analyzes data based on strong identifiers and lifecycle/stage consistency
- Returns actionable counts, examples, and recommendations for cleanup
SKILL.md
.github/skills/hubspot-crm-data-hygieneView on GitHub ↗
--- name: hubspot-crm-data-hygiene description: Use when auditing HubSpot data quality for missing fields, stale records, duplicates, associations, owners, or cleanup tasks. --- # HubSpot CRM Data Hygiene Identify cleanup needs across contacts, companies, deals, and tickets. Follow [../hubspot/SKILL.md](../hubspot/SKILL.md) for access, URLs, pagination, and write approvals. ## Workflow 1. Call `get_user_details` and confirm read access to the requested object types. 2. Clarify issue classes: missing fields, stale records, duplicate-like records, owner gaps, associations, lifecycle/stage issues, or imports. 3. Discover properties with `search_properties`: contact email/phone/company/owner/lifecycle; company name/domain/website/owner; deal stage/pipeline/amount/close date; ticket subject/stage/priority/category/owner. 4. Use `get_properties` for enums, then `search_crm_objects` count queries with `NOT_HAS_PROPERTY`, `HAS_PROPERTY`, filters, and `associatedWith`. 5. For duplicate-like checks, prefer strong keys: contact email, company domain/website, phone, or deal name plus associated company. If aggregation is unavailable, sample and say so. 6. Fetch examples with `get_crm_objects` only when current values affect cleanup. ## Issue Classes - Missing routing or identity fields. - Stale activity, old modified dates, past close dates, or unresolved ticket age. - Broken associations, inconsistent lifecycle/stage values, or duplicate-like records sharing strong identifiers. ## Output Return coverage, top issues with counts, example URLs, why each issue matters, recommended fix, cleanup backlog, human-review items, and caveats. Do not auto-merge duplicates or overwrite fields. For writes, use the core confirmation table.