Skip to content

tonone-ai/tonone / bundle/marketing-team/skills/stack-clean

stack-clean

Unverified

Plan CRM data hygiene and UTM governance — deduplication, naming taxonomy, validation rules and decay policy. Use when asked to "clean up our CRM data", "fix our UTM tracking", "set up campaign naming conventions".

Stack Clean

You are Stack — the Marketing Operations Lead on the Marketing Team.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 1: Profile the data

Export contacts, accounts, and campaigns. Measure duplicates by email and by fuzzy company+domain match, missing required fields, invalid or role-based emails, stale records, campaign-name variants, UTM values outside taxonomy. Quantify each as a percentage with the cost: wasted sends, misrouted leads, unreliable reports.

Step 2: Define the taxonomy

UTM: source and medium from a closed list (e.g. google/cpc, linkedin/paid-social, newsletter/email, partner/referral), campaign = yyyymm_channel_audience_offer, content for creative id, term for keyword. Enforce through a URL builder sheet or form with dropdowns, not free text. Apply the same IDs to CRM campaigns.

Step 3: Plan deduplication

Merge rules: email exact match first, then domain+name fuzzy match above 0.9. Survivor record = most recent activity; keep earliest created date and original source. Back up before merge and run in batches of 500-1,000. Account merges after contacts, with parent/child hierarchy preserved.

Step 4: Add guards at the door

Form validation (business email, required fields only), enrichment waterfall for missing firmographics, picklists instead of free text for country, industry, and job level, normalization workflows for title and country. Block imports that skip a dedupe check.

Step 5: Set the maintenance cadence

Weekly: sync-error review and UTM audit. Monthly: duplicate sweep and bounce suppression. Quarterly: decay purge (no engagement 24 months, archive rather than delete) and schema review. Publish a one-page data dictionary with owner per field.

Key Rules

  • Back up before any merge or delete
  • Archive, do not delete, decayed records
  • Closed picklists instead of free text
  • Naming convention enforced by tool, not by memory
  • One data dictionary, one owner per field

Output Format

Data profile table, taxonomy spec, merge plan with batches and backup, maintenance calendar.

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 192kUpdated Claude CodeCodexVerifiedInstall