Agent skill · software engineering · jeremylongshore
instantly-reference-architecture
Design an Instantly API v2 integration with tenant isolation, durable jobs, webhooks, and governance boundaries. Use when choosing system boundaries before implementation or reviewing an existing design. Trigger with "design an Instantly architecture", "review Instantly tenant isolation", or "plan an Instantly integration platform".
Why this skill is useful
Adds a complete reference architecture with executable scripts and project layout for Instantly.ai integrations that aren't publicly documented.
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 Reference Architecture Overview Produce a repo-grounded architecture that separates control-plane approvals from outreach mutations. 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 official API v2, the beta TypeScript SDK when appropriate, or the official CLI/MCP deliberately. Model workspace-wide throttling, cursor pagination, background jobs, and webhook delivery as first-class components. Keep campaign activation, account connection, key changes, and data deletion behind separate approvals. 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. Map callers, workspaces, data stores, queues, secret managers, webhook receivers, and owners. 2. Define a typed client boundary with scoped authentication, redaction, timeouts, and rate control. 3. Separate read models, command handlers, background-job polling, and webhook idempotency. 4. Define tenant/workspace identity checks and x-as-workspace safeguards. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-reference-architecture