Reddit Warmup - part of the Browser Automation Solutions pack. Browser-automation skills for e-commerce and data extraction.
---
name: reddit-warmup
description: "Runtime-neutral Reddit account warm-up and brand promotion skill for AI agents. Systematically grow newly registered or existing Reddit accounts into credible identities, then organically plant brand content in target subreddits to eventually promote products or tools. Use for: register or take over a Reddit account and start the full warm-up cycle, build a credible Reddit account from scratch, run automated daily tasks on a schedule, camp on a post after publishing to reply, run multiple accounts sequentially. Triggers: reddit warmup / 30-day warmup / start warmup / build reddit karma / reddit brand promotion / reddit automated posting / today's task - reddit warmup <user> / Day N warmup / enter brand phase / refresh subreddit pool / camp <user> / stop camping / pause warmup / resume warmup / delete account / promote on reddit. EXECUTION RULE: before taking any action, load the reference files listed in the Phase Router section of this skill. Do not call browser-act, write any state file, or execute any step until the required reference files have been loaded."
---
# Reddit Account Warm-up (30-Day Brand Promotion)
Builds authentic-looking Reddit accounts through a 30-day progression, then uses them to promote any brand the user configures. State files are managed as local files under `~/.reddit-warmup/<username>/`.
**Agent compatibility:** this skill is runtime-neutral. It can be used by any agent environment that can load local Markdown references, read/write local JSON/YAML/text files, list local directories, run shell commands for `browser-act`, and continue a conversation after a user approval reply. Do not depend on runtime-specific question widgets, background agents, sub-agents, notification events, or tool names.
**Execution boundary:** every Reddit-facing browser, page, network, publishing, and verification operation must use `browser-act` CLI as the only browser execution tool. No other browser execution path is allowed. Use `browser-act state` / `get markdown` / `get title` / screenshots / network capture for verification. Local state files are the only non-browser exception and may be handled with the host agent's normal local file read/write/list capabilities. If browser-act cannot complete a step, stop, log/notify, or use browser-act `remote-assist`; never fall back to another browser execution tool. Details in `references/browser-act-rules.md`.
**Three stages:**
- **Days 2-14 -Lurk**: browse and upvote only
- **Days 15-29 -Comment**: AI-generated natural comments; up to 1 non-brand practice post per week
- **Days 30+ -Promote**: comments + up to 2 posts/week (1 normal + 1 promotional)
**Core rule: one account = one browser profile = one proxy.** Never swap, never mix.
---
## Step 0 -Load Reference Files (required before any action)
Instructions live in separate files loaded on demand. Load the files for the current context before taking any action. Prior knowledge does not substitute for loading the current reference files.