crm-cleanup
$
npx mdskill add anthropics/knowledge-work-plugins/crm-cleanupCleans HubSpot data by fixing stale deals, duplicates, and missing fields.
- Removes outdated records and merges duplicate contact entries automatically.
- Integrates with HubSpot API to read deals and contact records.
- Analyzes activity dates and field completeness before proposing fixes.
- Shows full audit lists and waits for owner approval before acting.
SKILL.md
.github/skills/crm-cleanupView on GitHub ↗
--- name: crm-cleanup description: Scans HubSpot for stale deals, duplicate contacts, and missing fields, then fixes what the owner approves. Accepts optional scope argument for deals, contacts, or all. allowed-tools: Read, WebFetch, Bash --- Run a HubSpot hygiene pass using the `crm-maintenance` skill cleanup workflow. Act immediately — the user typed /crm-cleanup, so skip the intent-detection step. Parse arguments: - `--scope` (default: `all`) — `deals` for deal audit only, `contacts` for contact dedup only, `all` for both ## Step 1 — Scan for stale deals If scope includes deals: 1. Pull all open deals from HubSpot. 2. Flag deals with no activity (email, call, meeting, note) in the last 14 days. 3. For each stale deal: show deal name, stage, last activity date, associated contacts, and amount. 4. Propose actions per deal: update next-step, change stage, add a note, or close-lost. Present the full stale-deals list before making any changes. ## Step 2 — Scan for duplicate contacts If scope includes contacts: 1. Search HubSpot contacts for likely duplicates (same email, similar names, same company + similar name). 2. For each duplicate set: show both records side-by-side — name, email, company, deals, last activity. 3. Propose which record to keep and which fields to merge. Present all duplicate sets before merging anything. ## Step 3 — Scan for missing required fields 1. Check all open deals for missing fields: close date, amount, deal stage, associated contact, next-step/notes. 2. Check contacts associated with open deals for missing fields: email, company, phone. 3. Present a table of records with missing fields and what's missing. ## Step 4 — Apply approved fixes 1. Walk through each finding from Steps 1-3. 2. Apply only the changes the owner explicitly approves. 3. Report each change as it's made with a HubSpot link. ## Connector failures If HubSpot is unreachable, stop — this command requires HubSpot as the data source. Tell the owner: "HubSpot isn't connected. Connect it in Cowork settings, then rerun /crm-cleanup." ## Approval gates - **Never delete records.** Not contacts, not deals, not activities. If the user asks, say the skill cannot and direct them to HubSpot. - **Never change deal stage or close a deal without explicit approval.** Even if evidence is strong. Flag and defer. - **Never auto-merge duplicate contacts.** Show side-by-side and wait for approval per pair. - **Side-by-side diffs for all changes.** Show current value and proposed value; wait for approval per item. ## Output End with a summary: X deals updated, Y contacts merged, Z fields filled. Include links to the affected records.
More from anthropics/knowledge-work-plugins
- accessibility-reviewRun a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
- account-research"Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question."
- analyzeAnswer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
- architectureCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
- audit-supportSupport SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
- brand-reviewReview content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
- brand-voice-enforcement>
- briefGenerate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
- build-dashboardBuild an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
- build-zoom-botBuild a Zoom meeting bot, recorder, or real-time media workflow. Use when joining meetings programmatically, processing live media or transcripts, or combining Meeting SDK, RTMS, and backend services.