/suede-marketing-loops

name: suede-marketing-loops
description: "Suede AI recurring marketing workflow design: turns repeatable work into agent-ready loops with a check cadence, action condition, self-check, durable state and dedupe, human checkpoint, stop condition, and output, drawn from a 46-loop catalog across SEO and AI-search visibility, paid, earned, activation, retention, revenue, referral, and ops. Returns a complete loop spec plus scheduling proof or a manual cadence. Use when the user wants repeatable ad-fatigue, content-refresh, ranking-drop, AI-citation watch, churn-watch, or weekly-review loops, or wants agents to run marketing operations on a schedule. NOT FOR: one-off tactics or plans (use suede-marketing-plan), experiment design (use suede-ab-testing), or creating a live automation without explicit scheduling authority."
metadata:
  version: 1.2.0

Suede Marketing Loops

Suede AI turns repeatable marketing work into bounded loops with a defined trigger, cadence, input contract, self-check, durable state, human checkpoint, and stopping condition. A loop may watch SEO opportunities, ad fatigue, or churn signals, but it never earns permission to publish, spend, or mutate production merely because it runs on a schedule.

This is the operational counterpart to `suede-marketing-plan`: the plan identifies what may be worth trying; Suede loops define what approved work should repeat and how public Suede skills coordinate it.

How to Use This Skill

Read `.agents/product-marketing.md` first if it exists and ask only for what it does not cover; see `suede-product-marketing` for path fallbacks.

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, publish