New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Suede Marketing Loops

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-affiliated recurring marketing workflow design for cadence, inputs, decision rules, checkpoints, failure states, and measurable outputs.

MITAuto-check passedMarketing & SEO

Install Suede Marketing Loops

skills CLI
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-marketing-loops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-marketing-loops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-marketing-loops .claude/skills/suede-marketing-loops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
suede-marketing-loops
GitHub stars
127
Token cost
~2.6k tokens
SKILL.md length
1,405 words
Files
9 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-affiliated recurring marketing workflow design for cadence, inputs, decision rules, checkpoints, failure states, and measurable outputs.

  • Works in 5 steps: Clarify the job. What outcome should… → Pick a loop from the catalog in… → Tune the cadence to how fast the… → …
  • The user wants repeatable ad-fatigue
  • SKILL.md covers How to Use This Skill, Anatomy of a Marketing Loop, The cadence rule and When NOT to loop, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Marketing Loops is an agent skill from JasonColapietro/suede-creator-skills. Suede-affiliated recurring marketing workflow design for cadence, inputs, decision rules, checkpoints, failure states, and measurable outputs. Use when the user wants repeatable ad-fatigue, content-refresh, churn-watch, ranking-drop, or weekly-review loops. NOT FOR: one-off tactic ideation (use suede-marketing-ideas), experiment design (use suede-ab-testing), or creating a live automation without explicit scheduling authority.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).

It sits in Marketing & SEO, covering Journaling and reflection, Brainstorming and A/B testing. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.

When your agent uses it

  • The user wants repeatable ad-fatigue
  • Content-refresh
  • Weekly-review loops

Example prompts

  • “/suede-marketing-loops”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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…
  5. Schedule it (see "Scheduling a loop" below).

What it can do on your machine

Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Suede Marketing Loops loads about 2.6k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 1,405 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 1,405 words, ~2,558 tokens.

Download SKILL.mdSave it as .claude/skills/suede-marketing-loops/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
suede-marketing-loops
description
Suede-affiliated recurring marketing workflow design for cadence, inputs, decision rules, checkpoints, failure states, and measurable outputs. Use when the user wants repeatable ad-fatigue, content-refresh, churn-watch, ranking-drop, or weekly-review loops. NOT FOR: one-off tactic ideation (use suede-marketing-ideas), experiment design (use suede-ab-testing), or creating a live automation without explicit scheduling authority.
metadata.version
1.2.0

Suede Marketing Loops

Suede 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-ideas: ideas identify what may be worth trying once; 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 45 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.

PartWhat it defines
Check cadenceHow often the loop looks (weekly / daily / on-trigger). Match it to signal speed.
Acts whenThe 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."
PurposeThe one outcome this loop exists to move.
Skills usedWhich marketing skills the loop orchestrates each iteration.
Loop bodyThe ordered steps run each iteration.
Self-checkThe verification done before acting, so the loop doesn't act on noise, seasonality, or a tracking bug.
State / idempotencyWhat 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-outWhen 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").
OutputWhere 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.

SignalRealistic cadenceWhy
Rankings, backlinks, domain authorityWeeklyMove slowly; daily checks are noise
Ad creative fatigue, CPA driftEvery 2–3 daysMeta/Google feedback loops are days, not hours
Activation / onboarding funnelWeeklyNeeds enough signups to be significant
Churn signalsDaily or on-triggerEarly intervention window is short
Content / copy decayMonthlyTraffic erosion is gradual
Competitor changesWeeklyPricing/positioning shifts are infrequent but matter
Social listening / mentionsDailyEngagement 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.

Show full SKILL.md (635 more words)Show less

Scheduling a loop

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

  • Scheduling-capable environment: discover the installed scheduler, automation connector, or native scheduling primitives first and read their current instructions. Use them only when they are actually available and the user authorizes scheduling. Proof of a created schedule is the connector's own confirmation record, the created job's id or name and its next run time, quoted back.
  • Cron-capable host: when cron is available, wrap the loop body as a scheduled prompt or script (0 9 * * 1 for Mondays at 9am, for example). Proof is crontab -l output showing the new line.
  • 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. Proof is the copyable cadence instruction itself, plus an explicit statement that nothing was scheduled.

Never report a loop as scheduled without showing that proof. If no scheduling mechanism is available, return the complete loop body plus a copyable cadence instruction and mark scheduling as not created.

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, 45 marketing loops with thorough funnel coverage: SEO & Content, Paid, Earned/Social/Partnerships, 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.

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.

Halt format when a part can't be filled. Stop. Name which of the nine anatomy parts is unfilled and what is missing to fill it. Offer these options and wait for the user's choice, (1) supply the missing part now, (2) downgrade to a manual cadence and ship the body without scheduling, (3) narrow the loop's scope until the missing part is no longer needed, or (4) abandon this loop. Do not schedule, and do not present a partial loop as ready. The same halt applies to the human-checkpoint decision in step 4 above: if what runs autonomously versus what stages for approval is undecided, stop there rather than picking a default.

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.

Boundaries

  • Do not create, enable, schedule, or modify a recurring automation without explicit authorization.
  • Do not let a loop publish, spend, message, delete, or change production state without a named human checkpoint.
  • Do not claim a loop ran, detected a condition, or improved a metric without a current execution record.
  • Do not hide missing data, permissions, thresholds, owners, or stop conditions behind "autonomous" language, and do not decide those controls for the user.

Routing

  • Use suede-marketing-ideas for one-off tactics and suede-ab-testing for experimentation.
  • Use suede-analytics for measurement inputs.
  • Use suede-content-strategy for the portfolio decision behind a content loop, which pillars exist, and what should be refreshed, consolidated, or killed. This skill owns the recurring cadence; that skill owns what the cadence operates on.
  • Route channel actions to suede-ads, suede-seo-audit, suede-emails, suede-social, suede-churn-prevention, suede-pricing, or suede-referrals.

© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in skills/suede-marketing-loops of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • evals/evals.json
  • references/loop-catalog.md
  • references/loop-guardrails.md
  • references/loop-orchestration.md
  • references/loop-state.md
  • references/loop-template.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede Marketing Loops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Suede Marketing Loops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Marketing Loops this skillJasonColapietro/suede-creator-skills127—~2.6kAutomated safety check: PassMIT
Ad Test Designeraaron-he-zhu/aaron-marketing-skills2.9k2 repos~2.8kAutomated safety check: PassApache-2.0
Ab Test Analyzeririnabuht12-oss/marketing-skills4.1k—~1.4kAutomated safety check: PassNone
Define Hypothesisproduct-on-purpose/pm-skills716—~966Automated safety check: PassApache-2.0
Experiment Coachgrowthack88/growth-marketing-os116—~2.8kAutomated safety check: PassMIT
A B Test DesignOwl-Listener/designer-skills2.9k1 repos~472Automated safety check: PassMIT

Similar skills

  • Ad Test Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…

    2.9k GitHub starsUsed in 2 repos~2.8k tokens
    Marketing & SEOAuto-check passed

  • Ab Test Analyzer

    irinabuht12-oss/marketing-skills

    Statistical significance calculator for A/B test results with sample size requirements, segment breakdowns, and hypothesis generation.

    4.1k GitHub stars~1.4k tokensUpdated 17 days ago
    Marketing & SEOAuto-check passed

  • Define Hypothesis

    product-on-purpose/pm-skills

    Defines a testable hypothesis with clear success metrics and a validation approach.

    716 GitHub stars~966 tokensUpdated 3 days ago
    Marketing & SEOAuto-check passed

  • Experiment Coach

    growthack88/growth-marketing-os

    Experiment Coach — validates ideas before launch and runs growth experiments after it, from inside the chat.

    116 GitHub stars~2.8k tokensUpdated today
    Marketing & SEOAuto-check passed

  • A B Test Design

    Owl-Listener/designer-skills

    Design an A/B experiment — hypothesis, variants, primary metric, and sample size.

    2.9k GitHub starsUsed in 1 repo~472 tokens
    Marketing & SEOAuto-check passed

  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    190 GitHub stars~2.4k tokensUpdated today
    Marketing & SEOAuto-check passed

More from JasonColapietro/suede-creator-skills

All 78 skills in this repo

  • Suede Release Linter

    JasonColapietro/suede-creator-skills

    Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.

    127 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes

  • Creator Rights Passport

    JasonColapietro/suede-creator-skills

    Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.

    127 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check: notes

  • Suede Clip to Guide

    JasonColapietro/suede-creator-skills

    Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.

    127 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

  • Suede MCP Release QA

    JasonColapietro/suede-creator-skills

    Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.

    127 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Android App Factory

    JasonColapietro/suede-creator-skills

    Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.

    127 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

  • Suede Ad Creative

    JasonColapietro/suede-creator-skills

    Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.

    127 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Suede Marketing Loops

What does Suede Marketing Loops do?

Suede-affiliated recurring marketing workflow design for cadence, inputs, decision rules, checkpoints, failure states, and measurable outputs. Suede Marketing Loops is an agent skill from JasonColapietro/suede-creator-skills. Suede-affiliated recurring marketing workflow design for cadence, inputs, decision rules, checkpoints, failure states, and measurable outputs.

When should I use Suede Marketing Loops?

Suede Marketing Loops fits situations like: the user wants repeatable ad-fatigue; content-refresh; weekly-review loops.

How do I install Suede Marketing Loops in Claude Code?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-marketing-loops -a claude-code`. Or copy the skill folder (skills/suede-marketing-loops in JasonColapietro/suede-creator-skills) into .claude/skills/suede-marketing-loops in your project. Claude Code loads it when a task matches its description.

How do I install Suede Marketing Loops in Codex?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-marketing-loops -a codex`. Or copy the skill folder (skills/suede-marketing-loops in JasonColapietro/suede-creator-skills) into .agents/skills/suede-marketing-loops in your project. Codex loads it when a task matches its description.

Can I use Suede Marketing Loops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill suede-marketing-loops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-marketing-loops, .gemini/skills/suede-marketing-loops, .github/skills/suede-marketing-loops and .opencode/skills/suede-marketing-loops in your project.

What does Suede Marketing Loops need to run?

SKILL.md names no scripts, command-line tools or credentials: Suede Marketing Loops is instructions for the agent only.

Does Suede Marketing Loops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Suede Marketing Loops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Suede Marketing Loops use?

Suede Marketing Loops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Suede Marketing Loops use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Suede Marketing Loops?

Skills that share tags, products or a category with Suede Marketing Loops: Ad Test Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Ab Test Analyzer (irinabuht12-oss/marketing-skills, 4.1k stars), Define Hypothesis (product-on-purpose/pm-skills, 716 stars) and Experiment Coach (growthack88/growth-marketing-os, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Suede Marketing Loops?

JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.

Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.