Delete No Email Contacts

This skill appears to implement what it claims, but take these precautions before installing or running it: - Verify credentials: The scripts expect a HubSpot private app access token (HUBSPOT_ACCESS_TOKEN) with crm.objects.contacts.read and crm.objects.contacts.write scopes. The registry metadata does not declare this — do not proceed until you confirm where the token will come from and that it's least-privilege. - Review the code: Inspect before.py and the CSV produced to ensure the contacts targeted are the ones you intend to remove. - Run in stages: Run before.py first, review the generated data/no-email-contacts-before.csv, and only run execute.py after manual confirmation. The scripts already ask for a manual 'DELETE' confirmation but verify the CSV yourself first. - Adjust safety thresholds: The scripts include SAFETY_THRESHOLD/ABORT_THRESHOLD values. Set these conservatively (based on your before-state count) to avoid mass accidental deletion. - Secure the token: The scripts load a .env file in the repository root. Storing tokens in plaintext files has risk — prefer setting the token in your environment or a secure secrets manager and avoid committing .env to source control. After use, consider rotating the token. - Dependencies: The package metadata is only in script comments; ensure you have Python 3.10+ and install requests and python-dotenv before running. - Test in a safe environment: If possible, test against a HubSpot sandbox or a copy of your data first. Because the manifest fails to disclose the required credential, treat the registry entry as incomplete and proceed cautiously.