IN

instantly-prod-checklist

A pre-flight checklist for validating Instantly.ai campaigns before launching in production.

Install

mkdir -p .claude/skills/instantly-prod-checklist && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8662" && unzip -o skill.zip -d .claude/skills/instantly-prod-checklist && rm skill.zip

Installs to .claude/skills/instantly-prod-checklist

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Execute Instantly.ai production launch checklist and pre-flight validation.
75 charsno explicit “when” trigger
Advanced

Key capabilities

  • Verify SMTP and IMAP account health
  • Validate warmup analytics and inbox rates
  • Audit campaign configuration settings
  • Perform lead list hygiene checks
  • Verify webhook event delivery

How it works

The workflow systematically tests account vitals, campaign settings, and lead list quality to ensure deliverability before activating a cold email campaign.

Inputs & outputs

You give it
Campaign ID and account credentials
You get back
Launch readiness report

When to use instantly-prod-checklist

  • Verifying email account health
  • Validating lead list hygiene
  • Testing campaign configurations
  • Setting up campaign webhooks
  • Auditing deliverability readiness

About this skill

Instantly Production Checklist

Overview

Pre-flight checklist for launching Instantly cold email campaigns in production. Covers account warmup verification, deliverability testing, lead list hygiene, campaign configuration, webhook setup, and monitoring. Skip any step that doesn't apply to your use case.

Prerequisites

  • Completed instantly-install-auth setup
  • Email accounts connected and warmed up (minimum 14 days recommended)
  • Lead list prepared with verified emails

Production Launch Checklist

Phase 1: Account Health (2-4 weeks before launch)

import { instantly } from "./src/instantly";

async function phase1AccountHealth() {
  console.log("=== Phase 1: Account Health ===\n");

  // 1. Verify all accounts have healthy SMTP/IMAP
  const accounts = await instantly<Array<{ email: string }>>(
    "/accounts?limit=100"
  );
  const vitals = await instantly("/accounts/test/vitals", {
    method: "POST",
    body: JSON.stringify({ accounts: accounts.map((a) => a.email) }),
  }) as Array<{ email: string; smtp_status: string; imap_status: string }>;

  const broken = vitals.filter((v) => v.smtp_status !== "ok" || v.imap_status !== "ok");
  console.log(`Accounts: ${accounts.length} total, ${broken.length} broken`);
  if (broken.length > 0) {
    console.log("FIX THESE FIRST:");
    broken.forEach((v) => console.log(`  ${v.email}: SMTP=${v.smtp_status} IMAP=${v.imap_status}`));
    return false;
  }

  // 2. Verify warmup is active and healthy
  const warmup = await instantly("/accounts/warmup-analytics", {
    method: "POST",
    body: JSON.stringify({ emails: accounts.map((a) => a.email) }),
  }) as Array<{ email: string; warmup_emails_landed_inbox: number; warmup_emails_sent: number }>;

  for (const w of warmup) {
    const inboxRate = (w.warmup_emails_landed_inbox / (w.warmup_emails_sent || 1)) * 100;
    const healthy = inboxRate >= 80;
    console.log(`  ${w.email}: inbox rate ${inboxRate.toFixed(1)}% ${healthy ? "OK" : "LOW — extend warmup"}`);
  }

  // 3. Check daily limits are set
  const acctDetails = await instantly<Array<{ email: string; daily_limit: number | null }>>(
    "/accounts?limit=100"
  );
  const noLimit = acctDetails.filter((a) => !a.daily_limit);
  if (noLimit.length > 0) {
    console.log(`\nWARNING: ${noLimit.length} accounts have no daily limit set`);
  }

  return broken.length === 0;
}

Phase 2: Campaign Configuration (1 week before)

async function phase2CampaignConfig(campaignId: string) {
  console.log("\n=== Phase 2: Campaign Configuration ===\n");
  const campaign = await instantly<{
    name: string;
    sequences: Array<{ steps: Array<{ variants: Array<{ subject: string; body: string }> }> }>;
    campaign_schedule: { schedules: any[] };
    daily_limit: number | null;
    stop_on_reply: boolean;
    link_tracking: boolean;
    open_tracking: boolean;
    stop_on_auto_reply: boolean;
    email_gap: number;
  }>(`/campaigns/${campaignId}`);

  const checks = [
    { label: "Has sequences", pass: campaign.sequences?.length > 0 },
    { label: "Has email steps", pass: campaign.sequences?.[0]?.steps?.length > 0 },
    { label: "Has schedule", pass: campaign.campaign_schedule?.schedules?.length > 0 },
    { label: "Stop on reply enabled", pass: campaign.stop_on_reply === true },
    { label: "Link tracking disabled", pass: campaign.link_tracking === false },
    { label: "Open tracking enabled", pass: campaign.open_tracking === true },
    { label: "Daily limit set", pass: (campaign.daily_limit ?? 0) > 0 },
    { label: "Email gap >= 60s", pass: (campaign.email_gap ?? 0) >= 60 },
  ];

  let allPass = true;
  for (const check of checks) {
    console.log(`  ${check.pass ? "PASS" : "FAIL"}: ${check.label}`);
    if (!check.pass) allPass = false;
  }

  // Check A/B variants
  const step1 = campaign.sequences?.[0]?.steps?.[0];
  if (step1) {
    console.log(`  INFO: Step 1 has ${step1.variants.length} variant(s)`);
  }

  return allPass;
}

Phase 3: Lead List Hygiene

async function phase3LeadHygiene(campaignId: string) {
  console.log("\n=== Phase 3: Lead List Hygiene ===\n");

  // Check lead count
  const analytics = await instantly<{ total_leads: number }>(
    `/campaigns/analytics?id=${campaignId}`
  );
  console.log(`Total leads: ${analytics.total_leads}`);

  // Check block list
  const blocklist = await instantly<Array<{ bl_value: string }>>(
    "/block-lists-entries?limit=10"
  );
  console.log(`Block list entries: ${blocklist.length}+`);

  // Verify no internal domains are in lead list
  console.log("\nChecklist:");
  console.log("  [ ] Leads verified with email verification service");
  console.log("  [ ] Company domains in block list (your own + competitors)");
  console.log("  [ ] No role-based emails (info@, admin@, support@)");
  console.log("  [ ] Personalization variables populated (firstName, companyName)");
  console.log("  [ ] Test lead (your own email) included for QA");
}

Phase 4: Test Email & Webhook Verification

async function phase4TestAndWebhooks(campaignId: string) {
  console.log("\n=== Phase 4: Test & Webhooks ===\n");

  // Send test email
  const accounts = await instantly<Array<{ email: string }>>(
    "/accounts?limit=1"
  );
  if (accounts.length > 0) {
    await instantly("/emails/test", {
      method: "POST",
      body: JSON.stringify({
        eaccount: accounts[0].email,
        to_address_email_list: [process.env.TEST_EMAIL || "[email protected]"],
        subject: "Production Test — Instantly Integration",
        body: "This is a test email from the Instantly integration. If you received this, the setup is working correctly.",
      }),
    });
    console.log("Test email sent from:", accounts[0].email);
  }

  // Verify webhooks are registered
  const webhooks = await instantly<Array<{
    name: string; event_type: string; target_hook_url: string;
  }>>("/webhooks?limit=50");
  console.log(`\nWebhooks registered: ${webhooks.length}`);
  for (const w of webhooks) {
    console.log(`  ${w.name}: ${w.event_type} -> ${w.target_hook_url}`);
  }

  // Test webhook delivery
  if (webhooks.length > 0) {
    for (const w of webhooks.slice(0, 2) as Array<{ id: string; name: string }>) {
      try {
        await instantly(`/webhooks/${w.id}/test`, { method: "POST" });
        console.log(`  Tested: ${w.name} — check your endpoint`);
      } catch (e: any) {
        console.log(`  FAILED: ${w.name} — ${e.message}`);
      }
    }
  }
}

Phase 5: Launch & Monitor

async function phase5Launch(campaignId: string) {
  console.log("\n=== Phase 5: Launch ===\n");

  // Final confirmation
  const campaign = await instantly<{ name: string; status: number }>(
    `/campaigns/${campaignId}`
  );
  console.log(`Campaign: ${campaign.name} (status: ${campaign.status})`);

  // Activate
  await instantly(`/campaigns/${campaignId}/activate`, { method: "POST" });
  console.log("Campaign ACTIVATED");

  // Verify sending status
  const status = await instantly(`/campaigns/${campaignId}/sending-status`);
  console.log("Sending status:", JSON.stringify(status));

  // Monitor for first hour
  console.log("\nPost-launch monitoring:");
  console.log("  [ ] Check analytics after 1 hour for send activity");
  console.log("  [ ] Monitor bounce rate (should be <3%)");
  console.log("  [ ] Verify webhook events are arriving");
  console.log("  [ ] Check Unibox for replies");
}

// Run full checklist
async function main() {
  const campaignId = process.env.CAMPAIGN_ID!;
  const accountsOk = await phase1AccountHealth();
  if (!accountsOk) { console.log("\nFix account issues before proceeding."); return; }
  const configOk = await phase2CampaignConfig(campaignId);
  await phase3LeadHygiene(campaignId);
  await phase4TestAndWebhooks(campaignId);
  if (configOk) await phase5Launch(campaignId);
}

main().catch(console.error);

Error Handling

ErrorCauseSolution
Campaign won't activateMissing sequences/accounts/leadsRun Phase 2 checks
Test email not receivedAccount SMTP brokenRun vitals test
Webhook test failsTarget URL unreachableVerify endpoint is public HTTPS
High bounce rate post-launchUnverified leadsPause campaign, clean list

Resources

Next Steps

For version migration, see instantly-upgrade-migration.

When not to use it

  • When email accounts have not been warmed up
  • When lead lists are unverified

Prerequisites

instantly-install-auth setupWarmed up email accountsVerified lead list

Limitations

  • Requires minimum 14 days of warmup
  • Bounce rate monitoring is required post-launch

How it compares

This workflow automates the pre-flight validation of email infrastructure, reducing the risk of account bans or poor deliverability compared to manual setup.

Compared to similar skills

instantly-prod-checklist side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
instantly-prod-checklist (this skill)027dCautionAdvanced
unity-editor-toolkit106moReviewAdvanced
workflow42moReviewIntermediate
listener-creator29moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

unity-editor-toolkit

Dev-GOM

Automate and control Unity Editor with 500+ commands, real-time WebSocket communication, and SQLite integration for efficient game development.

10126

workflow

vercel

Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", or step-based orchestration.

431

listener-creator

anthropics

Creates event-driven email listeners that monitor for specific conditions (like urgent emails from boss, newsletters to archive, package tracking) and execute custom actions. Use when user wants to be notified about emails, automatically handle certain emails, or set up email automation workflows.

212

setup-build-tools

aaddrick

Install build and extraction tools needed for building Claude Desktop Debian packages

212

macos-spm-app-packaging

Dimillian

Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.

17

railway-templates

davila7

Search and deploy services from Railway's template marketplace. Use when user wants to add a service from a template, find templates for a specific use case, or deploy tools like Ghost, Strapi, n8n, Minio, Uptime Kuma, etc. For databases (Postgres, Redis, MySQL, MongoDB), prefer the railway-database skill.

15

Search skills

Search the agent skills registry