Agent skill · marketing growth · jeremylongshore

instantly-data-handling

Govern Instantly lead, email, suppression, export, and deletion data with explicit privacy controls. Use when mapping personal-data flows or reviewing an export, suppression, retention, or erasure request. Trigger with "map Instantly data flows", "export Instantly leads safely", or "handle an Instantly deletion request".

Why this skill is useful

Provides specific API commands and compliance handling for Instantly.ai that the AI wouldn't reliably generate on its own.

What it needs

Requires instantly account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Instantly Lead Data Governance Overview Map and constrain personal-data movement across lead ingestion, campaigns, webhooks, exports, logs, and deletion. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result. Prerequisites The target repository, Instantly workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved API v2 key only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output. Current Contract Lead payload values may be scalar values; nested arrays are not a safe assumed contract. Webhook payloads can contain lead and full reply/email content. Deletion and export behavior must be tied to customer policy and signed terms, not generic assumptions. Authentication Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions. Instructions 1. Classify every input field, purpose, legal basis, retention owner, and downstream destination. 2. Map create, list, patch, export, webhook, and delete paths with exact scopes. 3. Minimize payloads and apply blocklist, consent, suppression, and deduplication controls before import. 4. Redact email bodies, reply text, API keys, and personal identifiers from logs and evidence. 5. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/instantly-data-handling

View the source on GitHub

Browse the @skills marketplace