How do we test CRM automation without risking production data?

Nobody should trust bulk deletes and workflow creation with production on the first run. HubSpot gives every account free developer test accounts; this skill turns one into a proving ground — seeded fixtures, end-to-end runs, a graded report, marker-scoped teardown — and refuses, in code, to run against anything that is not a sandbox.

Fix it with one command

The sandbox-self-test skill walks Claude Code through the entire fix — audit, CSV baseline, execution, and verification. Ready-to-run Python scripts included.

/plugin marketplace add tomgranot/hubspot-admin-skills
/plugin install hubspot-admin@hubspot-admin-skills
/sandbox-self-test

Frequently asked questions

How do I get a HubSpot sandbox for free?

Any HubSpot account can create up to 10 developer test accounts under Settings > Testing > Developer test accounts — free, with Enterprise-trial features, expiring after 90 days of API inactivity.

How does the harness avoid touching production?

Two locks: it only reads its own HUBSPOT_SANDBOX_ACCESS_TOKEN variable, and every script checks the portal’s accountType via the account-info API and refuses anything that is not DEVELOPER_TEST or SANDBOX. The check fails closed and has no override.

More audit & planning skills