Customer Research
Nexus-JPF/note-companion
When the user wants to conduct, analyze, or synthesize customer research.
Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy.
Install Suede Community Marketing
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-community-marketing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-community-marketing .claude/skills/suede-community-marketing && rm -rf skills-srcUse ~/.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/
Install the "suede-community-marketing" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-community-marketing into .claude/skills/suede-community-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-community-marketing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-community-marketingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-community-marketing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/suede-community-marketing .agents/skills/suede-community-marketing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "suede-community-marketing" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-community-marketing into .agents/skills/suede-community-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-community-marketing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-community-marketing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/suede-community-marketing .cursor/skills/suede-community-marketing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "suede-community-marketing" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-community-marketing into .cursor/skills/suede-community-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-community-marketing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JasonColapietro/suede-creator-skills.git --path skills/suede-community-marketing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-community-marketing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/suede-community-marketing .gemini/skills/suede-community-marketing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "suede-community-marketing" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-community-marketing into .gemini/skills/suede-community-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-community-marketing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JasonColapietro/suede-creator-skills suede-community-marketingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/suede-community-marketing .github/skills/suede-community-marketing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "suede-community-marketing" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-community-marketing into .github/skills/suede-community-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-community-marketing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-community-marketing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/suede-community-marketing .opencode/skills/suede-community-marketing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "suede-community-marketing" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-community-marketing into .opencode/skills/suede-community-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-community-marketing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
suede-community-marketing- GitHub stars
- 127
- Token cost
- ~3k tokens
- SKILL.md length
- 1,362 words
- Files
- 4
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy.
- Works in 5 steps: What is the product or brand?: What… → What community platform(s) are in play?:… → What stage is the community at?:… → …
- Growing a Discord
- SKILL.md covers Before You Start, Community Strategy Principles, Playbooks by Goal and Platform Selection Guide, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Suede Community Marketing is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy. Use when starting, auditing, or growing a Discord, Slack, forum, subreddit, or comparable product community. NOT FOR: public social-channel content (use suede-social), referral-program mechanics (use suede-referrals), or customer-interview research (use suede-customer-research).
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).
It sits in Marketing & SEO, covering Market research, Referral and retention marketing and User research. It works with Discord, Reddit and Slack. 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
- Growing a Discord
- Comparable product community
Example prompts
- “/suede-community-marketing”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- What is the product or brand?: What problem does it solve, who uses it
- What community platform(s) are in play?: Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
- What stage is the community at?: Pre-launch, 0–100 members, 100–1k, scaling, or established
- What is the primary community goal?: Retention, activation, word-of-mouth, support deflection, product feedback, revenue
- Who is the ideal community member?: Role, motivation, what they hope to get from joining
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 (its code samples are markdown).
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 Community Marketing loads about 3k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,362 words of instructions outside code blocks.
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,362 words, ~2,961 tokens.
Download SKILL.mdSave it as
.claude/skills/suede-community-marketing/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- suede-community-marketing
- description
- Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy. Use when starting, auditing, or growing a Discord, Slack, forum, subreddit, or comparable product community. NOT FOR: public social-channel content (use suede-social), referral-program mechanics (use suede-referrals), or customer-interview research (use suede-customer-research).
- metadata.version
- 2.0.0
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):
- What is the product or brand?: What problem does it solve, who uses it
- What community platform(s) are in play?: Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
- What stage is the community at?: Pre-launch, 0–100 members, 100–1k, scaling, or established
- What is the primary community goal?: Retention, activation, word-of-mouth, support deflection, product feedback, revenue
- 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.
Example: r/homelab: the identity is tinkerers who self-host, and every ritual, channel, and recognition mechanic in it reinforces that self-image.
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
Playbooks by Goal
Launching a Community from Zero
- Recruit 20–50 founding members manually: DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
- Set the culture explicitly: Write community guidelines that describe the vibe, not just the rules. What does great participation look like here?
- Seed conversations before launch: Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
- 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.
- Define your core loop: What action do you want members to take weekly? Make it easy and reward it publicly.
Growing an Existing Community
- Audit where members drop off: Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
- 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.
- Surface member wins publicly: Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
- Run recurring community rituals: Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
- Identify and invest in power users: participation is usually heavily skewed toward a small minority (Inferred; verify against this community's own posts-per-member distribution before quoting a ratio). Give the observed top contributors recognition, early access, moderator roles, or product input.
Building a Brand Ambassador / Advocate Program
- Identify candidates: Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
- Make the ask personal: Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
- Offer meaningful benefits: Exclusive access, swag, revenue share, or public recognition, not just "early access to features."
- Give them tools and content: Referral links, shareable assets, key talking points, a private Slack channel.
- Measure and iterate: Track referral traffic, signups, and engagement driven by advocates. Double down on what works.
Community-Led Support (Deflection + Retention)
- Create a searchable knowledge base from top community questions
- Recognize members who help others: "Community Expert" badges, leaderboards, shoutouts
- Close the loop with product: When community feedback drives a change, announce it publicly and credit the members who raised it
- Monitor sentiment weekly: Look for patterns in complaints or confusion before they become churn signals
Platform Selection Guide
| Platform | Best For | Watch Out For |
|---|---|---|
| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |
| Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |
| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |
| High-volume public communities; SEO benefit | You don't own it; moderation is hard | |
| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |
| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
Show full SKILL.md (586 more words)Show less
Community Health Metrics
Track these signals weekly. Label every number by evidence class, Boundaries below forbids stating any of them without a source, window, and denominator:
- Observed: read directly from the platform's admin view or export. Name the view and the date pulled.
- Computed: derived from observed values. Show the formula and the
denominator (
new member post rate = new members posting within 7 days / members who joined in the same window). - Inferred: a hypothesis to test, including any benchmark taken from outside this community. Never word it as this community's fact.
- Unknown: the platform does not expose the measure. State what would resolve it.
Metrics:
- DAU/MAU ratio: Stickiness (Computed: daily actives / monthly actives). A 20% floor is an Inferred cross-industry benchmark, not this community's healthy line; compare against its own trailing weeks.
- 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
- Engagement concentrates in a handful of accounts: compute the share of posts from the top 5 posters over a stated window before calling it a warning
- 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.
Community Strategy Doc: exact headings
# <Community name>: Strategy
## Identity
Member identity reinforced: <who members are or aspire to be>
Who is explicitly not the member: <exclusion>
## Platform Choice
Chosen: <platform> | Rejected: <platform> because <watch-out from the table>
Evidence class for any cited benchmark: Observed | Computed | Inferred | Unknown
## Core Loop
Weekly member action: <one action>
What makes it easy: <mechanic>
How it is rewarded publicly: <mechanic>
Where new value re-enters: <mechanic>
## Seeding Plan
Founding members (20–50, manually recruited): <source list>
Pre-launch seed posts: <5–10 topics that model the behavior>
Culture statement: <what great participation looks like here>
## 90-Day Plan
Days 0–30 | Days 31–60 | Days 61–90, for each: goal, rituals live,
owner, primary metric with its denominator
## Measurement
Primary metric: <metric> = <formula> / <denominator>, window <n> days
Diagnostics (2–4): <metric + evidence class each>
## Open Gates
<authorization or evidence still missing; use the halt contract below>The other five deliverables use these headings:
- Channel Architecture: Channel | Purpose | Who posts | Posting rules | Success signal
- New Member Journey: Pinned post / DM template / Day 1–7 prompts / First-win definition / Drop-off checkpoint
- Community Ritual Calendar: Ritual | Cadence | Owner | Member job | Kill condition
- Ambassador Program Brief: Criteria / Benefits / Outreach template / Disclosure requirement / Tracking plan
- Health Audit Report: Metrics with evidence class and denominator / Diagnosis / Top 3 priorities / What would disprove the diagnosis
Halt Contract
Use this exact format when authorization, evidence, or an enforcement decision blocks the requested result: including the space-creation, invite, role, moderation, removal, and announcement gate and the enforcement-outcome gate in Boundaries:
HALT: <one-line blocker>
Why it blocks: <specific missing authority or evidence>
Resolve with:
1. <option>
2. <option>
3. <option, when useful>
Waiting for: <the exact item or approval>Continue with safe drafts, plans, or worksheets only when they remain useful and do not imply the blocker was resolved.
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. - Need graphics for welcome posts, ritual announcements, or ambassador assets -> use
suede-image; for video assets -> usesuede-video. - Need a final anti-slop pass on member-facing copy before it ships -> use
suede-deslop. - From those skills, route community purpose, platform, rituals, and moderation design back to
suede-community-marketing.
© 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 3 other files in skills/suede-community-marketing of JasonColapietro/suede-creator-skills.
- SKILL.md
- CARD.md
- agents/openai.yaml
- evals/evals.json
Open the folder on GitHubat commit e5f94d7
Compare with similar skills
Suede Community Marketing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Suede Community Marketing this skillJasonColapietro/suede-creator-skills | 127 | — | ~3k | Automated safety check: Pass | MIT | |
| Customer ResearchNexus-JPF/note-companion | 870 | 6 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Reddit Researchlignertys/reddit-research-skills | 14 | — | ~3.8k | Automated safety check: Warn | MIT | |
| 28 Community Building Globalminhnv0807/ai-business-skills | 609 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Community MarketingNexus-JPF/note-companion | 870 | 4 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Community Seeding Planminhnv0807/ai-business-skills | 609 | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Reddit Research
lignertys/reddit-research-skills
Researches what people say on Reddit through semantic search on reddapi.dev: pain points, product validation, competitor research and subreddit trends.
28 Community Building Global
minhnv0807/ai-business-skills
A skill your agent uses when a PERSONAL brand needs its OWN community — Skool, Mighty Networks, Discord, Circle, or Slack: a three-layer public, member, and inner-circle blueprint, seven-day…
Community Marketing
Nexus-JPF/note-companion
Build and leverage online communities to drive product growth and brand loyalty.
Community Seeding Plan
minhnv0807/ai-business-skills
Plans honest participation in outside communities such as Reddit, Discord and Facebook Groups, with a rules-based community list, roster, posts, replies and calendar.
Community Management
social-media-skills/skills
A skill your agent uses to build a genuine community — turning an audience into people who interact with each other, not just with the brand.
More from JasonColapietro/suede-creator-skills
All 78 skills in this repoSuede 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.
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.
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.
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.
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.
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.
Related
Questions about Suede Community Marketing
What does Suede Community Marketing do?
Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy. Suede Community Marketing is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy.
When should I use Suede Community Marketing?
Suede Community Marketing fits situations like: growing a Discord; comparable product community.
How do I install Suede Community Marketing in Claude Code?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a claude-code`. Or copy the skill folder (skills/suede-community-marketing in JasonColapietro/suede-creator-skills) into .claude/skills/suede-community-marketing in your project. Claude Code loads it when a task matches its description.
How do I install Suede Community Marketing in Codex?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-community-marketing -a codex`. Or copy the skill folder (skills/suede-community-marketing in JasonColapietro/suede-creator-skills) into .agents/skills/suede-community-marketing in your project. Codex loads it when a task matches its description.
Can I use Suede Community Marketing 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-community-marketing -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-community-marketing, .gemini/skills/suede-community-marketing, .github/skills/suede-community-marketing and .opencode/skills/suede-community-marketing in your project.
What does Suede Community Marketing need to run?
SKILL.md names no scripts, command-line tools or credentials: Suede Community Marketing is instructions for the agent only.
Does Suede Community Marketing 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 Community Marketing 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 Community Marketing use?
Suede Community Marketing 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 Community Marketing use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Suede Community Marketing?
Skills that share tags, products or a category with Suede Community Marketing: Customer Research (Nexus-JPF/note-companion, 870 stars), Reddit Research (lignertys/reddit-research-skills, 14 stars), 28 Community Building Global (minhnv0807/ai-business-skills, 609 stars) and Community Marketing (Nexus-JPF/note-companion, 870 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Suede Community Marketing?
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.