hubspot-attribution-auditorlisted

Audit deal-to-source revenue attribution in a CRM and surface likely misattributed revenue. Reconstructs credit under first-touch, last-touch, linear, and position-based models, flags deals whose recorded source conflicts with their touch history, scores each 0-100 by confidence, and quantifies dollars at risk and credit shift by channel. Use when the user says "audit attribution", "check deal attribution", "misattributed revenue", "attribution model", "which channel gets credit", "revenue attribution report", "clean up our attribution", or otherwise asks why a channel's numbers look wrong, whether marketing is over- or under-credited, where pipeline really came from, or to compare first-touch against last-touch. Works against live HubSpot via the connected MCP or a CSV export of deals. DEFAULTS TO A READ-ONLY DRY RUN — produces a report and correction CSV for human review, and writes to the CRM only when the user explicitly passes --apply and confirms.
aidan269/chewie-attribution-auditor · ★ 0 · Data & Documents · score 72

Install: claude install-skill aidan269/chewie-attribution-auditor

# Attribution auditor Reconstruct where deal revenue actually came from, compare that against what the CRM says, and hand back a report a human can act on. ## Operating principle: report first, write never (by default) Attribution fields feed budget decisions and comp plans. Overwriting them on a guess is worse than leaving them wrong, because a confidently wrong number gets spent against. **Every run is a dry run unless the user explicitly asks otherwise.** The scripts in this skill have no network access and no CRM write capability — they read CSVs and write local files. Even `--apply` does not write to a CRM; it emits a plan of proposed writes for a human to approve. The only thing that can touch the portal is you, through the HubSpot MCP, after Step 6. If the user opens with "just fix our attribution", still run the audit first and show them the report. They will change their mind about at least some rows — everyone does. ## Step 1 — establish the source and the ceiling Ask, and do not guess: 1. **Live HubSpot MCP, or a CSV export?** 2. **What scope?** Always prefer a **closed-won window** (e.g. last two quarters). Auditing open pipeline attributes revenue that may never arrive and inflates the headline number for no reason. 3. **Which field is the source of truth?** Many portals maintain a custom attribution property and let the built-in `hs_analytics_source` go stale. Ask which one the team actually maintains. Then establish **how much touch history