ClaudeSuperPower
SubmitLog in

data-cleanup

Skill

Check your CRM board's health and clean up messy data — run a scored health check (missing fields, stalled deals, abandoned columns, automation gaps) as a report, or fix data in bulk (phone formats, missing emails, country codes, unowned deals, stale dates). Use when someone says "clean my CRM", "fi

0Sales

Install

git clone https://github.com/mondaycom/mcp.git ~/.claude/skills/data-cleanup

What is data-cleanup?

Check your CRM board's health and clean up messy data — run a scored health check (missing fields, stalled deals, abandoned columns, automation gaps) as a report, or fix data in bulk (phone formats, missing emails, country codes, unowned deals, stale dates). Use when someone says "clean my CRM", "fix my data", "normalize my phone numbers", "fill in missing owners", "run a board health check", "audit my CRM board", "what's broken in my CRM", "what are the data gaps on my board", "board is messy", or "clean up before my kickoff call".

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Read files only

Read-only tools

~135 tokens of context used while enabled, before you invoke anything

All declared tools (16)
AskUserQuestionReadmcp__monday__all_monday_apimcp__monday__board_insightsmcp__monday__change_item_column_valuesmcp__monday__create_docmcp__monday__create_notificationmcp__monday__create_updatemcp__monday__get_board_activitymcp__monday__get_board_infomcp__monday__get_board_items_pagemcp__monday__get_column_type_infomcp__monday__get_user_contextmcp__monday__list_users_and_teamsmcp__monday__list_workspacesmcp__monday__search

Documentation

README · ~15 min read

Data Cleanup

Two jobs in one skill for the recurring "my CRM is messy" pain (Sidekick's #1 negative-sentiment JTBD):

  • Health check (report-only): a scored structural audit of a CRM board — missing-data patterns, stalled groups, abandoned columns, automation gaps, and a 0–100 data-quality score — published as a diagnosis doc. No writes.
  • Cleanup (fix): audit the board for data gaps, let the user pick which to fix, then run a bounded, idempotent write loop.

Flow (report): Trigger → Gather → Score (5 strands) → Publish diagnosis doc → offer to fix. Flow (fix): Trigger → Audit → User picks gaps → Plan writes → Execute (bounded, idempotent) → Summary.

Input

  • Optional: board name/ID via argument.
  • Optional: pre-declared mode (Default / Silent / Proactive).

Output

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.