instantly-debug-bundle
Automates the collection of diagnostic data from Instantly.ai, including campaign state and error logs, for technical support.
Install
mkdir -p .claude/skills/instantly-debug-bundle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3390" && unzip -o skill.zip -d .claude/skills/instantly-debug-bundle && rm skill.zipInstalls to .claude/skills/instantly-debug-bundle
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Collect Instantly.ai debug evidence for support tickets and troubleshooting.Key capabilities
- →Collect Instantly workspace information and campaign states
- →Retrieve Instantly email account details and warmup analytics
- →Gather Instantly webhook configurations and event summaries
- →List recent Instantly background jobs and lead counts per campaign
- →Generate a JSON report of Instantly diagnostic data
- →Identify broken email accounts with SMTP/IMAP/DNS status
How it works
The skill collects various data points from the Instantly API, including workspace, campaigns, accounts, webhooks, and background jobs, then compiles them into a JSON report and provides a console summary.
Inputs & outputs
When to use instantly-debug-bundle
- →Collecting evidence for Instantly support tickets
- →Auditing campaign warmup and health metrics
- →Investigating failed webhook deliveries
- →Generating environment state reports for debugging
About this skill
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
- Define the failing operation, time window, workspace, incident owner, and evidence destination.
- Collect client version, route templates, statuses, request IDs, and timestamps.
- Query only aggregate campaign, account, job, and webhook health needed for the incident.
- Replace workspace, campaign, account, lead, and email identifiers with stable opaque labels.
- Scan the bundle for bearer tokens, addresses, message text, and unrestricted environment output.
- Present the manifest and obtain approval before transmitting it outside the team.
Approval Boundaries
Do not create, rotate, reveal, or revoke keys; invite or remove members; delegate across workspaces; connect sending accounts; create or activate campaigns; import or delete leads; change suppression or retention; register, patch, resume, or delete webhooks; alter plans or paid capacity; transmit diagnostics; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.
Output
Return the workspace-safe scope, files and contracts inspected, exact API v2 routes and required scopes, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.
Error Handling
| Condition | Response |
|---|---|
401 | Stop and verify that the bearer key exists, is current, and was not revoked. |
403 | Stop and compare the operation with its exact required scope; do not broaden to all:all by default. |
429 | Coordinate the workspace-wide budget, honor endpoint overrides, and bound retries. |
| Schema or tenant mismatch | Fail closed, preserve redacted evidence, and do not retry a mutation. |
Examples
Use a compact handoff that makes scope, mutation authority, and evidence reviewable.
Input:
incident=INC-123; window=30m; include-bodies=false
Expected handoff:
bundle=diagnostics.json; identifiers=tokenized; disclosure=not-sent
Resources
When not to use it
- →When the API key lacks `all:read` scope for all resources
- →When only a partial bundle is needed due to size constraints
Prerequisites
Limitations
- →API key must have `all:read` scope for full bundle collection
- →Warmup analytics may be empty if no accounts have warmup enabled
- →Bundle size can be large with many campaigns and accounts
How it compares
This skill automates the collection of specific Instantly.ai diagnostic data into a structured report, which is more efficient than manually querying each API endpoint.
Compared to similar skills
instantly-debug-bundle side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| instantly-debug-bundle (this skill) | 1 | 2mo | Review | Beginner |
| godot | 1,044 | 7mo | Review | Intermediate |
| python-testing-patterns | 77 | 4mo | Review | Intermediate |
| error-handling-patterns | 35 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
unreal-engine-cpp-pro
sickn33
Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.