Agent skill · software engineering · jeremylongshore
instantly-local-dev-loop
Build an offline-first Instantly development loop with fixtures, fakes, and optional read-only staging probes. Use when developers need fast repeatable tests without mutating a live workspace. Trigger with "mock the Instantly API", "build Instantly fixtures", or "test Instantly locally".
Why this skill is useful
Provides specific integration patterns and mock server usage for Instantly API that the AI wouldn't reliably generate on its own.
What it needs
Requires node 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 Local Contract Loop Overview Develop safely without relying on an undocumented vendor mock endpoint or sending real outreach. 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 The documentation exposes interactive examples but does not establish a durable public mock API contract. Use local fakes and captured synthetic schemas for deterministic tests. Live probes require a staging workspace, read-only scopes, and bounded requests. 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. Inventory routes and generate or pin types from the official OpenAPI surface. 2. Create local fake responses for success, 401, 403, 429, pagination, and malformed data. 3. Use synthetic leads and messages; never copy production payloads into fixtures. 4. Run unit and contract tests without network access. 5. Optionally run one owner-approved read-only staging probe. 6. Update fixtures only after reviewed schema evidence and record the source date. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-local-dev-loop