Auto Commenter
Playwright-driven Claude skill that posts personalized, authentic comments in target communities for community-led growth on Reddit, HN, Indie Hackers, and LinkedIn.
Overview
rokpiy/auto-commenter automates personalized community comments for growth marketers running outbound engagement. It is one of the few high-adoption skills specifically aimed at community-led acquisition rather than SEO or ads. Important: it uses vanilla Playwright—pair with careful rate limits and stealth/browser infrastructure on platforms with strong bot detection.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
git clone https://github.com/rokpiy/auto-commenter.git ~/.claude/skills/auto-commenter
# install Playwright deps per README, then restart Claude CodeHow to use it
Provide target communities, ICP voice, and offer constraints. Review every comment batch before posting. Keep volume low and personalization high to reduce detection risk.
Example prompts
- “Draft 10 personalized Reddit comments for threads about [problem] without being spammy. Our product is [X].”
- “Build a weekly community engagement plan for HN + Indie Hackers around our launch.”
- “Rewrite these auto-drafted comments to sound more human and specific.”
Use cases and examples
- Reddit/HN comment outreach at light scale
- Indie Hackers launch engagement
- LinkedIn comment programs for B2B ICPs
- Community reply drafts grounded in product context
- Growth experiments for conversation-led acquisition
Prerequisites
- Claude Code, Claude.ai Skills, or another Agent Skills–compatible host
- Product/brand context (ICP, offer, URLs, constraints) for grounded outputs
- Optional: `.agents/product-marketing.md` or `.claude/product-marketing.md` in the repo
- Permission to install third-party skills — audit SKILL.md first
- Optional: analytics or ad-platform access when the task needs real performance data
Tips
- Keep triggers specific so Auto Commenter only fires when relevant.
- Audit SKILL.md and any bundled scripts before production use.
- Pair with verification (analytics, QA, human edit) before shipping.
- Re-audit installed skills monthly to avoid context tax from unused packs.