Apollo Operator

An open-source library of Claude Code skills that turns the raw Apollo MCP into a guided outbound motion. Free, and built by running it end to end on a live account.

WHAT A RUN LOOKS LIKE

001

apollo-operator / live run

apollo-operator / install prompt
Goal:
Install the Apollo Operator skills into this
Claude Code project, then confirm they can
reach Apollo.
 
Check first:
Run `claude --version`.
Run `apollo auth whoami` to test the Apollo CLI.
 
Install:
git clone \
https://github.com/creatop-gtm/apollo-operator
mkdir -p .claude/skills
cp -r apollo-operator/.claude/skills/* \
.claude/skills/
 
Do not edit the skills. Update by pulling.
 
Prerequisites, install only what is missing:
- Apollo MCP, connected in Claude Code.
- Apollo CLI:
brew install apolloio/apollo-io-cli/apollo-io-cli
- An email verification service of your choice.
 
Verify:
Load operator-context/SKILL.md and confirm the
eight phases resolve: Foundations, Context,
Targeting, Infrastructure, List, Message,
Launch, Iterate.
 
Then:
Run the Context phase to write brief.md before
any list or sequence work. Nothing sends
without my approval.
 
Success message:
Say Apollo Operator is installed and that the
first real step is Targeting, once brief.md
exists.

On the left, what running it looks like: you describe the job in plain language and the skills carry the method, routing between 17 of them across eight phases. On the right, the whole library in one prompt. Copy it into Claude Code and it installs itself, then asks for your context before it searches anything.

WHAT IS INSIDE

FIG. 01

FOUNDATIONS

operator context and voice

TARGETING

ICP, angles, signals

LIST

built, graded, suppressed

MESSAGE

sequences and personalization

LAUNCH

stop a send any time

THE LANES

four, not three

THE

LANES

Apollo can be driven four ways, and picking the right one decides what a job costs and whether it is possible at all

MCP

Apollo arrives as typed tools inside the model. Guardrailed and human-gated, and every result lands in the context window. Right for small record counts, and for anything that actually sends.

CLI binary

One terminal command, output straight to disk. Right for bulk search and enrichment on the common filters, and for any job you want to re-run later.

REST, CLI token

The lane most people miss. The token stored by apollo auth login already reaches the full filter surface, with disk output and no API key to manage.

API key

For building software that runs without a logged-in user. Useful, but not the lane you want when you are running a motion.

Shape

HOW IT BEHAVES

002

LEARNED BY

“Outbound is a system, relevance beats volume, deliverability is sacred, humans approve the copy.”

01

Title filters

A Founder filter also matches Founding Engineer. The list builder checks for that instead of trusting the count.

02

Pagination overlap

Overlapping pages are flagged before you pay to enrich the same person a second time.

03

Credit ceiling

A job that would cross 85% of your remaining credits stops and asks before it spends.

UPDATE HISTORY

001

v1.2.0July 29, 2026Feature

Four lanes, not three

Reading Apollo's full REST spec turned up a fourth access path: the CLI's own OAuth token reaches the complete MCP filter surface, with output written to disk and no API key needed. Numbered levels became named phases across all 17 skills, and re-engagement shipped as its own skill.

v1.1.0July 23, 2026Improvement

CLI awareness

Apollo shipped a command line tool and framed three lanes for running Apollo headless, so the library learned to route between them: MCP by default, the CLI for high-volume search and enrichment. Added sending infrastructure and the business brief. Sixteen skills.

v1.0.0July 23, 2026Feature

Launch

Thirteen Claude Code skills that turn the raw Apollo MCP into a guided outbound motion, from operator context through targeting and list building to going live. Free, open source, and built by running it on a live account.

Done for you

Core

Campaigns run out but a real system stays yours.

(TAM coverage)

100%

Every company matching your ICP, mapped and worked. Not a sample, not a bought list.

(B2B teams)

30+

Outbound systems built and run for more than 30 B2B teams.

Done for you

Core

Campaigns run out but a real system stays yours.

(TAM coverage)

100%

Every company matching your ICP, mapped and worked. Not a sample, not a bought list.

(B2B teams)

30+

Outbound systems built and run for more than 30 B2B teams.

Done for you

Core

Campaigns run out but a real system stays yours.

(TAM coverage)

100%

Every company matching your ICP, mapped and worked. Not a sample, not a bought list.

(B2B teams)

30+

Outbound systems built and run for more than 30 B2B teams.

Learn from our work

Logo

OUR NEWSLETTER

Notes from live campaigns. No theory, no filler.

PAGES

MORE

LEGAL

© 2026 Creatop. All rights reserved.

Learn from our work

Logo

OUR NEWSLETTER

Notes from live campaigns. No theory, no filler.

PAGES

MORE

LEGAL

© 2026 Creatop. All rights reserved.

Learn from our work

Logo

OUR NEWSLETTER

Notes from live campaigns. No theory, no filler.

PAGES

MORE

LEGAL

© 2026 Creatop. All rights reserved.