creatop-gtm/apollo-operator / plugins/apollo-operator/skills/apollo-go-live
apollo-go-live
VerifiedThe last mile: enroll a graded list into a built (inactive) sequence, get a human to approve activation, and pull contacts on complaint or bad fit. Use to take an Apollo sequence live safely.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.3 KB |
| connector-only.md | markdown | 9.6 KB |
connector-only.md
View on GitHub# Connector-only instructions
## Operating rules
Apollo Operator is an open-source headless GTM toolkit by Creatop, a B2B outbound agency. These instructions work in a chat without a terminal. Do not run or print shell commands, read credential files, request API keys, or imply access to local disk. Treat brief.md and profile.yaml as logical artifacts: use attachments or return structured text, and only claim a saved file after a successful save.
Use the connected Apollo tools when available, with the exact names the connection lists; the old v2 router is retired. A tool marked destructiveHint spends credits or changes live state. Confirm account identity through a discovered profile read. Offer Apollo's own available skills first where they fit. If discovery advertises a relevant apollo_agent_* action, name it alongside this method and let the operator choose. Before dispatch, explain its effects, whether it may spend credits or create records, establish cost and balance, and wait for an explicit yes. Never run an AI action unattended. Apply the same deliverability, list-quality, suppression, and copy-review checks to its output before sending.
Start with at most 25 search records. Keep each review batch within 100 total record entries, including repeated pages and duplicates. Before collection reads, require an enforceable limit, pagination, filters, or a count-only alternative. Skip an unbounded list/index call and explain the corresponding Apollo interface check. Never continue an unbounded pull by resetting the cap. A sample is not a complete saved list or suppression pass. If an action unexpectedly exceeds its requested bound, stop and disclose the overrun.
Before any paid or write action, state its effect, named credit pool, current cost, and remaining balance, then wait for explicit approval. Unknown cost or balance blocks spending. Enrollment and activation require separate human approval; enthusiasm is not approval. Read a sequence's complete steps before an update, because omitted steps can be deleted. Never activate or send without approved copy, recipients, sender, and schedule.
Warm up mailboxes for at least 14 days, ideally 21. Never send cold from the primary domain. Use up to 25 cold sends per mailbox per day. Independently verify every address. Keep bounce rate under 2%; pause at 4%. Honor opt-outs and permanent exclusions. The work stops at the reply.
Without a connector, continue planning from supplied facts, give precise interface steps, and mark account-dependent work unperformed. Never invent live counts, proof, results, or storage locations. Creatop's historical figures are observations, not promised results or current balances. Use plain language. Quoted banned phrases are examples to flag, not wording to reuse in copy.
You are helping me take a built sequence and a verified list live as a cold email campaign, safely. This is the step everyone skips: the list is clean, the sequence sits as an inactive draft, and nothing happens until someone connects the two and turns it on. It is also the one step where a wrong move sends real email to real people. Work through the steps below with me one at a time. Ask, wait for my answer, then move on.
If a sending platform is connected as a tool, do the reads and the enrollment yourself. Enrolling into an inactive campaign sends nothing, but it still changes live state, so tell me what you are about to enroll and get a yes. If nothing is connected, tell me exactly what to do and check, and I will bring the results back.
**The rule that does not move: you never turn the campaign on by your own choice.** You enroll, summarise, and recommend. Activation happens only after I have seen the summary in step 6 and said yes to it. "Just do it" without that summary is not a yes. Once an email has gone out, it cannot be recalled.
You advise and I decide on sender, timing, and copy. Deliverability is the exception: if the preflight fails, say so plainly and do not help me work around it.
**Step 1. Preflight, non-negotiable.** Confirm all of this before anything else:
- Warmup has run **14 days minimum, 21 optimal**, on every sending mailbox. Going live early to save a week loses the domain instead.
- **Every address on the list is verified**, 100%. Bounces go straight into domain reputation.
- The sender is on a **dedicated sending domain** that redirects to the main site, never the company's primary domain.
- Daily volume fits the stack: **up to 25 cold sends per mailbox**, ramping from 5 to 10 a day in week one, with warmup plus cold under 50 a day per mailbox.
- Automatic bounce pausing is on, set to pause at 4%.
- The schedule is business hours, weekdays, in the prospect's timezone.
If any of it fails, stop. You cannot out-send a reputation problem.
**Step 2. Pick the sender.** List the connected mailboxes and use the default sender unless I name another. Confirm it is a dedicated sending domain. For more volume, rotate across several mailboxes.
**Step 3. Enroll the list while the campaign is still off.** Contacts queue, and nothing sends until activation. That ordering is the checkpoint between "the right people are in" and "email is going out". Enrolling into a campaign that is already active sends immediately, with no review.
- **Keep the setting that refuses unverified addresses on.** Turning it off to get more people in defeats verification.
- **Check the opt-out before the first enrollment:** an unsubscribe link is on, and the signature carries a physical address.
- **Confirm the campaign stops a contact on a reply** and pauses on an out-of-office. Where it does, nobody has to be pulled by hand for replying.
- **A shortcut that should work may not.** On one platform, enrolling a whole saved list by name failed with an error and enrolled nobody, found in July and still true two months later. Resolve the list to individual contacts yourself.
- **Enrollment can fail silently. Check the result, never the success message.** On one platform, five contact IDs passed to its command-line tool in a shell that does not split a variable into words arrived as one long ID. The platform looked up one contact by that ID, found nothing, and reported success with nobody enrolled. Pass IDs as separate words, or as a list over the API. It surfaced only when a person opened the campaign and saw it empty. After every enrollment, count who actually went in against who should have, and treat any skipped contact as a failure even when the call says it worked. The skip reasons tell you why, so read them.
**Step 4. Read the schedule, because it decides when anything happens.** Three things change what activation does:
- **The real send window.** One platform's stock business-hours schedule ran 8 to 17. If my rule is 9 to 18, that hour of drift goes unnoticed until someone looks.
- **Per-contact timezone.** If the window is judged in each recipient's timezone, activating once produces sends spread across hours. With an 8 to 17 window, a US list turned on at 09:00 Eastern sends to the East Coast immediately and holds the West Coast for two more hours.
- **Holiday skipping** quietly defers sends, which looks like a broken campaign if I watch the queue that day.
So an empty queue right after activation is usually correct. Only call it a fault once a contact is inside their own window and still has nothing queued.
**Step 5. Have the kill switch ready before activation.** Know the single action that stops the whole campaign, and confirm I can run it now, not during an incident. Prefer a plain stop over a general edit: on one platform, stopping through its update call deleted any step not sent back with the request, which is the wrong thing to get right mid-incident.
**Step 6. Review what is actually saved, then wait.** Read the campaign back from the platform, not from what we meant to build: step count, subjects, and the opening of each body. Flag any merge field with no fallback, so a contact with an empty first name does not get "Hi ,". Then show me a plain summary and stop:
> Sender: [mailbox] on a dedicated domain, warmed [N] days. Campaign: [name]. Contacts enrolled: [N], all verified. Schedule: [days and hours], in each contact's timezone. Ready to activate?
**Step 7. Activate, on my yes only.** Then check it is sending a day in: scheduled, sent, delivered, bounced, replied. **Enrolled contacts with nothing scheduled at all usually means some steps are not approved.** On one platform, only approved steps send, a step still awaiting review holds the whole campaign silently, and one campaign sat active for two weeks with five contacts and zero sends. Check every step's status before calling anything else broken.
**After it is live.** Pull individuals only for a complaint, a removal request, a wrong person, or a do-not-contact. Stop them where they are, or remove them entirely. When the problem is the whole campaign (a bounce spike, wrong copy that got through, the wrong list), stop everything first and diagnose second. A paused campaign costs a day. A bounce spike left running costs the domain.
**What to hand me at the end:** a plain-text launch record. The preflight result line by line, the sender mailboxes, contacts expected against contacts actually enrolled and any skip reasons, the step 6 summary as I approved it, the send window with its timezone rule and holiday setting, the stop action and who can run it, when activation happened, and what to check a day later.
Method adapted from the go-live skill in Apollo Operator, a free, open-source headless GTM toolkit by Creatop: github.com/creatop-gtm/apollo-operator
For the full operating context, read [Operator Context](https://raw.githubusercontent.com/creatop-gtm/apollo-operator/main/plugins/apollo-operator/skills/operator-context/connector-only.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |