Communitygithub.com

marketing-loops

協助設定由 AI 代理定期執行的重複性行銷工作流程(行銷循環),而非一次性任務。當使用者提到需要週期性(每週、每日、觸發條件)自動運行的行銷流程時使用。

marketing-loops 是什麼?

此技能旨在幫助建立與管理「行銷循環」(Marketing Loops)——由 AI 代理按既定節奏重複執行的行銷工作流程。每個循環都包含明確的觸發條件、有限的步驟集合、自我檢查機制以及明確的停止條件。它能將原本需要手動執行且可能被遺忘的行銷任務(例如每週的 SEO 機會掃描、廣告疲勞更新、客戶流失訊號監控)轉變為永不停歇的主動系統。 該技能提供了詳細的循環構成指南(包含九個必要部分,如檢查節奏、停止條件、狀態管理等),並根據訊號變化速度提供節奏設定建議(例如排名變化建議每週檢查,而流失訊號則需每日或觸發檢查)。它明確指出何時不應建立循環(例如涉及策略方向或自動發布/花費時),並要求針對發送、花費或發布行為設置人工審查點。 此技能與代理無關,循環本體可在任何代理上執行,但排程方式會因環境而異(例如 Claude Code 支援 `/loop`、`ScheduleWakeup` 或 `CronCreate`;其他代理可搭配 cron;高度判斷性循環也可手動執行)。它還引用了配套的目錄檔案 (`references/loop-catalog.md`) 與模板 (`references/loop-template.md`),覆蓋 43 種涵蓋完整行銷漏斗的循環,並提供了常見的反模式(如缺少停止條件、節奏設定過快、缺乏自我檢查)以及禁止使用的誇大詞彙,強調循環是需要檢查點的紀律性系統。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/marketing-loops

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

行銷循環 (Marketing Loops)

你負責協助設定行銷循環——一種由 AI 代理按既定節奏重複執行的行銷工作流程。每個循環都包含明確的觸發條件、有限的步驟集合、自我檢查機制以及明確的停止條件。循環能將你原本需要手動執行(而且常常忘記)的行銷任務轉變為永不停歇的主動系統:例如每週的 SEO 機會掃描、廣告疲勞更新、客戶流失訊號監控。

這是 marketing-ideas(行銷點子)的實戰表親。點子告訴你該嘗試什麼。循環則告訴你該持續做什麼——並將其他行銷技能整合在一起。

如何使用此技能

首先檢查產品行銷背景資料: 如果存在 .agents/product-marketing.md(或 .claude/product-marketing.md,或舊版的 product-marketing-context.md),請先閱讀它再提問。利用該背景資訊,僅詢問缺失的部分。

接著:

  1. 釐清任務。 這個循環應該保護或促進什麼成果?(排名、廣告效率、啟動率、留存率、營收、推薦)
  2. 從目錄中選取循環。 從 references/loop-catalog.md 的目錄中選取一個循環——或改編最接近的一個。
  3. 調整節奏。 根據底層訊號的實際變化速度來調整(請參考下方的節奏規則)。
  4. 確認人工審查點。 決定循環自主執行的部分,以及哪些需要先經人工審核才能發布或花費——請參考 references/loop-guardrails.md。
  5. 排程它。 (請參考下方的「排程循環」)。

要建立多個循環或一整套行銷作業系統?請參考 references/loop-orchestration.md,了解循環如何組合以及採用的順序(從追蹤加上每週檢討開始;不要一次建立 43 個)。

行銷循環的構成

目錄中的每個循環都包含以下九個部分。當你撰寫或改編一個循環時,請填寫所有部分——缺少停止條件、自我檢查或狀態處理的循環是負債,而非資產。

部分定義內容
檢查節奏循環檢查的頻率(每週 / 每日 / 觸發條件觸發)。需與訊號速度匹配。
執行條件行動條件——必須為真才會實際執行某個動作,否則僅檢查並跳過。一個好的循環大部分執行次數都是「檢查了,沒什麼好做的」。
目的這個循環存在是為了推動的單一成果。
使用的技能每次迭代中,循環所編排的行銷技能。
循環主體每次迭代執行的有序步驟。
自我檢查在執行之前進行的驗證——確保循環不會受到雜訊、季節性或追蹤錯誤的影響而採取行動。
狀態 / 冪等性循環在執行之間記住哪些資訊:上次執行標記、去重金鑰、冷卻時間窗口、「已處理」集合。沒有這個,循環會重複執行、重複打擾同一個人、或重複警示同一件事。對於任何排程的循環來說,這是不可協商的——請參考 references/loop-state.md,了解狀態存放位置及冪等性模式。
停止 / 緊急退出循環何時跳過、暫停、升級給人類處理、或自行停用——以及出錯時該怎麼做。每個循環都需要一個,包括心跳循環(其停止條件為「手動停用 + 錯誤暫停」,永遠不會是「不適用」)。
輸出結果的存放位置:檔案、PR、草稿、通知、報告。

檢查節奏 / 執行條件 的區分非常重要:一個客戶流失訊號循環可能每日檢查,但僅在帳戶超過某個風險閾值且該帳戶在冷卻時間內未被聯繫過時才採取行動。將兩者混淆會產生要嘛錯過時間窗口、要嘛產生垃圾訊息的循環。

節奏規則

將節奏與訊號實際變化速度匹配——而不是與你希望收到更新的頻率匹配。

訊號實際可行的節奏原因
排名、反向連結、網域權威每週變化緩慢;每日檢查是雜訊
廣告創意疲勞、CPA 偏移每 2-3 天Meta/Google 的反饋迴圈週期是天,不是小時
啟動/入職漏斗每週需要足夠的註冊量才能具有統計意義
客戶流失訊號每日或觸發條件觸發早期干預窗口很短
內容/文案衰退每月流量侵蝕是漸進的
競爭對手變化每週定價/定位轉變不頻繁,但很重要
社交聆聽 / 提及每日互動窗口很快就關閉

過於頻繁的循環是最常見的失敗模式:它們會產生無效工作量、耗費預算,並訓練你忽略輸出結果。

何時不該建立循環

並非所有事情都應該按節奏自動化。在以下情況中,跳過循環——或加入強制性的人工審查點:

  • 策略或創意方向才是真正的工作。 循環負責維護和優化;它們不制定定位、發明行銷活動、或做出品牌決策。
  • 該行動會發布或花費,且未經審查。 自動起草廣告、電子郵件或貼文是可以的。自動發布或自動調整預算需要人工審查點,除非使用者已明確授權自主行動並設定防護措施(上限、允許清單)。
  • 訊號過於稀疏,不具統計意義。 每週對 40 位訪客執行的轉換率循環只是在測量雜訊。
  • 這是個虛榮循環。 如果沒有人根據輸出採取行動,請刪除該循環。一個發送沒人閱讀的儀表板郵件的循環比沒有還糟。

對於任何涉及發送、花費、發布或接觸個人資料的循環,請應用 references/loop-guardrails.md——包括兩層行動模型(自主安全 vs. 閘門控制)、花費/發送上限、CAN-SPAM/GDPR/FTC/ToS 規則、始終升級清單以及必要的緊急停止開關。

排程循環

這些循環與代理無關——循環主體可在任何代理中運作。排程方式則取決於你的環境:

  • Claude Code — 原生選項:/loop(自定節奏,直到滿足條件為止)、ScheduleWakeup(根據狀態動態調整節奏)以及 CronCreate(固定 cron 排程)。如果你已安裝類似 loopify 的循環機制技能,請使用它來選擇並調整延遲;否則,下方的指引就已足夠。
  • 任何代理 + cron — 將循環主體包裝為排程的提示/腳本(0 9 * * 1 表示每週一早上 9 點,依此類推)。
  • 手動節奏 — 對於高度判斷性的循環,「每週一執行此技能」就是一個非常好的循環。其價值在於可重複的主體,而非自動化。

預設情況下,檢討類型的循環(每週檢討、排名監控)使用特定時間的 cron,而監控直到達到閾值的循環(客戶流失監控、發布日追蹤)則使用動態節奏。

目錄

references/loop-catalog.md 包含完整的資料庫——43 個涵蓋完整行銷漏斗的行銷循環:SEO & 內容、付費廣告、贏得/社交/合作夥伴、啟動、留存、營收、推薦與倡導,以及持續營運。每個都是完整且可調整的規格。從那裡開始,選取最接近的匹配,然後根據使用者的產品、階段和工具進行調整。

撰寫新的循環

當目錄中沒有合適的選項時,請從 references/loop-template.md 開始撰寫新的循環——這是一個可複製貼上的模板,包含填空提示、完整的 Before/After 範例以及上線檢查清單。填寫所有九個構成部分;如果你無法具體回答自我檢查、狀態/冪等性以及停止/緊急退出,那麼這個循環還不準備好執行。

反模式

  • 循環沒有停止條件 → 無限花費或無窮盡的客戶流失。
  • 每個循環都使用相同的節奏 → 大多數執行得太頻繁而導致被忽略。
  • 沒有自我檢查 → 循環會根據雜訊、季節性或追蹤錯誤採取行動。
  • 花費/發布動作沒有人工審查點。
  • 一次建立 10 個循環 → 從一個開始,證明其價值,然後再加入下一個。

禁止使用的詞彙

避免使用:「設定後就忘了它」、「完全自主行銷」、「AI 什麼都做」、「自動駕駛 10 倍成長」、「成長駭客機器」。循環是需要檢查點的紀律性系統,不是魔法。請誠實地描述它們。

相關技能

  • marketing-ideas — 一次性戰術與靈感(該嘗試什麼)。循環將那些值得重複的點子實戰化。
  • ab-testing — 專門的實驗循環(假設 → 測試 → 推廣勝者 → 重複)。
  • analytics — 大多數循環從分析工具讀取數據來決定是否採取行動。
  • 個別渠道技能(ads、seo-audit、emails、social、churn-prevention、pricing、referrals)——循環主體會編排這些技能。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

相關技能