community-forum

Name: community-forum
Author: kostja94

821installs109forks

How to install community-forum?

kostja94/marketing-skills/community-forum

$npx -y skills add kostja94/marketing-skills --skill community-forum

Installs into the current project.

Summary

When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora,

Files · 1

View on GitHub

SKILL.md

1	# Channels: Community & Forum Promotion
2
3	Guides forum promotion, community invitation, and vertical community marketing. Community-led growth (CLG) costs ~90% less than paid acquisition with ~3.2x higher customer LTV. Indie Hackers delivers ~23% conversion vs Product Hunt ~3%; HN and Reddit require sustained engagement. For cold start planning (first users, launch channels), see cold-start-strategy. For indie hacker strategy (first 100 users, Build in Public content framework, Indie Hackers tactics), see indie-hacker-strategy.
4
5	When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
6
7	## Initial Assessment
8
9	Check for project context first: If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and brand voice.
10
11	Identify:
12	1. Goal: Leads, community growth, brand awareness
13	2. Platform fit: Indie Hacker, HN, Reddit, Discord, vertical forums
14	3. Timeline: One-time launch vs sustained (4-6 months for Indie Hackers)
15
16	## Forum Types
17
18	\| Platform \| Audience \| Use \|
19	\|----------\|----------\|-----\|
20	\| Indie Hacker \| Indie makers, founders \| Sustained engagement; authentic journey posts; ~23% conversion vs PH 3% \|
21	\| Hacker News \| Tech, startups \| Show HN launch; ~1,300 posts/day; front page = luck + timing \|
22	\| Hackernoon \| Dev, tech readers \| Content distribution \|
23	\| Industry forums \| Niche verticals \| Discount codes for leads; search "[industry] forum"; post event/activity promotion; see discount-marketing-strategy for code strategy \|
24	\| Reddit \| Subreddit-specific \| See reddit-posts; 90/10 rule; 29+ posts for traction \|
25	\| Discourse (self-hosted forum) \| Community-specific \| Owned forum; full SEO/GEO control; see Discourse SEO section below \|
26
27	## Discourse (Self-Hosted Forum) SEO
28
29	If you run a Discourse forum (or similar self-hosted forum), SEO/GEO considerations differ from posting on third-party platforms:
30
31	\| Practice \| Guideline \|
32	\|----------\|-----------\|
33	\| Guest access \| Allow anonymous reading for categories meant to attract traffic; login-only mode severely limits indexed pages \|
34	\| Topic structure \| First post carries SEO weight; write clear titles and substantive opening posts; avoid fragmented short topics \|
35	\| Sitemap & robots \| Discourse generates sitemaps automatically; monitor in GSC as a separate property (subdomain or subdirectory) \|
36	\| Content quality \| Merge duplicates, mark resolved threads, surface FAQ topics—forum-level quality signals affect crawl and citation \|
37	\| GEO \| Structured topic titles and well-formed opening posts are extractable by AI tools; forum format with timelines and accepted answers lends credibility \|
38	\| Subdomain vs subdirectory \| Discourse recommends subdomain for operational reasons; search engines do not inherently favor either for ranking—choose based on infrastructure, not SEO alone \|
39
40	## Hacker News Launch
41
42	\| Practice \| Guideline \|
43	\|----------\|-----------\|
44	\| Title \| "Show HN: [Product] - [specific problem solved]"; honest, no clickbait \|
45	\| Timing \| Tue-Thu; peak US hours; avoid weekends, Mon, Fri \|
46	\| First comment \| Invitation to engage; product status (beta/MVP); differentiated solution; try-it link \|
47	\| Assets \| Live demo, GIFs, screenshots, 30-60s demo video \|
48	\| Expectation \| Traffic spike, not sustained growth; partly luck-dependent \|
49
50	## Indie Hackers Best Practices
51
52	- Sustained engagement: 4–6 months; not a one-time launch
53	- Content: Authentic journey posts; product "sprinkled within"; avoid heavy promotion
54	- Result: ~23% conversion vs Product Hunt ~3%; organic traffic from authentic sharing
55
56	For full Indie Hackers tactics, Build in Public content framework (40/30/20/10), first 100 users → indie-hacker-strategy.
57
58	## Community Invitation Tactics
59
60	\| Channel \| Method \|
61	\|---------\|--------\|
62	\| Welcome email \| Post-signup automation; 4x open, 5x CTR vs regular campaigns \|
63	\| Homepage CTA \| Button, popup, banner; above-the-fold upgrade CTA \|
64	\| In-site placement \| High-visibility areas; user-focused sections (e.g. dashboard, settings) \|
65	\| Banner \| Homepage, carousel below hero \|
66	\| Registration emails \| Success/confirmation email with community link \|
67	\| EDM campaign \| Newsletter + banner, interview-for-membership \|
68	\| *Discord

People who liked this also viewed

6 picks

Type

community-forum

821installs109forks

View on GitHub

How to install community-forum?

kostja94/marketing-skills/community-forum

$npx -y skills add kostja94/marketing-skills --skill community-forum

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Channels: Community & Forum Promotion
2
3	Guides forum promotion, community invitation, and vertical community marketing. Community-led growth (CLG) costs ~90% less than paid acquisition with ~3.2x higher customer LTV. Indie Hackers delivers ~23% conversion vs Product Hunt ~3%; HN and Reddit require sustained engagement. For cold start planning (first users, launch channels), see cold-start-strategy. For indie hacker strategy (first 100 users, Build in Public content framework, Indie Hackers tactics), see indie-hacker-strategy.
4
5	When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
6
7	## Initial Assessment
8
9	Check for project context first: If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and brand voice.
10
11	Identify:
12	1. Goal: Leads, community growth, brand awareness
13	2. Platform fit: Indie Hacker, HN, Reddit, Discord, vertical forums
14	3. Timeline: One-time launch vs sustained (4-6 months for Indie Hackers)
15
16	## Forum Types
17
18	\| Platform \| Audience \| Use \|
19	\|----------\|----------\|-----\|
20	\| Indie Hacker \| Indie makers, founders \| Sustained engagement; authentic journey posts; ~23% conversion vs PH 3% \|
21	\| Hacker News \| Tech, startups \| Show HN launch; ~1,300 posts/day; front page = luck + timing \|
22	\| Hackernoon \| Dev, tech readers \| Content distribution \|
23	\| Industry forums \| Niche verticals \| Discount codes for leads; search "[industry] forum"; post event/activity promotion; see discount-marketing-strategy for code strategy \|
24	\| Reddit \| Subreddit-specific \| See reddit-posts; 90/10 rule; 29+ posts for traction \|
25	\| Discourse (self-hosted forum) \| Community-specific \| Owned forum; full SEO/GEO control; see Discourse SEO section below \|
26
27	## Discourse (Self-Hosted Forum) SEO
28
29	If you run a Discourse forum (or similar self-hosted forum), SEO/GEO considerations differ from posting on third-party platforms:
30
31	\| Practice \| Guideline \|
32	\|----------\|-----------\|
33	\| Guest access \| Allow anonymous reading for categories meant to attract traffic; login-only mode severely limits indexed pages \|
34	\| Topic structure \| First post carries SEO weight; write clear titles and substantive opening posts; avoid fragmented short topics \|
35	\| Sitemap & robots \| Discourse generates sitemaps automatically; monitor in GSC as a separate property (subdomain or subdirectory) \|
36	\| Content quality \| Merge duplicates, mark resolved threads, surface FAQ topics—forum-level quality signals affect crawl and citation \|
37	\| GEO \| Structured topic titles and well-formed opening posts are extractable by AI tools; forum format with timelines and accepted answers lends credibility \|
38	\| Subdomain vs subdirectory \| Discourse recommends subdomain for operational reasons; search engines do not inherently favor either for ranking—choose based on infrastructure, not SEO alone \|
39
40	## Hacker News Launch
41
42	\| Practice \| Guideline \|
43	\|----------\|-----------\|
44	\| Title \| "Show HN: [Product] - [specific problem solved]"; honest, no clickbait \|
45	\| Timing \| Tue-Thu; peak US hours; avoid weekends, Mon, Fri \|
46	\| First comment \| Invitation to engage; product status (beta/MVP); differentiated solution; try-it link \|
47	\| Assets \| Live demo, GIFs, screenshots, 30-60s demo video \|
48	\| Expectation \| Traffic spike, not sustained growth; partly luck-dependent \|
49
50	## Indie Hackers Best Practices
51
52	- Sustained engagement: 4–6 months; not a one-time launch
53	- Content: Authentic journey posts; product "sprinkled within"; avoid heavy promotion
54	- Result: ~23% conversion vs Product Hunt ~3%; organic traffic from authentic sharing
55
56	For full Indie Hackers tactics, Build in Public content framework (40/30/20/10), first 100 users → indie-hacker-strategy.
57
58	## Community Invitation Tactics
59
60	\| Channel \| Method \|
61	\|---------\|--------\|
62	\| Welcome email \| Post-signup automation; 4x open, 5x CTR vs regular campaigns \|
63	\| Homepage CTA \| Button, popup, banner; above-the-fold upgrade CTA \|
64	\| In-site placement \| High-visibility areas; user-focused sections (e.g. dashboard, settings) \|
65	\| Banner \| Homepage, carousel below hero \|
66	\| Registration emails \| Success/confirmation email with community link \|
67	\| EDM campaign \| Newsletter + banner, interview-for-membership \|
68	\| *Discord

People who liked this also viewed

6 picks

Type