Community ForumSAFE

Agent Skills for Marketing — SEO, Social, Influencer & More. 160+ open-source skills for SEO, content, 40+ page types, paid ads, channels, and strategies. Add project context; get tailored, production-ready output. Cursor, Claude Code, OpenClaw — no lock-in.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: community-forum
description: 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," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
metadata:
  version: 1.1.1
---

# Channels: Community & Forum Promotion

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**.

**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.

## Initial Assessment

**Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Identify:
1. **Goal**: Leads, community growth, brand awareness
2. **Platform fit**: Indie Hacker, HN, Reddit, Discord, vertical forums
3. **Timeline**: One-time launch vs sustained (4-6 months for Indie Hackers)

## Forum Types

| Platform | Audience | Use |
|----------|----------|-----|
| **Indie Hacker** | Indie makers, founders | Sustained engagement; authentic journey posts; ~23% conversion vs PH 3% |
| **Hacker News** | Tech, startups | Show HN launch; ~1,300 posts/day; front page = luck + timing |
| **Hackernoon** | Dev, tech readers | Content distribution |
| **Industry forums** | Niche verticals | Discount codes for leads; search "[industry] forum"; post event/activity promotion; see **discount-marketing-strategy** for code strategy |
| **Reddit** | Subreddit-specific | See **reddit-posts**; 90/10 rule; 29+ posts for traction |
| **Discourse (self-hosted forum)** | Community-specific | Owned forum; full SEO/GEO control; see Discourse SEO section below |

## Discourse (Self-Hosted Forum) SEO

If you run a Discourse forum (or similar self-hosted forum), SEO/GEO considerations differ from posting on third-party platforms:

| Practice | Guideline |
|----------|-----------|
| **Guest access** | Allow anonymous reading for categories meant to attract traffic; login-only mode severely limits indexed pages |
| **Topic structure** | First post carries SEO weight; write clear titles and substantive opening posts; avoid fragmented short topics |
| **Sitemap & robots** | Discourse generates sitemaps automatically; monitor in GSC as a separate property (subdomain or subdirectory) |
| **Content quality** | Merge duplicates, mark resolved threads, surface FAQ topics—forum-level quality signals affect crawl and citation |
| **GEO** | Structured topic titles and well-formed opening posts are extractable by AI tools; forum format with timelines and accepted answers lends credibility |
| **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 |

## Hacker News Launch

| Practice | Guideline |
|----------|-----------|
| **Title** | "Show HN: [Product] - [specific problem solved]"; honest, no clickbait |
| **Timing** | Tue-Thu; peak US hours; avoid weekends, Mon, Fri |
| **First comment** | Invitation to engage; product status (beta/MVP); differentiated solution; try-it link |
| **Assets** | Live demo, GIFs, screenshots, 30-60s demo video |
| **Expectation** | Traffic spike, not sustained growth; partly luck-dependent |

## Indie Hackers Best Practices

- **Sustained engagement**: 4–6 months; not a one-time launch
- **Content**: Authentic journey posts; product "sprinkled within"; avoid heavy promotion
- **Result**: ~23% conversion vs Product Hunt ~3%; organic traffic from authentic sharing

For full Indie Hackers tactics, Build in Public content framework (40/30/20/10), first 100 users → **indie-hacker-strategy**.

## Community Invitation Tactics

| Channel | Method |
|---------|--------|
| **Welcome email** | Post-signup automation; 4x open, 5x CTR vs regular campaigns |
| **Homepage CTA** | Button, popup, banner; above-the-fold upgrade CTA |
| **In-site placement** | High-visibility areas; user-focused sections (e.g. dashboard, settings) |
| **Banner** | Homepage, carousel below hero |
| **Registration emails** | Success/confirmation email with community link |
| **EDM campaign** | Newsletter + banner, interview-for-membership |
| **Discord** | Post event/community info; founder engagement 2-3h/day |
| **Vertical forums** | Search "[industry] forum"; post event/activity promotion |
| **Post-login form** | In-app signup form shown after login; high-intent placement |

**Welcome email best practices**: One clear CTA per email; front-load value in subject; personalize (signup source, interests); link to best content, events; ask questions (~75% reply rate). Automated 2-4 email sequence.

## Vertical Community Channels

| Principle | Guideline |
|-----------|-----------|
| **Target** | Find channels where target audience gathers |
| **Niche over broad** | Industry-specific subgroups; avoid mass posting |
| **Caution** | Mass posting risks removal; match community tone; choose wording carefully |
| **Examples** | Reddit subreddits, Discord servers, Quora, X, Hacker News, Stack Overflow, niche B2B communities |
| **Regional** | Lar

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.