Agent skill · marketing growth · jeremylongshore
instantly-incident-runbook
Analyze and triage Instantly campaign, account, webhook, job, and API failures with explicit containment approvals. Use when responding to a live degradation, delivery anomaly, or integration outage. Trigger with "triage an Instantly incident", "contain Instantly sending failure", or "investigate an Instantly outage".
Why this skill is useful
Adds executable scripts for triaging and mitigating Instantly.ai campaign issues that aren't available in public documentation.
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
Instantly Incident Response Overview Contain a production incident while preserving evidence, tenant boundaries, and reversible recovery actions. 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 Campaign pause, account pause, webhook resume, and key revocation are state-changing actions. Sending-status, account vitals, background jobs, and webhook aggregates provide documented evidence surfaces. Workspace-wide 429s require coordinated throttling across every key. 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. Declare severity, affected workspace, owner, time window, and customer impact. 2. Preserve redacted request IDs, statuses, deploy SHA, campaign state, and aggregate health. 3. Classify identity, scope, quota, sending, account, job, webhook, or provider failure. 4. Propose the smallest containment action with blast radius and rollback. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-incident-runbook