Agent skill · data analytics · jeremylongshore
instantly-common-errors
Diagnose Instantly API v2 authentication, scope, validation, quota, and resource errors without unsafe retries. Use when a request fails or returns an unfamiliar status or payload. Trigger with "debug Instantly 401", "fix Instantly 429", or "diagnose Instantly API error".
Why this skill is useful
Provides specific troubleshooting steps and API error handling patterns 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 API Error Triage Overview Turn an observed failure into a bounded diagnosis and a verified corrective action. 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 401 means missing, invalid, or revoked authorization; 403 means the key lacks a required scope. 429 is workspace-wide unless the endpoint publishes a stricter override. API errors expose statusCode, error, and message; do not infer success from a JSON body alone. 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. Capture the method, route template, status, request ID, and redacted response shape. 2. Separate authentication, authorization, payment, validation, absence, conflict, and throttling failures. 3. Check the live endpoint reference and exact required scope. 4. Reproduce with a synthetic read-only request where possible. 5. Apply the smallest configuration or code correction. 6. Record evidence and stop before any destructive retry. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-common-errors