reddit-engagement

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# Reddit Engagement

Reddit can drive massive developer traffic — or get you banned for self-promotion. This skill covers authentic engagement across developer subreddits, understanding each community's rules, and the comment-first strategy that actually works.

---

## Before You Start

1. Read `.agents/developer-audience-context.md` if it exists
2. Identify which subreddits your developers actually use
3. Create a dedicated Reddit account (using your real identity is fine, but don't use your company name as username)
4. Understand: Reddit requires months of genuine participation before self-promotion

---

## Developer Subreddit Landscape

### High-Traffic Developer Subreddits

| Subreddit | Members | Culture | Self-promo tolerance |
|-----------|---------|---------|---------------------|
| r/programming | 6M+ | Technical depth, skeptical | Very low |
| r/webdev | 2M+ | Practical, career-focused | Low |
| r/javascript | 2M+ | Framework debates, news | Low |
| r/Python | 1.5M+ | Helpful, educational | Moderate |
| r/devops | 500K+ | War stories, tools | Moderate |
| r/selfhosted | 400K+ | DIY, open source love | Moderate for OSS |
| r/sysadmin | 800K+ | Cynical, enterprise-focused | Very low |
| r/learnprogramming | 4M+ | Beginners, supportive | Low |
| r/ExperiencedDevs | 200K+ | Senior discussions, no beginners | Very low |
| r/cscareerquestions | 1M+ | Career advice, compensation | None |

### Niche Technical Subreddits

| Category | Subreddits | Notes |
|----------|------------|-------|
| Languages | r/rust, r/golang, r/typescript, r/cpp, r/java | Often more welcoming to relevant tools |
| Frameworks | r/reactjs, r/vuejs, r/angular, r/nextjs, r/django | Very specific content requirements |
| Infrastructure | r/kubernetes, r/docker, r/aws, r/terraform | Practical problems welcome |
| Specialties | r/netsec, r/machinelearning, r/datascience | Deep expertise expected |

---

## Understanding Subreddit Rules

### Check Before Posting

Every subreddit has different rules. Before engaging:

1. **Read the sidebar** — Rules, posting guidelines, allowed content
2. **Check the wiki** — Many have self-promotion policies
3. **Look at top posts** — What format/content succeeds
4. **Search for your competitors** — How did their posts do?
5. **Check moderator activity** — How strict is enforcement?

### Common Rule Patterns

| Rule type | What it means |
|-----------|---------------|
| "No self-promotion" | Your own stuff is banned entirely |
| "10:1 rule" | 10 helpful comments/posts for every self-promo |
| "No affiliate links" | Even indirect monetization banned |
| "Project showcase Sunday" | Self-promo limited to specific threads |
| "No beginners" | r/ExperiencedDevs, r/cscareerquestionsEU |
| "Text posts only" | No link posts, must add context |

### Self-Promotion Limits by Subreddit

| Tolerance | Subreddits | Strategy |
|-----------|------------|----------|
| **Zero** | r/programming, r/sysadmin, r/cscareerquestions | Don't post your stuff. Comment only. |
| **Showcase threads only** | r/webdev (Showoff Saturday) | Wait for weekly threads |
| **10:1 rule** | Most technical subreddits | Heavy comment investment first |
| **Open source friendly** | r/selfhosted, r/opensource, r/commandline | OSS gets more leeway |
| **More welcoming** | Niche language subs, small communities | Still need participation first |

---

## The Comment-First Strategy

### Why Comments Beat Posts

| Comments | Posts |
|----------|-------|
| Build karma and history | Require karma to post in many subs |
| Establish expertise | Subject to self-promo scrutiny |
| No self-promo restrictions | Often removed if promotional |
| Reach engaged audiences | Compete with all other posts |
| Can mention your work naturally | Direct promo usually fails |

### High-Value Comment Opportunities

| Opportunity | How to find | What to comment |
|-------------|-------------|-----------------|
| Questions in your area | Search by flair or keywords | Detailed, helpful answers |
| Discussions of problems you solve | Monitor relevant keywords | Share approach without pitching |
| Competitor mentions | Search competitor names | Fair comparison, not attack |
| "What tools do you use?" threads | Common in most dev subs | Honest mention among other tools |
| Frustrated users | Posts about problems | Empathize, help, maybe mention if very relevant |

### Comment Templates

**Answering a technical question**:
```
Good question. Here's what's worked for me:

[Specific technical answer with code/steps]

One thing to watch out for: [edge case or caveat]

I've been using [approach/tool] for this, and [specific benefit].
```

**When your tool is directly relevant** (use sparingly):
```
I work on [tool] and we built it specifically for this use case.

The way we handle [problem] is:
[Technical explanation]

From jonathimer/devmarketing-skills, MIT.

More from jonathimer/devmarketing-skills