Agent skill · marketing growth · jeremylongshore
instantly-core-workflow-a
Build and launch an Instantly API v2 campaign through an approval-gated, reversible workflow. Use when creating a campaign from a reviewed audience, schedule, and sequence specification. Trigger with "create an Instantly campaign", "launch an Instantly sequence", or "build campaign from spec".
Why this skill is useful
Provides specific API commands and workflows for launching cold email campaigns using Instantly API v2 that the AI wouldn't reliably generate on its own.
What it needs
Requires instantly account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Governed Instantly Campaign Launch Overview Create a campaign from reviewed inputs, load approved leads, validate sending state, and require explicit activation approval. 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 Campaigns use REST API v2 resources and scoped keys. Lead listing is POST /leads/list because filters are complex; bulk lead addition supports at most 1,000 leads per request. Campaign activation is a separate mutation and must not be implicit in creation. 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. Read the campaign specification, consent basis, suppression rules, sending accounts, schedule, and rollback owner. 2. Resolve workspace identity and use campaigns/leads scopes no broader than required. 3. Create or patch a draft campaign with bounded sequences and approved variables. 4. Import a small deduplicated synthetic or approved lead cohort and inspect rejected rows. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-core-workflow-a