instantly-prod-checklist
Execute Instantly.ai production launch checklist and pre-flight validation. Use when deploying Instantly integrations to production, launching first campaign, or auditing production readiness. Trigger with phrases like "instantly production", "instantly launch checklist", "instantly go-live", "instantly pre-flight", "instantly prod ready".
What this skill does
# 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)
```typescript
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)
```typescript
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
```typescript
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
```typescript
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
```typescript
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
| Error | Cause | Solution |
|-------|------Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".