Catalog
coreyhaines31/marketing-loops

coreyhaines31

marketing-loops

When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'weekly ads check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'run my SEO,' 'SEO operator,' 'daily SEO agent,' 'run my outbound,' 'AI SDR,' 'reply triage,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

NewUpdated Nov 7, 2026

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.

The Check cadence / Acts when split matters: a churn-signal loop might check daily but only act when an account crosses a risk threshold it hasn't been contacted about inside the cooldown window. Conflating the two produces loops that either miss the window or spam.

The cadence rule

Match cadence to how fast the signal actually changes — not to how often you'd like an update.

Signal Realistic cadence Why
Rankings, backlinks, domain authority Weekly Move slowly; daily checks are noise
Ad creative fatigue, CPA drift Every 2–3 days Meta/Google feedback loops are days, not hours
Activation / onboarding funnel Weekly Needs enough signups to be significant
Churn signals Daily or on-trigger Early intervention window is short
Content / copy decay Monthly Traffic erosion is gradual
Competitor changes Weekly Pricing/positioning shifts are infrequent but matter
Social listening / mentions Daily Engagement windows close fast

Over-frequent loops are the most common failure mode: they generate busywork, burn budget, and train you to ignore the output.

When NOT to loop

Not everything should be automated on a cadence. Skip a loop — or add a mandatory human checkpoint — when:

  • Strategy or creative direction is the real work. Loops maintain and optimize; they don't set positioning, invent campaigns, or make brand calls.
  • The action publishes or spends without review. Auto-drafting an ad, email, or post is fine. Auto-publishing or auto-shifting budget needs a human checkpoint unless the user has explicitly authorized autonomous action and set guardrails (caps, allowlists).
  • The signal is too sparse to be significant. A weekly conversion-rate loop on 40 visitors/week is measuring noise.
  • It's a vanity loop. If nobody acts on the output, delete the loop. A loop that emails a dashboard nobody reads is worse than nothing.

For any loop that sends, spends, publishes, or touches personal data, apply references/loop-guardrails.md — the two-tier action model (autonomous-safe vs. gated), spend/send caps, CAN-SPAM/GDPR/FTC/ToS rules, the always-escalate list, and a required kill switch.

Scheduling a loop

These loops are agent-agnostic — the body works in any agent. The scheduling depends on your environment:

  • Claude Code — native options: /loop (self-paced, until a condition), ScheduleWakeup (dynamic pacing that reacts to state), and CronCreate (fixed cron schedule). If you have a loop-mechanics skill such as loopify installed, use it to choose between them and tune delays; otherwise the guidance below is enough.
  • Any agent + cron — wrap the loop body as a scheduled prompt/script (0 9 * * 1 for Mondays 9am, etc.).
  • Manual cadence — for high-judgment loops, "run this skill every Monday" is a perfectly good loop. The value is the repeatable body, not the automation.

Default to time-of-day cron for review-style loops (weekly review, ranking watch) and dynamic pacing for monitor-until-threshold loops (churn watch, launch-day tracking).

The Catalog

references/loop-catalog.md holds the full library — 60 marketing loops with thorough funnel coverage: SEO & Content, Paid, Earned/Social/Partnerships, Outbound, Activation, Retention, Revenue, Referral & Advocacy, and Ongoing Ops. Each is a complete, adaptable spec. Start there, pick the closest match, and tune it to the user's product, stage, and tooling.

Running a whole channel: the SEO operator

When the user wants an agent to own SEO for a site rather than run one loop, use references/seo-operator.md. It bundles the SEO loops (site health, claim drift, striking-distance push, AI-answer check, keyword gap, content decay, competitor watch, and more) into one schedule with shared memory in .agents/seo/, a first-run checklist, operating rules, a writing gate, and a one-screen weekly report.

Running outbound: the outbound operator

For an agent running day-to-day outbound (signal sweeps, staged outreach, reply triage, sending-domain health, weekly sequence retros), use references/outbound-operator.md. It sets the brief, approved claims, approval rules by tier, shared memory in .agents/outbound/, and a weekly report.

Authoring a new loop

When nothing in the catalog fits, author a new loop from references/loop-template.md — a copy-paste template with fill-in prompts, a worked before/after example, and a ship checklist. Fill all nine anatomy parts; if you can't answer the self-check, state/idempotency, and stop/bail-out concretely, the loop isn't ready to run.

Anti-patterns

  • Looping without a stop condition → runaway spend or infinite churn.
  • Same cadence for every loop → most run too often and get ignored.
  • No self-check → the loop acts on noise, seasonality, or a tracking bug.
  • No human checkpoint on spend/publish actions.
  • Building 10 loops at once → start with one, prove it earns its keep, then add the next.

Banned vocabulary

Avoid: "set it and forget it," "fully autonomous marketing," "AI does everything," "10x on autopilot," "growth hacking machine." Loops are disciplined systems with checkpoints, not magic. Describe them honestly.

  • marketing-ideas — one-off tactics and inspiration (what to try). Loops operationalize the ones worth repeating.
  • ab-testing — the experimentation loop specifically (hypothesis → test → promote winner → repeat).
  • analytics — most loops read from analytics to decide whether to act.
  • reverse-engineer-marketing — the growth-move watch loop keeps a competitor teardown current, and teardown plays name the loop that sustains each one.
  • Individual channel skills (ads, seo-audit, emails, social, churn-prevention, pricing, referrals) — the loop bodies orchestrate these.
Files9
9 files · 113.2 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

88

Quality

89

Clarity

86

Completeness

84

Summary

The marketing-loops skill teaches agents to build and operationalize repeatable, scheduled marketing workflows (loops) with defined triggers, bounded actions, self-checks, and explicit stopping conditions. It is the operational counterpart to one-off marketing tactics — where loops orchestrate other marketing skills into always-on systems (SEO monitoring, ad fatigue refresh, churn detection, outbound campaigns) that run on a cadence. The skill emphasizes disciplined guardrails: human checkpoints for spend/publish actions, state tracking to prevent double-acting, and a catalog of 60+ proven loop templates covering the full funnel.

Detected Capabilities

file readstate management and persistencescheduled workflow orchestrationdata analysis and reportingcontent drafting and stagingreference material lookupstructured decision logging

Trigger Keywords

Phrases that agents use to match this skill to user intent.

weekly marketing reviewrecurring marketing automationscheduled marketing workflowmarketing loop setupchurn watch loopranking drop alertad fatigue refreshrevenue recovery loopseo operatoroutbound automation

Risk Signals

INFO

Referenced external GitHub URL in code examples (loop-catalog.md, seo-operator.md)

references/seo-operator.md, references/loop-catalog.md
INFO

Recommendation to stage work for human approval rather than autonomous execution for spend/publish actions

SKILL.md, references/loop-guardrails.md
INFO

State and PII handling guidance explicitly avoids storing raw PII, uses hashes/IDs instead

references/loop-state.md
INFO

Compliance guardrails documented for CAN-SPAM, GDPR, CCPA, FTC, platform ToS

references/loop-guardrails.md

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

  • Set up a weekly SEO monitoring loop that watches rankings and flags optimization opportunities
  • Build a churn-detection loop that identifies at-risk customers daily and stages intervention workflows
  • Automate ad-creative refresh when frequency rises and CTR declines (ad fatigue loop)
  • Create a daily reply-triage loop that categorizes and routes customer messages before human team review
  • Establish a weekly pricing experiment loop that A/B tests different plan structures and stages results for approval
  • Set up a recurring content-repurposing workflow that turns long-form assets into channel-native social drafts
  • Build a failing-payment recovery loop with retries and escalation rules to stop churn
  • Create a keyword-gap detection loop that surfaces striking-distance ranking opportunities weekly
  • Establish a daily signal-sweep loop for outbound prospecting that sources leads and stages outreach sequences
  • Build a weekly brand-mention monitor that detects news coverage, competitor moves, and AI-answer drift

Quality Notes

  • Excellent anatomy framework: the nine-part loop template (cadence, acts-when, purpose, skills, body, self-check, state, stop, output) is clear, repeatable, and comprehensive. It forces users to think through idempotency and error handling before deployment.
  • Strong guardrails documentation: loop-guardrails.md covers two-tier actions (autonomous vs. gated), spend caps, suppression, compliance, PII handling, and an always-escalate list. The checklist ensures safety before scheduling.
  • Comprehensive catalog (60+ loops): covering SEO, Paid, Email, Social, Outbound, Activation, Retention, Revenue, Referrals, and Ops. Each loop is a complete, adaptable spec with worked examples.
  • Excellent staged rollout guidance (loop-orchestration.md): shows the order to adopt loops (tracking/weekly review → retention → activation → growth → monetization → advocacy). Prevents over-building and ensures foundation layers exist first.
  • Practical operator patterns: seo-operator.md and outbound-operator.md show how to bundle loops with shared state, approval rules, and weekly reporting — moving beyond isolated scripts to a real operating system.
  • State and idempotency treatment is exemplary: loop-state.md defines watermarks, dedup sets, cooldowns, and in-flight guards with clear JSON examples. The run-logging pattern (timestamp, checked, acted, notes) enables auditing and vanity-loop detection.
  • Clear distinction between signal speed and cadence: the cadence rule table (rankings → weekly, ad fatigue → 2–3 days, etc.) prevents the most common failure mode (over-frequent loops that generate busywork).
  • Explicit anti-patterns section: lists common failures (no stop condition, same cadence everywhere, no self-check, no human checkpoint, building all loops at once) with remedies.
  • Banned vocabulary section: deliberately avoids overselling ('set it and forget it', 'fully autonomous') and frames loops honestly as disciplined systems, not magic.
  • Self-check emphasis: every loop's self-check guards against noise, seasonality, and tracking bugs — preventing false positives from cascading into waste.
  • Well-organized reference structure: SKILL.md is the hub; loop-catalog.md, loop-template.md, loop-guardrails.md, loop-state.md, loop-orchestration.md, seo-operator.md, outbound-operator.md are focused deep dives.
  • Evaluation suite (evals.json) is thorough: 9 test cases covering SEO loops, full automation setup, newsjacking guardrails, scheduling mechanics, anti-patterns, dunning, A/B testing loops, SEO operator, and outbound operator. Assertions are specific and actionable.
Model: claude-haiku-4-5-20251001Analyzed: Nov 7, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v3.4

    Content updated

    ✦ AILoop catalog expanded to 60 loops (from 59); supporting file updated.

    2026-11-07

    LATEST
  2. v3.3

    Content updated

    ✦ AILoop catalog expanded to 59 loops and adds reverse-engineer-marketing skill reference.

    2026-10-31

    View This Version
  3. v3.2

    Content updated

    ✦ AIReference documentation updated in loop-catalog.md.

    2026-10-28

    View This Version
  4. v3.1

    Content updated

    ✦ AIUpdates reference content in loop-catalog.md.

    2026-10-20

    View This Version
  5. v3.0

    Contract changed: description

    ✦ AIExpands activation triggers to include 'weekly ads check' and increases marketing loops library from 52 to 58 specs.

    triggering2026-10-17

    View This Version
  6. v2.0

    Contract changed: description

    ✦ AIExpands skill scope to full-channel operators: adds SEO operator and outbound operator bundling multiple loops with shared state and weekly reporting. Loop catalog grows from 43 to 52 loops.

    triggering2026-10-08

    View This Version
  7. v1.2

    Content updated

    ✦ AILoop catalog reference updated with minor content changes.

    2026-10-03

    View This Version
  8. v1.1

    Content updated

    ✦ AIReferences file updated with expanded loop catalog content.

    2026-09-09

    View This Version
  9. v1.0

    2026-07-03

    View This VersionInitial version

Use coreyhaines31/marketing-loops in your dev environment

Command Palette

Search for a command to run...