reddit-warmup
Reddit account onboarding and a staged 30-day warm-up workflow through BrowserAct CLI. Use for Reddit warmup, daily browsing and engagement, account handover, reviewing pending comments/posts, and configured brand-promotion workflows.
Install / Use
npx skills add browser-act/skills --skill reddit-warmupInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of reddit-warmup
reddit-warmup scores 96/100 on our quality scale, 221st of 2,790 Automation skills we index (top 8%).
Its SKILL.md is 22 KB long, well organised into 20 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
With 6,001 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so reddit-warmup is actively maintained.
- Our last check on 2026-11-15 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
reddit-warmup compared with similar skills
All 4 of these similar skills score higher than reddit-warmup; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| reddit-warmup (this skill)by browser-act | 96 | 6.0k | 3mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install reddit-warmup?
- Run
npx skills add browser-act/skills --skill reddit-warmup. The install tabs above show the steps for each supported agent. - Which AI agents does reddit-warmup work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is reddit-warmup safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is reddit-warmup still maintained?
- The repository was last updated about 3 months ago, so reddit-warmup is actively maintained.
Skill content
View source on GitHubname: 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.
| Context | Load these files (in order) |
|---|---|
| config.yaml not found (onboarding) | references/phase1-onboarding.md only |
| Phase 2, any stage -start of run | references/browser-act-rules.md ->references/phase2-preflight.md |
| Stage 1 (Days 2-14) execution | references/stage1-lurk.md |
| Stage 2 (Days 15-29) execution | references/stage2-comment.md ->references/approval-rules.md |
| Stage 3 (Day 30+) execution | references/stage3-promote.md ->references/approval-rules.md |
| Notification / inbox check | references/notification-check.md (called from phase2-preflight Step 6) |
| Daily tail recon + feedback | references/end-of-day-recon.md ->references/comment-follow-up.md |
| Daily report + anomaly check | references/anomaly-detection.md |
Language
All process output to the user (plan confirmation, progress updates, process notifications) follows the user's language.
Red Lines (every account, every stage, no exceptions)
| Rule | Why |
|------|-----|
| Never delete any post/comment in first 30 days | Deletion is a stronger bot signal than silence |
| Email verified immediately after registration | Unverified accounts get silently filtered by many subs' AutoMod |
| No DMs, no friend requests in first 30 days | New-account DMs trigger anti-harassment heuristics instantly |
| No unsubscribing in first 30 days | Sub-hopping looks like a burner account |
| Never edit the same comment more than twice | Repeated edits flag the account |
| All browser open uses --headed | |
| All browser work goes through browser-act CLI | No alternate execution path |
State Files
All state lives in ~/.reddit-warmup/<username>/:
| File | Purpose |
|------|---------|
| config.yaml | Browser ID, proxy, subreddits, keywords, timezone |
| progress.json | Current day, karma, stage, last_run, pause flags, week counters |
| sub_profiles.json | Per-sub risk cache (karma/age gate, rules, flair, filter rate) -14-day TTL |
| activity_log.jsonl | Append-only log; every action recorded here |
| pending_approval/<batch_id>/ | Batches awaiting user pick -no expiry while unpicked, then retired after skip/publish |
| drafts/<batch_id>/ | Published / auto-pick audit records and delayed replay records |
| evidence/ | Per-event screenshots |
| images/ | Downloaded images for Stage 3 image posts |
| last_run.png | Most recent run screenshot |
Templates: assets/config.yaml.template, assets/progress.json.template, assets/sub_profiles.json.template, assets/persona.json.template.
How the agent manages these: use the host environment's normal local-file capabilities to load JSON/YAML/text, rewrite whole state files, and list matching account/batch directories. Append to JSONL by reading existing content and writing it back with a new line. Do not use shell text-processing shortcuts for state mutation.
Keyword Rotation
The user's keywords.find and keywords.brand typically have more than one entry. Daily tasks automatically rotate one term from the list so activity naturally disperses.
| List | Rotates? | Reason |
|------|--------|------|
| keywords.find | Daily rotation | Swap daily so search result subsets naturally shift |
| keywords.brand | Rotates per brand post | Alternate between different selling points per post |
| keywords.content | NONo rotation | Persona descriptors form a whole; splitting them causes voice drift |
Rotation state in progress.json
"keyword_rotation": {
"find_index": <int>, // index to use next time Stage 2/3 uses keywords.find
"brand_index": <int> // index to use next time Path B uses keywords.brand
}
Both indices start at 0 and increment by 1 per use. Retrieval: list[index % len(list)].
- List has only 1 item ->always uses that one (no error)
- User adds/removes items mid-stream ->index just modulos to the new length
- List becomes empty ->skip the current use case
When to increment
| Trigger | Increment |
|----------------|---------|
| Stage 2/3 uses find keyword to search candidate posts | +1 find_index (at most once per day) |
| Path B post draft generation determines today's brand angle | +1 brand_index (per draft generation, regardless of publish) |
Write back to progress.json at the end of the run.
User-facing commands
| User says | Effect |
|-------|------|
| "Reset keyword rotation <username>" | find_index = 0, brand_index = 0 |
| "Next keyword <username>" | find_index += 1, brand_index += 1 |
| "Which keyword today <username>" | Display today's rotated keyword for find and brand |
Core Principles
- Strictly stage-gated.
current_day = (today - start_date).days + 1decides the stage. No jumping ahead. - Preview first, execute immediately. Show today's plan as one short message, then start -don't wait for "go".
- Auto-execute safe actions, pause for publishing. Browse / upvote / subscribe / scrape run non-stop. These pause for explicit user ack: CAPTCHA / bot challenge, email verification, every comment/post publish (per approval_policy), inbox reply, brand exposure warning, Stage 3 entry decision card.
- Once per scheduler day. If
progress.json.last_run_scheduler_date == today_scheduler, show cached report and exit. Approval publish flows do not update this field and do not count as the daily run. - All time comparisons use
config.yaml ->account.timezone. Never machine-local, never UTC. Timestamps = ISO 8601 with offset.
Approval Rules -Policy-Driven Content Publishing
All content publishing (comments, posts, brand or non-brand) is governed by config.yaml.approval_policy -the single source of truth. Full rules in references/approval-rules.md.
Master policy table:
| approval_policy | Non-brand content | Brand-bearing (Stage 2) | Brand-bearing (Stage 3) |
|---|---|---|---|
| manual | User picks (no expiry) | User picks (no expiry) | User picks (no expiry) |
| auto | Agent auto-picks & publishes | Agent auto-picks & publishes | Agent auto-picks & publishes |
| auto_stage2 | Agent auto-picks & publishes | Agent auto-picks & publishes | User picks (no expiry) |
Change approval policy: "set approval to manual / auto / auto_stage2 for <username>" ->agent first warns that changing between auto-publish and approval paths changes the account's behavior pattern and may increase risk. If the user still confirms, write to config.yaml; takes effect next run. Do not auto-suggest switching to auto mode because of missed or stale approvals.
Brand-bearing determination: Variant D / any keywords.brand token hit / Path B generated post.
Brand Exposure warning: always computed. User-picks paths ->displayed in chat before variants. Auto paths ->logged silently.
Sub verification (Path B only): always runs regardless of policy -blocked sub = post skipped entirely.
Approval (user-picks paths only): no time limit while unpicked -batch stays in pending_approval/ until user replies. If one run generates several comments/replies plus posts, store all of them and show one same-account Approval Batch Request containing all currently reviewable items. Comments/replies are ordered before posts. The user can approve in bulk (all A) or per item (1 B, 2 skip, 3 revise title). Each item still carries its own batch_id, browser_id, platform, skill, and account metadata, so execution remains deterministic. Clear approve/skip actions publish or retire items sequentially; do not publish in parallel. After publish/skip, remove each handled item from pending_approval and keep the audit record outside the hot-approval pool. Batches older than 7 days are cleaned up by Pre-flight (post almost certainly dead).
Hot Approval (Rule C6): natural-language approval in any conversation -D, all A, 1 B, 2 skip, publish B, skip, make item 1 shorter, etc. ->agent resolves item(s) from the Approval Batch anchor, item number, batch_id, or local pending-approval file lookup ->normalizes the message to internal pick / skip / revise actions. Clear picks start a fresh browser-act run session with the stored browser_id, open directly to /user/me/ for a short account check, then publish stored variants sequentially through the optimized production flow. Clear revise requests update targeted pending items and redisplay one anchored Approval Batch Request for unresolved items. meta.json carries platform, skill, username, browser_id, batch_id, and full draft/variant text for self-contained execution; it must not depend on any previous browser-act session surviving.
Hard execution rule: user approval is not complete when the agent writes a choice file, marker, or local state note. Approval is complete only after the browser publish flow runs, result is verified, activity_log.jsonl / progress are updated, and the fi
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
