The HubSpot cleanup you keep postponing, run by Claude Code
Duplicate companies, hard bounces still marked marketable, a third of your contacts missing a lifecycle stage. You know the backlog. These 37 open-source skills work through it: each one audits first, exports a CSV baseline, makes the change, and shows you the before/after.
What a cleanup actually looks like
Step 1: Audit
Run /hubspot-audit. Read-only API queries across eight dimensions: contacts, deliverability, duplicates, owners, lifecycle, lists, workflows, pipeline. Every finding gets a grade and the name of the skill that fixes it.
Step 2: Plan
Run /hubspot-implementation-plan. It orders the fixes by dependency: you can't score leads on firmographics nobody backfilled, so enrichment comes before scoring, hygiene before both.
Step 3: Execute
One skill per finding. Destructive skills export a CSV baseline before touching anything, stop at an abort threshold, and document the rollback. Workflows are created disabled so you review them in the UI first.
Step 4: Maintain
Prevention workflows screen new records at creation. /weekly-cleanup-routine is a five-minute check; /quarterly-database-cleanup handles the drift both miss.
Watch
See it in action
Skill categories
Skills for every phase of the CRM lifecycle
37 skills across six categories. 21 ship with ready-to-run Python scripts.
For AI agents
Built to be read by agents, not scraped
Point your agent at this site
If an agent does your HubSpot work, it can read this site directly and run any skill against your portal with your own token. Agent install guide →llms.txt and llms-full.txt
An index of every skill, and the full documentation in one fetch.
Raw markdown twins
Every skill page has a .md URL serving the SKILL.md verbatim, frontmatter included.
skills.json
The whole catalog as JSON: slugs, categories, script URLs, install commands.
FAQs
The questions that decide whether you run this
Is this safe to run against production?
The audit is read-only. Skills that change data export a CSV of every affected record first, show you what will change, ask before writing, and stop at an abort threshold. Run /sandbox-self-test against a free HubSpot developer test account if you want proof before granting a production token.
Where does my CRM data go?
Nowhere. There is no SaaS here. The skills are markdown instructions plus Python scripts that run on your machine, calling the HubSpot API with your own private app token. CSV exports stay in a local, gitignored folder.
What do I need?
Claude Code, a HubSpot private app token, and Python 3.10+ with uv for the scripted skills. Workflow skills need Marketing Professional or higher; the audit and hygiene skills work on any tier.
What if the audit finds something no skill covers?
It offers to write the skill on the spot, and to contribute it back as a pull request. The skill set grows out of real portals, not a roadmap.
Is this a HubSpot product?
No. Independent open source, built from years of administering HubSpot portals. It works inside your existing portal; nothing gets replaced. HubSpot is a trademark of HubSpot, Inc.
Two commands and you're auditing
/plugin marketplace add tomgranot/hubspot-admin-skills /plugin install hubspot-admin@hubspot-admin-skills