reddit-warmup

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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`

```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 |

---

From browser-act/skills, MIT.

More from browser-act/skills