SKILL·24497E

suede-community-marketing

JasonColapietro
更新于 8 days ago
152
8
152
在 GitHub 上查看
设计general

关于

This skill provides a playbook for building and managing product communities on platforms like Discord or Slack. It covers key growth disciplines including platform selection, seeding, moderation, and measuring community health. Use it specifically for starting, auditing, or growing a dedicated product community, not for public social media or referral programs.

快速安装

Claude Code

推荐
主要方式
npx skills add JasonColapietro/suede-creator-skills -a claude-code
插件命令备选方式
/plugin add https://github.com/JasonColapietro/suede-creator-skills
Git 克隆备选方式
git clone https://github.com/JasonColapietro/suede-creator-skills.git ~/.claude/skills/suede-community-marketing

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

Suede Community Marketing

Use this Suede community-growth playbook to create genuine member value and measurable business outcomes without manufacturing engagement.

Before You Start

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered.

Understand the situation (ask if not provided):

  1. What is the product or brand? — What problem does it solve, who uses it
  2. What community platform(s) are in play? — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
  3. What stage is the community at? — Pre-launch, 0–100 members, 100–1k, scaling, or established
  4. What is the primary community goal? — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
  5. Who is the ideal community member? — Role, motivation, what they hope to get from joining

Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.


Community Strategy Principles

Build around a shared identity, not just a product

The strongest communities are built around who members are or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.

Examples:

  • Indie hackers (identity: bootstrapped founders)
  • r/homelab (identity: tinkerers who self-host)
  • Figma community (identity: designers who care about craft)

Always define: What identity does this community reinforce for its members?

Value must flow to members first

Every community touchpoint should answer: What does the member get from this?

  • Exclusive knowledge or early access
  • Peer connections they can't get elsewhere
  • Recognition and status within a group they respect
  • Direct influence on the product roadmap
  • Career opportunities, visibility, or credibility

The Community Flywheel

Healthy communities compound over time:

Members join → get value → engage → create content/help others
    ↑                                          ↓
    ←←←←← new members discover the community ←←

Design for the flywheel from day one. Every decision should ask: Does this accelerate the loop or slow it down?


Playbooks by Goal

Launching a Community from Zero

  1. Recruit 20–50 founding members manually — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
  2. Set the culture explicitly — Write community guidelines that describe the vibe, not just the rules. What does great participation look like here?
  3. Seed conversations before launch — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
  4. Do things that don't scale at first — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof.
  5. Define your core loop — What action do you want members to take weekly? Make it easy and reward it publicly.

Growing an Existing Community

  1. Audit where members drop off — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
  2. Create a new member journey — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear "start here" path.
  3. Surface member wins publicly — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
  4. Run recurring community rituals — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
  5. Identify and invest in power users — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.

Building a Brand Ambassador / Advocate Program

  1. Identify candidates — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
  2. Make the ask personal — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
  3. Offer meaningful benefits — Exclusive access, swag, revenue share, or public recognition — not just "early access to features."
  4. Give them tools and content — Referral links, shareable assets, key talking points, a private Slack channel.
  5. Measure and iterate — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.

Community-Led Support (Deflection + Retention)

  1. Create a searchable knowledge base from top community questions
  2. Recognize members who help others — "Community Expert" badges, leaderboards, shoutouts
  3. Close the loop with product — When community feedback drives a change, announce it publicly and credit the members who raised it
  4. Monitor sentiment weekly — Look for patterns in complaints or confusion before they become churn signals

Platform Selection Guide

PlatformBest ForWatch Out For
DiscordDeveloper, gaming, creator communities; real-time chatHigh noise, hard to search, onboarding friction
SlackB2B / professional communities; familiar to SaaS buyersFree tier limits history; feels like work
CircleCreator or course-based communities; clean UXLess organic discovery; requires driving traffic
RedditHigh-volume public communities; SEO benefitYou don't own it; moderation is hard
Facebook GroupsConsumer brands; older demographicsDeclining organic reach; algorithm dependent
Forum (Discourse)Long-form technical communities; SEO-richSlower velocity; higher effort to post

Community Health Metrics

Track these signals weekly:

  • DAU/MAU ratio — Stickiness. Above 20% is healthy for most communities.
  • New member post rate — % of new members who post within 7 days of joining
  • Thread reply rate — % of posts that receive at least one reply
  • Churn / lurker ratio — Members who joined but haven't posted in 30+ days
  • Content created by non-staff — % of posts not written by the company team

Warning signs:

  • Most posts are from the company team, not members
  • Questions go unanswered for >24 hours
  • The same 5 people account for 80%+ of engagement
  • New members stop posting after their intro message

Output Formats

Depending on what the user needs, produce one of:

  • Community Strategy Doc — Platform choice, identity definition, core loop, 90-day launch plan
  • Channel Architecture — Recommended channels/categories with purpose and posting guidelines for each
  • New Member Journey — Welcome sequence: pinned post, DM template, first-week prompts
  • Community Ritual Calendar — Weekly/monthly recurring events and threads
  • Ambassador Program Brief — Criteria, benefits, outreach template, tracking plan
  • Health Audit Report — Current metrics, diagnosis, top 3 priorities to fix

Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.


Task-Specific Questions

  1. What platform are you building on (or considering)?
  2. What stage is the community at? (Pre-launch, early, growing, established)
  3. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)
  4. Who is the ideal community member and what motivates them?
  5. Do you have existing users or customers to seed from?
  6. How much time can you dedicate to community management weekly?

Boundaries

  • Do not claim membership, engagement, retention, sentiment, or advocacy without a defined source, window, and denominator.
  • Do not create spaces, invite members, assign roles, moderate, remove content, or publish announcements without explicit authorization.
  • Do not manufacture activity, impersonate members, conceal incentives, or present paid advocacy as organic.
  • Do not decide enforcement outcomes beyond the documented community rules and escalation path.

Routing

  • Need referral or ambassador incentives -> use suede-referrals.
  • Need public social content -> use suede-social.
  • Need member-language research -> use suede-customer-research.
  • Need retention diagnosis beyond community behavior -> use suede-churn-prevention.
  • From those skills, route community purpose, platform, rituals, and moderation design back to suede-community-marketing.

GitHub 仓库

JasonColapietro/suede-creator-skills
路径: skills/suede-community-marketing
0
agent-orchestrationagent-skillagent-skillsai-agentsai-codinganthropic
FAQ

常见问题

什么是 suede-community-marketing Skill?

suede-community-marketing 是一个 Claude Skill,作者为 JasonColapietro。Skill 将 Claude 按需加载的说明和资源打包,让 Claude 无需额外提示即可执行与 suede-community-marketing 相关的任务。

如何安装 suede-community-marketing?

使用本页的安装命令:将 suede-community-marketing 作为插件添加到 Claude Code,或将其仓库克隆到 skills 目录,然后重启 Claude 以加载该 Skill。

suede-community-marketing 属于哪个分类?

suede-community-marketing 属于设计分类。

suede-community-marketing 可以免费使用吗?

可以。suede-community-marketing 已收录在 AIMCP,可免费安装。

相关推荐技能

executing-plans
设计

该Skill用于当开发者提供完整实施计划时,以受控批次方式执行代码实现。它会先审阅计划并提出疑问,然后分批次执行任务(默认每批3个任务),并在批次间暂停等待审查。关键特性包括分批次执行、内置检查点和架构师审查机制,确保复杂系统实现的可控性。

查看技能
requesting-code-review
设计

该Skill可在完成任务、实现主要功能或合并代码前自动调度代码审查子代理,确保实现符合需求和计划。它支持通过指定git SHA范围进行精准的代码变更审查,帮助开发者在关键节点及时发现潜在问题。核心原则是"早审查、勤审查",适用于开发流程的各个关键阶段。

查看技能
connect-mcp-server
设计

这个Skill指导开发者如何将MCP服务器连接到Claude Code,支持HTTP、stdio和SSE三种传输协议。它涵盖了从安装配置到认证安全的完整流程,适用于集成GitHub、Notion、数据库等外部服务。当开发者需要添加集成、配置外部工具或提及MCP相关功能时,这个Skill能提供实用的操作指南。

查看技能
web-cli-teleport
设计

该Skill帮助开发者根据任务特性选择Claude Code的Web或CLI界面,并指导如何在两种环境间无缝迁移会话。它能分析任务复杂度、迭代需求等要素,推荐最优工作界面和工作流。关键特性包括会话状态管理、环境切换指导和上下文优化建议。

查看技能