marketing-loops

Marketing Loops

You help set up marketing loops — repeatable marketing workflows an AI agent runs on a cadence, each with a defined trigger, a bounded set of steps, a self-check, and an explicit stopping condition. A loop turns a marketing task you'd otherwise do manually (and forget) into an always-on system: the weekly SEO opportunity scan, the ad-fatigue refresh, the churn-signal watch.

This is the operational cousin of marketing-ideas. Ideas tell you what to try once. Loops tell you what to keep doing on a schedule — and wire the other marketing skills together to do it.

How to Use This Skill

Check for product marketing context first: if .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md), read it before asking questions. Use that context and only ask for what's missing.

Then:

1. Clarify the job. What outcome should this loop protect or grow? (rankings, ad efficiency, activation, retention, revenue, referrals)
2. Pick a loop from the catalog in references/loop-catalog.md — or adapt the closest one.
3. Tune the cadence to how fast the underlying signal actually changes (see the cadence rule below).
4. Confirm the human checkpoint. Decide what the loop does autonomously vs. what it stages for human approval before publishing or spending — see references/loop-guardrails.md.
5. Schedule it (see "Scheduling a loop" below).

Building more than one loop, or a whole marketing operating system? See references/loop-orchestration.md for how loops compose and the order to adopt them (start with tracking + a weekly review; don't build them all at once).

Anatomy of a Marketing Loop

Every loop in the catalog has these nine parts. When you author or adapt one, fill all of them — a loop missing a stop condition, a self-check, or its state handling is a liability, not an asset.

Part	What it defines
Check cadence	How often the loop looks (weekly / daily / on-trigger). Match it to signal speed.
Acts when	The action condition — what must be true to actually do something, vs. just check and skip. Most runs of a good loop are "checked, nothing to do."
Purpose	The one outcome this loop exists to move.
Skills used	Which marketing skills the loop orchestrates each iteration.
Loop body	The ordered steps run each iteration.
Self-check	The verification done before acting — so the loop doesn't act on noise, seasonality, or a tracking bug.
State / idempotency	What the loop remembers between runs: last-run marker, dedupe key, cooldown window, "already handled" set. Without this, loops double-act, re-nag the same people, or re-alert the same thing. Non-negotiable for anything scheduled — see references/loop-state.md for where state lives and the idempotency patterns.
Stop / bail-out	When the loop skips, halts, escalates to a human, or disables itself — plus what it does on error. Every loop needs one, including heartbeat loops (their stop is "manual disable + error-halt," never "n/a").
Output	Where results go: a file, a PR, a staged draft, a notification, a report.