reddit-organic-warmup
Skill1 starsChanged 3 months agoMITView on GitHub
Create low-risk Reddit organic post drafts, subreddit-native title options, first comments, and reply banks for account warmup, karma building, pet posts, hobby communities, and non-promotional community participation. Use when the user mentions Reddit organic content, subreddit posting, account warming, karma, cat/dog/pet content, hobby content, community replies, comment banks, or avoiding spammy Reddit behavior. Outputs a ready-to-review Reddit post/comment pack with risk notes and posting boundaries.
In this repository9 other files it gives its agents.
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. About 0 are common, 21 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill for organic Reddit participation built around real, non-promotional content.
- Distinctive: line 22
Read visible rules before drafting.
- Distinctive: line 23
Prefer communities where casual posts and everyday observations are normal.
- Distinctive: line 24
Avoid promotional, controversial, medical, legal, financial, or identity-sensitive framing unless the user provides context and asks for it.
- Distinctive: line 27
Use one simple observation from the media or story.
- Distinctive: line 28
Do not invent a backstory.
- Distinctive: line 29
Do not force a joke.
- Distinctive: line 30
Keep titles short and native to the subreddit.
- Distinctive: line 34
Create 3 optional first-comment options.
- Distinctive: line 35
Create 5 lightweight reply options for likely comments.
- Distinctive: line 38
Remove anything that sounds like engagement bait, brand promotion, AI filler, or karma farming.
- Distinctive: line 39
Do not include links, product mentions, business names, or calls to action.
- Distinctive: line 40
If the subreddit rules are unclear, output drafts only and ask for review before posting.
- Distinctive: line 43
Do not post automatically unless the user explicitly asks and the authenticated browser/account context is available.
- Distinctive: line 44
Keep a human approval step before final submit.
- Distinctive: line 80
No em dashes. Use a comma, a period, or a single hyphen if a visual pause is really needed.
- Distinctive: line 82
No forced three-item lists (three parallel clauses, three bullets that all sound the same shape).
- Distinctive: line 84
Every longer comment needs at least one concrete, specific detail, a number, a name, a moment, not an abstract summary of a category of …
- Distinctive: line 86
Don't wrap up with a summary, a moral, or "hope this helps." Real comments often just stop.
- Distinctive: line 87
Keep real jargon from the poster's world if it fits (specific tool names, specific metrics), but don't follow it with a definition, a …
- Distinctive: line 90
Before handing a draft back, run it through this checklist.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reddit Organic Warmup
Use this skill for organic Reddit participation built around real, non-promotional content. The goal is steady account activity and community fit, not selling.
Inputs
- A photo, video, anecdote, or topic
- Target subreddit, if available
- Prior account tone or example comments, if available
- Goal: warmup, karma, lightweight community presence, or testing content fit
Workflow
- Check subreddit fit
- Read visible rules before drafting.
- Prefer communities where casual posts and everyday observations are normal.
- Avoid promotional, controversial, medical, legal, financial, or identity-sensitive framing unless the user provides context and asks for it.
- Choose the post angle
- Use one simple observation from the media or story.
- Do not invent a backstory.
- Do not force a joke.
- Keep titles short and native to the subreddit.
- Draft variants
- Create 5 title options.
- Create 3 optional first-comment options.
- Create 5 lightweight reply options for likely comments.
- Risk check
- Remove anything that sounds like engagement bait, brand promotion, AI filler, or karma farming.
- Do not include links, product mentions, business names, or calls to action.
- If the subreddit rules are unclear, output drafts only and ask for review before posting.
- Posting boundary
- Do not post automatically unless the user explicitly asks and the authenticated browser/account context is available.
- Keep a human approval step before final submit.
Output Format
Subreddit:
Media/story:
Post title options:
1.
2.
3.
4.
5.
Suggested first comment:
1.
2.
3.
Reply bank:
1.
2.
3.
4.
5.
Risk notes:
Best next step:Style Rules
Reddit runs an AI-content filter that rejects text that reads as machine-written, separate from any human moderator judgment call. Passing it is a floor, not a quality bar by itself, but failing it means the post never goes up at all. Check every draft against this before handing it back:
- Lowercase sentence starts are fine and common; don't force capitalization everywhere.
- Drop apostrophes in common contractions (
dont,isnt,youre) unless the sentence is meant to read more formal. Keep apostrophes that mark possession (company's). - No em dashes. Use a comma, a period, or a single hyphen if a visual pause is really needed.
- No "not X, it's Y" or "it's not just about X, it's Y" constructions, and no tailing negations like "no guessing" tacked onto the end of a sentence. Say the thing plainly instead.
- No forced three-item lists (three parallel clauses, three bullets that all sound the same shape). Real speech clusters into twos or fours, or just runs on.
- One or two casual filler words per 100-150 words is normal (
honestly,tbh,kind of,ngl). Every sentence having one is a tell in the other direction. - Every longer comment needs at least one concrete, specific detail, a number, a name, a moment, not an abstract summary of a category of experience.
- Sentence-fragment endings are fine and human (
the second one's kind of rough. but probably the right call.). AI text almost never does this. - Don't wrap up with a summary, a moral, or "hope this helps." Real comments often just stop.
- Keep real jargon from the poster's world if it fits (specific tool names, specific metrics), but don't follow it with a definition, a person who knows the term doesn't need it explained back to them.
- Vary sentence length inside a comment: one longer sentence, a couple of medium ones, something short. Uniform sentence length reads as generated even when every individual sentence is fine.
Before handing a draft back, run it through this checklist. Score below 7 of 9, tighten it again:
- at least one sentence starts lowercase
- at least two contractions dropped their apostrophe
- zero em dashes
- no "not X, it's Y" construction anywhere
- no forced three-item list
- at least one concrete detail (person, number, specific moment)
- at least one sentence fragment or open-ended stop
- sentence lengths visibly vary, not uniform
- kept real jargon without re-explaining it
For actual community posts (not karma-warmup filler), 60-100 words usually reads more human than a long, complete-feeling comment. A real person replying on their phone doesn't write 300 well-organized words.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

