Agent skill · marketing growth · jeremylongshore
instantly-core-workflow-b
Analyze sending-account readiness, then connect and qualify Instantly accounts with OAuth, health checks, and controlled campaign assignment. Use when onboarding mailboxes or deciding which healthy accounts may join a campaign. Trigger with "connect Instantly sending accounts", "check Instantly mailbox health", or "assign accounts to a campaign".
Why this skill is useful
Adds specific API commands and workflows for managing email warmup and analytics that the AI wouldn't reliably generate on its own.
What it needs
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 Sending Account Onboarding Overview Onboard Google or Microsoft sending accounts without exposing credentials or assigning unhealthy accounts to live campaigns. 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 Google and Microsoft connections use an OAuth session URL followed by status polling. OAuth sessions expire after 10 minutes. Warmup enablement may return a background job that must be polled. 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. Confirm account ownership, provider, workspace, allowed domains, and change owner. 2. Create a least-privilege OAuth session and give the authorization URL only to the account owner. 3. Poll the session within its expiry window without logging tokens. 4. Test account vitals and capture only non-sensitive status fields. 5. Enable warmup or campaign assignment only after an explicit change approval. 6. Poll background jobs and produce per-account success and failure evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-core-workflow-b