Agent skill · data analytics · jeremylongshore
instantly-debug-bundle
Analyze an Instantly failure and collect a minimal redacted diagnostic bundle for campaigns, accounts, jobs, and webhook delivery. Use when engineering or support needs reproducible incident evidence without credentials or lead content. Trigger with "collect Instantly diagnostics", "prepare an Instantly support bundle", or "redact Instantly incident evidence".
Why this skill is useful
Adds a comprehensive JSON report generation script for debugging Instantly.ai that includes specific API calls and error handling.
What it needs
Requires curl, npm installed locally. 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
Redacted Instantly Diagnostic Bundle Overview Gather reproducible operational evidence without exporting credentials, lead data, or message bodies. 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 Use documented list, sending-status, vitals, background-job, and webhook-event aggregates. Raw lead, email, and webhook payloads may contain personal or message content. Support sharing is an external disclosure that needs owner review. 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. Define the failing operation, time window, workspace, incident owner, and evidence destination. 2. Collect client version, route templates, statuses, request IDs, and timestamps. 3. Query only aggregate campaign, account, job, and webhook health needed for the incident. 4. Replace workspace, campaign, account, lead, and email identifiers with stable opaque labels. 5. Scan the bundle for bearer tokens, addresses, message text, and unrestricted environment output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-debug-bundle