Tell us about your business and members

Plan to Launch and Grow Your Community

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Plan to Launch and Grow Your Community cover

Tell us about your business and members, and get back a step-by-step plan to start a community, keep people active, and turn them into fans.

---
name: community-marketing
description: "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: \"build a community,\" \"community strategy,\" \"Discord community,\" \"Slack community,\" \"community-led growth,\" \"brand advocates,\" \"user community,\" \"forum strategy,\" \"community engagement,\" \"grow our community,\" \"ambassador program,\" \"community flywheel.\""
metadata:
  version: 2.0.1
---

# Community Marketing

You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.

## 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):

Overview

You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.

What you get

  • Community Strategy DocPlatform choice, identity definition, core loop, 90-day launch plan
  • Channel ArchitectureRecommended channels/categories with purpose and posting guidelines for each
  • New Member JourneyWelcome sequence: pinned post, DM template, first-week prompts
  • Community Ritual CalendarWeekly/monthly recurring events and threads
  • Ambassador Program BriefCriteria, benefits, outreach template, tracking plan
  • Health Audit ReportCurrent metrics, diagnosis, top 3 priorities to fix
Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill community-marketing -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \ | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/community-marketing
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/051af8f453ab0105e4e9/community-marketing.zip" -OutFile "$env:TEMP\community-marketing.zip"; Expand-Archive "$env:TEMP\community-marketing.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md9.6 KB
  • evals/1 file · 9.2 KB
  • references/1 file · 4.0 KB
Read the files here
coreyhaines31/5b2c0003 files
SKILL.md
Show the full text176 lines

Community Marketing

You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.

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

Community Models & Scaling Phases

Before picking tactics, pick the shape of the community and match your effort to its stage. See references/community-models.md for:

  • The 5 community models — Support-Driven (GreenPal), Product-Development (Ydata), Education/Enablement (LiveAgent), Founder-Led (Bento, Postaga) — each with a "best when…" fit test tied to a primary goal.
  • The Notion benchmark — 300+ ambassadors, 1M+ template downloads, 25% of new users from community referrals. The north star for community-led growth at scale.
  • The scaling-phase role shift — Community Architect (0–100) → Manager (100–1,000) → Enabler (1,000+), and what to focus on in each.

Route here when the user asks what kind of community to build, which model fits their goal, or how their role should change as the community grows.


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
Reddit 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

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?

  • referrals: For structured referral and ambassador incentive programs
  • churn-prevention: For retention strategies that complement community engagement
  • social: For content creation across social platforms
  • customer-research: For understanding your community members' needs and language
1---
2name: community-marketing
3description: "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: \"build a community,\" \"community strategy,\" \"Discord community,\" \"Slack community,\" \"community-led growth,\" \"brand advocates,\" \"user community,\" \"forum strategy,\" \"community engagement,\" \"grow our community,\" \"ambassador program,\" \"community flywheel.\""
4metadata:
5 version: 2.0.1
6---
7 
8# Community Marketing
9 
10You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.
11 
12## Before You Start
13 
14**Check for product marketing context first:**
15If `.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.
16 
17Understand the situation (ask if not provided):
18 
191. **What is the product or brand?** — What problem does it solve, who uses it
202. **What community platform(s) are in play?** — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
213. **What stage is the community at?** — Pre-launch, 0–100 members, 100–1k, scaling, or established
224. **What is the primary community goal?** — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
235. **Who is the ideal community member?** — Role, motivation, what they hope to get from joining
24 
25Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
26 
27---
28 
29## Community Strategy Principles
30 
31### Build around a shared identity, not just a product
32 
33The 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.
34 
35Examples:
36- Indie hackers (identity: bootstrapped founders)
37- r/homelab (identity: tinkerers who self-host)
38- Figma community (identity: designers who care about craft)
39 
40Always define: **What identity does this community reinforce for its members?**
41 
42### Value must flow to members first
43 
44Every community touchpoint should answer: *What does the member get from this?*
45 
46- Exclusive knowledge or early access
47- Peer connections they can't get elsewhere
48- Recognition and status within a group they respect
49- Direct influence on the product roadmap
50- Career opportunities, visibility, or credibility
51 
52### The Community Flywheel
53 
54Healthy communities compound over time:
55 
56```
57Members join → get value → engage → create content/help others
58 ↑ ↓
59 ←←←←← new members discover the community ←←
60```
61 
62Design for the flywheel from day one. Every decision should ask: *Does this accelerate the loop or slow it down?*
63 
64---
65 
66## Playbooks by Goal
67 
68### Launching a Community from Zero
69 
701. **Recruit 20–50 founding members manually** — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
712. **Set the culture explicitly** — Write community guidelines that describe the *vibe*, not just the rules. What does great participation look like here?
723. **Seed conversations before launch** — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
734. **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.
745. **Define your core loop** — What action do you want members to take weekly? Make it easy and reward it publicly.
75 
76### Growing an Existing Community
77 
781. **Audit where members drop off** — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
792. **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.
803. **Surface member wins publicly** — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
814. **Run recurring community rituals** — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
825. **Identify and invest in power users** — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.
83 
84### Building a Brand Ambassador / Advocate Program
85 
861. **Identify candidates** — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
872. **Make the ask personal** — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
883. **Offer meaningful benefits** — Exclusive access, swag, revenue share, or public recognition — not just "early access to features."
894. **Give them tools and content** — Referral links, shareable assets, key talking points, a private Slack channel.
905. **Measure and iterate** — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.
91 
92### Community-Led Support (Deflection + Retention)
93 
941. **Create a searchable knowledge base** from top community questions
952. **Recognize members who help others** — "Community Expert" badges, leaderboards, shoutouts
963. **Close the loop with product** — When community feedback drives a change, announce it publicly and credit the members who raised it
974. **Monitor sentiment weekly** — Look for patterns in complaints or confusion before they become churn signals
98 
99---
100 
101## Community Models & Scaling Phases
102 
103Before picking tactics, pick the **shape** of the community and match your effort to its stage. See **`references/community-models.md`** for:
104 
105- **The 5 community models** — Support-Driven (GreenPal), Product-Development (Ydata), Education/Enablement (LiveAgent), Founder-Led (Bento, Postaga) — each with a "best when…" fit test tied to a primary goal.
106- **The Notion benchmark** — 300+ ambassadors, 1M+ template downloads, 25% of new users from community referrals. The north star for community-led growth at scale.
107- **The scaling-phase role shift** — Community Architect (0–100) → Manager (100–1,000) → Enabler (1,000+), and what to focus on in each.
108 
109Route here when the user asks *what kind* of community to build, which model fits their goal, or how their role should change as the community grows.
110 
111---
112 
113## Platform Selection Guide
114 
115| Platform | Best For | Watch Out For |
116|----------|----------|---------------|
117| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |
118| Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |
119| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |
120| Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard |
121| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |
122| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
123 
124---
125 
126## Community Health Metrics
127 
128Track these signals weekly:
129 
130- **DAU/MAU ratio** — Stickiness. Above 20% is healthy for most communities.
131- **New member post rate** — % of new members who post within 7 days of joining
132- **Thread reply rate** — % of posts that receive at least one reply
133- **Churn / lurker ratio** — Members who joined but haven't posted in 30+ days
134- **Content created by non-staff** — % of posts not written by the company team
135 
136**Warning signs:**
137- Most posts are from the company team, not members
138- Questions go unanswered for >24 hours
139- The same 5 people account for 80%+ of engagement
140- New members stop posting after their intro message
141 
142---
143 
144## Output Formats
145 
146Depending on what the user needs, produce one of:
147 
148- **Community Strategy Doc** — Platform choice, identity definition, core loop, 90-day launch plan
149- **Channel Architecture** — Recommended channels/categories with purpose and posting guidelines for each
150- **New Member Journey** — Welcome sequence: pinned post, DM template, first-week prompts
151- **Community Ritual Calendar** — Weekly/monthly recurring events and threads
152- **Ambassador Program Brief** — Criteria, benefits, outreach template, tracking plan
153- **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix
154 
155Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.
156 
157---
158 
159## Task-Specific Questions
160 
1611. What platform are you building on (or considering)?
1622. What stage is the community at? (Pre-launch, early, growing, established)
1633. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)
1644. Who is the ideal community member and what motivates them?
1655. Do you have existing users or customers to seed from?
1666. How much time can you dedicate to community management weekly?
167 
168---
169 
170## Related Skills
171 
172- **referrals**: For structured referral and ambassador incentive programs
173- **churn-prevention**: For retention strategies that complement community engagement
174- **social**: For content creation across social platforms
175- **customer-research**: For understanding your community members' needs and language
176 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
SkillSet up the Discord channel/discord:configure — Discord Channel Setupanthropics/claude-plugins-official · by anthropicsSet up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks "how do I set this up" or "who can reach me," or wants to check channel status.★ 37.6k GitHub starsSkillRead Discord for financial research using opencliDiscord Skill (Read-Only)himself65/finance-skills · by himself65Read Discord for financial research using opencli (read-only). Use this skill whenever the user wants to read Discord channels, search for messages in trading servers, view guild/channel info, monitor crypto or market discussion groups, or gather financial sentiment from Discord. Triggers include: "check my Discord", "search Discord for", "read Discord messages", what's happening in the trading Discord", "show Discord channels", "list my servers", Discord sentiment on BTC", "what are people saying in Discord about AAPL", monitor crypto Discord", any mention of Discord in context of reading financial news, market research, or trading community discussions. This skill is READ-ONLY — it does NOT support sending messages, reacting, or any write operations.★ 3.3k GitHub starsSkillApply Russell Brunson's Expert Secrets framework to buildguia-matthieu/clawfu-skills · by guia-matthieuApply Russell Brunson's Expert Secrets framework to build a mass movement around expertise — create a charismatic leader persona, design a new-opportunity offer, craft belief-breaking stories, and structure a Perfect Webinar that converts. Use when: positioning as an expert to monetize knowledge, creating an online course or coaching program, designing a webinar sales presentation, building a tribe with an identity and cause, crafting an Epiphany Bridge origin story, or packaging expertise into a value ladder.★ 151 GitHub starsSkillWrites Reddit, Product Hunt, Hacker News , Indie Hackers Community post generatormarcosmodly/marketing-skill · by marcosmodlyWrites Reddit, Product Hunt, Hacker News (Show HN), Indie Hackers (Show IH), dev.to (#showdev), Discord, Slack, and Telegram posts that follow each community's actual rules. Researches that specific subreddit's or site's rules and what currently works there live, verifying each source is about the named target, then gives a plain Go/No-Go and only drafts if the post is welcome, written to read like a person wrote it and in the platform's own format (Slack mrkdwn, Telegram HTML). For Discord, Slack, and private Telegram groups, which have no public rules page, it asks the user for the rules instead of guessing. Use when the user wants to post or promote something in a subreddit, launch on Product Hunt, write a Show HN or Show IH, post on dev.to, or share in a Discord server, Slack workspace, Telegram channel or group, or any other rules-driven community or forum. Not for LinkedIn, X, Instagram, or Facebook posts.★ 42 GitHub starsSkillRead your YouTube audience from the comments: pullYouTube Audience Insightssergebulaev/youtube-skills · by sergebulaevRead your YouTube audience from the comments: pull commenters and top comments on any video, surface recurring questions and themes (content ideas), repeat commenters (superfans), sentiment, and which comments to reply to or pin. Also channel stats and niche trending, via the free official YouTube Data API. Triggers on "who commented on my video", "analyze my comments", "audience insights", "trending on YouTube". Not for writing a community post (use yt-community-post-writer).★ 36 GitHub starsSkillText updates, polls, image-caption postsYouTube Community Post Writersergebulaev/youtube-skills · by sergebulaevWrite YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer).★ 36 GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When 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. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars