Agent skill · data analytics · jeremylongshore
instantly-observability
Monitor Instantly API, campaign sending, account vitals, background jobs, and webhook delivery with safe telemetry. Use when defining dashboards, alerts, or service-level indicators for an Instantly integration. Trigger with "monitor Instantly API health", "alert on Instantly webhook failures", or "design Instantly telemetry".
Why this skill is useful
Adds specific monitoring scripts and integration patterns for Instantly.ai that the AI wouldn't reliably generate on its own.
What it needs
Requires 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 Integration Observability Overview Define actionable service signals without logging lead content, email bodies, or credentials. 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 campaign sending-status rather than inferring health from aggregate counts alone. Webhook event aggregate endpoints expose success/failure evidence. Workspace-wide rate limits require shared client telemetry across keys. 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 service-level indicators for request success, latency, 429s, job age, sending state, and webhook failures. 2. Instrument route templates, status classes, retry counts, request IDs, and workspace-safe labels. 3. Poll documented health and aggregate endpoints at a bounded cadence. 4. Redact API keys, addresses, lead payloads, reply content, and email bodies. 5. Set alerts against measured baselines with owner-reviewed thresholds. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-observability