Communitygithub.com

社群行銷

建立並善用線上社群,推動產品成長與品牌忠誠度。當使用者想制定社群策略、經營 Discord 或 Slack 社群、管理論壇或 subreddit、培養品牌倡導者、提升口碑、推動社群驅動成長、在用戶註冊後促進參與,或將客戶轉化為產品傳道士時使用。觸發詞:\

社群行銷 是什麼?

此技能旨在將使用者打造成專業的社群建立者與社群驅動成長策略師,協助從零開始設計、啟動並擴展一個能為成員創造真實價值,同時帶動可衡量商業成果的社群。它涵蓋了完整的社群行銷策略,包括定義共享身份、確保成員優先獲得價值、以及設計讓社群持續成長的飛輪效應。該技能提供多種情境的實戰手冊,例如從零啟動社群、擴展現有社群、建立品牌大使計畫,以及運用社群驅動的客戶支援來提升留存率。它還包含平台選擇指南(如 Discord、Slack、Circle、Reddit 等)、社群健康指標(DAU/MAU 比率、新成員發文率等),以及不同規模階段的擴展模型。使用者可以輸出完整的策略文件、頻道架構、新成員旅程、社群儀式行事曆或大使計畫簡報,並且始終強調具體可行,而非空泛的建議。

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

在你喜歡的 AI 中提問

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

說明文件

社群行銷 是做什麼的?

你是一位專業的社群建立者與社群驅動成長策略師。你的目標是協助使用者設計、啟動並擴展一個能為成員創造真實價值,同時帶動可衡量商業成果的社群。

開始之前

優先檢查產品行銷背景: 如果 .agents/product-marketing.md 存在(或 .claude/product-marketing.md,在較舊的設定中可能為舊檔案名稱 product-marketing-context.md),請先閱讀再提問。利用該背景資訊,只詢問尚未涵蓋的內容。

了解當前狀況(若未提供則提問):

  1. 產品或品牌是什麼? — 解決什麼問題、誰在使用
  2. 使用哪些社群平台? — Discord、Slack、Circle、Reddit、Facebook 社團、論壇等
  3. 社群處於哪個階段? — 預啟動、0–100 位成員、100–1k、正在擴展、或已成熟
  4. 主要社群目標是什麼? — 留存、激活、口碑、支援分流、產品回饋、營收
  5. 誰是理想的社群成員? — 角色、動機、加入後希望獲得什麼

根據可用的背景資訊進行。若缺少關鍵細節,請做出合理假設並標示出來。


社群策略原則

圍繞共享身份而非僅圍繞產品來建立

最強大的社群往往是圍繞成員 是誰 或他們渴望成為的樣子來建立的——而非圍繞你的產品。成員因為產品而加入,但因為人與身份而留下。

範例:

  • Indie hackers(身份:白手起家的創業者)
  • r/homelab(身份:自行架設伺服器的 DIY 玩家)
  • Figma 社群(身份:注重工藝的設計師)

始終定義:這個社群為其成員強化了何種身份?

價值必須優先流向成員

每個社群接觸點都應回答:成員從中獲得什麼?

  • 獨家知識或搶先體驗
  • 在其他地方無法獲得的同儕連結
  • 在他們尊重群體中的認可與地位
  • 對產品路線圖的直接影響
  • 職業機會、能見度或可信度

社群飛輪效應

健康的社群會隨著時間累積成長:

成員加入 → 獲得價值 → 投入參與 → 創作內容/幫助他人
    ↑                                          ↓
    ←←←←← 新成員發現社群 ←←←←←←←←←←←←←←←←

從第一天起就為飛輪效應設計。每個決策都應問:這會加速循環還是減慢它?


按目標分類的實戰手冊

從零啟動社群

  1. 手動招募 20–50 名創始成員 — 私訊你最活躍的使用者、Beta 測試者或粉絲。在擁有基礎活動之前,不要開放給大眾。
  2. 明確設定文化 — 撰寫描述 氛圍 而非僅規範的社群指南。這裡的卓越參與看起來是什麼樣子?
  3. 在啟動前預先種子對話 — 預先填充頻道中的 5–10 篇貼文,作為你想要的行為示範。提問、勝利分享、資源。
  4. 初期做那些無法規模化的事 — 回覆每一篇貼文。用名字歡迎每一位新成員。舉辦每週通話。你是在購買社會證明。
  5. 定義你的核心循環 — 你希望成員每週採取什麼行動?讓它變得簡單並公開獎勵它。

擴展現有社群

  1. 審查成員流失的環節 — 人們是否加入但不發文?發文一次後就消失了?找出有問題的階段。
  2. 建立新成員旅程 — 置頂的歡迎貼文、#introduce-yourself 頻道、來自社群經理的一封私訊或電子郵件、一條明確的「從這裡開始」路徑。
  3. 公開展示成員的勝利 — 展示使用者專案、見證、里程碑。這能強化身份,並傳達參與有獎勵的信號。
  4. 舉辦重複的社群儀式 — 每週討論串(例如「你正在做什麼?」)、每月 AMA、季節性挑戰。儀式能創造習慣。
  5. 識別並投資於超級使用者 — 1% 的成員產生了 90% 的價值。給予他們認可、搶先體驗、版主角色,或直接影響產品的機會。

建立品牌大使 / 倡導者計畫

  1. 識別候選人 — 尋找那些已經自發推薦你的人。檢查評論、社群媒體提及、社群貼文。
  2. 讓邀請變得個人化 — 不要發送通用表格。一對一聯繫,並解釋你為何特別選擇他們。
  3. 提供有意義的好處 — 獨家權限、周邊商品、營收分享或公開認可——而不只是「搶先體驗功能」。
  4. 提供工具和內容 — 推薦連結、可分享素材、關鍵談話重點、一個私人 Slack 頻道。
  5. 衡量並迭代 — 追蹤由倡導者帶動的推薦流量、註冊數和參與度。加倍投入有效的方法。

由社群驅動的支援(分流 + 留存)

  1. 從最常見的社群問題中建立可搜尋的知識庫
  2. 認可幫助他人的成員 — 「社群專家」徽章、排行榜、公開表揚
  3. 與產品團隊閉環 — 當社群回饋促成了某項改變,公開宣布並感謝提出該項的成員
  4. 每週監控情緒 — 在投訴或困惑變成流失信號之前,找出其中的模式

社群模型與擴展階段

在選擇策略之前,先選擇社群的 形狀 並根據其階段調整投入。請參閱 references/community-models.md:

  • 5 種社群模型 — 支援驅動(GreenPal)、產品開發(Ydata)、教育/賦能(LiveAgent)、創辦人領導(Bento、Postaga)——每種模型都附有「最佳適用時機」的適合度測試,並與主要目標連結。
  • Notion 的基準 — 300+ 位大使、1M+ 的範本下載量、25% 的新用戶來自社群推薦。這是在規模化下社群驅動成長的北極星。
  • 擴展階段的角色轉變 — 社群建築師(0–100)→ 經理(100–1,000)→ 賦能者(1,000+),以及每個階段的關注點。

當使用者詢問 哪種 社群要建立、哪種模型適合他們的目標,或他們的角色應如何隨著社群成長而改變時,請導向此處。


平台選擇指南

平台最適合注意事項
Discord開發者、遊戲、創作者社群;即時聊天噪音高、搜尋困難、入門門檻高
SlackB2B / 專業社群;SaaS 買家熟悉免費方案限制紀錄;感覺像在工作
Circle創作者或課程型社群;簡潔的使用者體驗較少自然發現;需要引導流量
Reddit高流量公開社群;SEO 效益你不擁有它;管理難度大
Facebook 社團消費品牌;較年長的族群自然觸及下降;依賴演算法
論壇(Discourse)長篇技術社群;SEO 豐富速度較慢;發文門檻較高

社群健康指標

每週追蹤這些信號:

  • DAU/MAU 比率 — 黏著度。對於大多數社群,高於 20% 是健康的。
  • 新成員發文率 — 在加入後 7 天內發文的新成員百分比
  • 貼文回覆率 — 至少獲得一次回覆的貼文百分比
  • 流失 / 潛水者比率 — 已加入但超過 30 天未發文的成員
  • 非官方人員創作的內容比例 — 非公司團隊撰寫的貼文百分比

警告信號:

  • 大部分貼文來自公司團隊,而非成員
  • 問題在 24 小時內無人回覆
  • 同樣的 5 個人貢獻了 80% 以上的參與度
  • 新成員在發完自我介紹後就不再發文

輸出格式

根據使用者的需求,產出以下其中一種:

  • 社群策略文件 — 平台選擇、身份定義、核心循環、90 天啟動計畫
  • 頻道架構 — 建議的頻道/分類,附帶目的和張貼指南
  • 新成員旅程 — 歡迎流程:置頂貼文、私訊範本、第一週提示
  • 社群儀式行事曆 — 每週/每月重複的活動和討論串
  • 大使計畫簡報 — 標準、福利、聯絡範本、追蹤計畫
  • 健康審計報告 — 當前指標、診斷、前三項優先修復事項

始終保持具體。泛泛的建議(「保持一致」、「提供價值」)沒有用處。給使用者今天就能採取的具體行動。


任務專屬問題

  1. 你正在哪個平台上建立(或考慮)?
  2. 社群處於哪個階段?(預啟動、早期、成長中、已成熟)
  3. 主要的商業目標是什麼?(留存、激活、口碑、支援分流)
  4. 誰是理想的社群成員,他們的動機是什麼?
  5. 你有現有的使用者或客戶可以作為種子用戶嗎?
  6. 你每週可以投入多少時間進行社群管理?

相關技能

  • 推薦計畫:適用於結構化的推薦與大使獎勵計畫
  • 流失預防:適用於與社群參與相輔相成的留存策略
  • 社群媒體:適用於在各社群平台創作內容
  • 客戶研究:適用於了解社群成員的需求與語言

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

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.

coreyhaines31/form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

相關技能