social-reddit · diff
git:20260828.82faea7 to git:20260905.4909a33
156 added, 179 removed. Audit A to A.
---
name: social-reddit
title: "Reddit Publishing Playbook"
- description: "Ground-truth 2026 playbook for posting, commenting, and replying anywhere on Reddit — any topic, from hobbies and health to careers and software. Covers the ranking algorithm, thread target selection by velocity, subreddit-first research, the 90/10 self-promotion rule, title craft, post body structure by sub type, comment strategy that earns trust without pitching, thread-vibe matching, the named AI-tell tic list, and the response protocol for being accused of writing with an LLM. Activate whenever drafting anything destined for Reddit."
+ description: "Draft and revise Reddit posts, comments, AMAs, and product launches in the author's documented voice. Use when preparing content for a subreddit: check community rules, choose a native format, ground claims in supplied proof, disclose affiliations and AI use, and plan useful replies and outcome measurement."
license: Apache-2.0
- compatibility: "Octomind content agents. Platform-specific to Reddit."
+ compatibility: "Requires network access to current Reddit rules and post pages; some research requires an authenticated session."
domains: content
rules:
- content(reddit)
- content(subreddit)
- content(upvote)
- content(upvotes)
- content(karma)
- match(\br/[a-zA-Z0-9_]+)
- match(\bpost\s+(on|to|for)\s+(reddit|r/))
- match(\bask\s?me\s?anything\b|\bAMA\b)
---
## Overview
- Reddit is thousands of subreddits — hobbies, health, finance, careers, fandoms, local cities, trades, software — each with its own rules, culture, and moderators. Everything here applies whatever the topic: the ranking mechanics, the 90/10 rule on posting about your own thing, the per-community research loop, and the 2026 anti-detection layer (AI-content automods now run on most large subs and silently remove LLM-shaped text). Where an example is technical, it is an example, not a scope limit — the same rule holds in r/cooking, r/personalfinance, or r/AskHistorians.
+ Write a useful contribution for a particular community in a particular person's voice. Apply supplied facts and proof first, the author's documented voice next, and platform register as the fallback; community rules remain a publication gate. Use `content-voice` for general editing and this skill for Reddit decisions.
- Pair with `content-voice` for the general human-voice ruleset. This skill adds the Reddit-specific layer.
+ ## Mental model
- For more examples beyond the 3 in this file, see `reference/examples.md`.
+ Separate visibility from permission and qualified interest. Downvotes reduce visibility; moderators enforce community rules alongside sitewide defenses (official, Reddit Safety, 2026-07). Don't use archived Hot or Best formulas, fixed ranking weights, or comment-entry cutoffs to predict distribution.
- ## Instructions
+ The Home-feed X experiment hides an item and signals less similar content for a limited global subset (official, Reddit Changelog, 2026-08). Keep each angle relevant; don't treat a personalized Home sample as a community-wide leaderboard (directional).
- ### The 2026 Ranking Algorithm
+ Treat editorial advice marked (directional) as craft judgment, never a detection bypass or performance promise.
- Reddit ranks posts and comments with different math. Both penalize corporate behaviour and reward early, organic engagement.
+ ## Community and format decisions
- Post ranking (Hot sort) is roughly `log(upvotes - downvotes) × time_decay`. The log means the first ten upvotes matter far more than going from 90 to 100, and decay halves visibility every few hours. What moves it: vote velocity in the first one to two hours (50 upvotes in an hour outranks 200 spread over six), upvote ratio (below ~70% the post is buried), comment count and depth, account trust (new or low-karma accounts get throttled invisibly), and the sub's own activity baseline. Peak visibility lands four to eight hours in; a twelve-hour-old post needs roughly ten times the upvotes of a one-hour-old one. Discussion outranks applause — 50 comments of back-and-forth beat 200 upvotes and silence, so give people something to argue with.
+ Read the target's current rules, sidebar, pinned threads, and recent comparable posts before drafting. Record rule URLs and access date, allowed format/flair, promotional placement, eligibility, AI restrictions, audience register, and recurring objections. If rules are inaccessible, mark clearance unknown and withhold the publication recommendation.
- Comment ranking (Best sort) uses a Wilson confidence interval, not raw score: 10 up and 1 down ranks above 1 up and 0 down, because more data means more confidence. Early comments compound — the first three substantive comments capture most of the reply karma a post will ever produce.
+ Use modern community pages and their rules links. Direct community rules JSON was verified for r/rust and r/mcp; it isn't a guaranteed logged-out interface (official, Community Rules, checked 2026-09). Old Reddit requires login during the announced transition; new public API requests are being restricted gradually (official, Reddit Infrastructure, 2026-08).
- ### The 90/10 Rule (non-negotiable)
+ Promotion isn't inherently spam. Some communities prohibit it; others set their own promotional share guideline (official, Reddit Spam Guidance, 2026-03). Resolve local requirements instead of counting toward a universal quota.
- At least 90% of activity must be non-promotional. The other 10% can be yours. Break this and posts get shadow-removed, the site-wide spam filter kicks in, or the account gets suspended.
+ Build a roster by angle, with permission verified separately for every actual subreddit (directional):
- Non-promotional in practice: answering questions without self-linking, commenting on others' posts, sharing other people's articles/tools, posting unrelated discussion starters. Burner and bought-karma accounts get detected — the only path is genuine membership in the communities you post in.
+ | Audience situation | Candidate venue | Contribution and clearance question |
+ |---|---|---|
+ | Practitioner evaluating a workflow | Relevant specialist community | Reproducible artifact; check source and promotion rules |
+ | Buyer comparing alternatives | Existing question in the buyer's niche | Answer the stated constraints; disclose your stake |
+ | Maker showing a finished object | Relevant showcase community or designated thread | Show the object and a real limitation; check media/flair |
+ | Local customer planning a job | Relevant city or trade community | Explain local scope; check commercial-post placement |
+ | Existing users needing support | Product's owned community | Answer unresolved problems and publish useful documentation |
- ### Subreddit-First Research (always before posting)
+ Choose qualitative length bands from the surrounding posts, not a platform-wide word target (directional):
- Every subreddit has its own culture — the same post lands very differently in r/AskHistorians than in r/CasualConversation. Minimum 10 minutes per target sub:
+ | Community/task | Format | Post length band and anatomy | Comment length band |
+ |---|---|---|---|
+ | Expertise or technical discussion | Text; link if the source is the subject | Developed explanation with evidence and conditions | Developed answer if needed to evaluate evidence |
+ | Showcase or craft | Image/gallery or demo video where enabled | Compact caption explaining the artifact | Brief observation or compact process answer |
+ | Help or buying question | Text or existing question thread | Compact account of attempts and unresolved constraints | Compact answer; expand for a necessary procedure |
+ | Experience or local service story | Text with permissioned evidence | Developed account of the decision and consequences | Compact response to the particular experience |
+ | Casual chat | Text or enabled media reply | Brief observation | Brief conversational reply |
+ | Existing relevant submission | Repost, formerly crosspost | Short destination-specific context | Match the destination's discussion depth |
- 1. Read the sidebar and rules. Many subs ban self-promotion outright, require flair or minimum account age, or mandate formatting. Violating any = auto-removal, often with a ban.
- 2. Check the last 20 posts. What titles are getting upvotes? What's the vibe — technical, casual, sarcastic, earnest? Match the register.
- 3. Check the pinned posts and weekly threads. Many subs have a "Self-Promotion Saturday" or "Showcase Sunday" thread. Your post belongs there, not as a standalone submission.
- 4. Scan the top comments on similar posts. What do they push back on? Pre-empt it in your post.
+ Reposts preserve the original username, community, and score in the preview; destinations must allow reposting (official, Reddit Reposting, 2026-07). No permission follows from the original post's success.
- Output before writing:
- - Subreddit: r/_______
- - Rule-compliant? (account age, karma, flair): _______
- - Tone: (technical / casual / sarcastic / earnest): _______
- - Recent upvoted titles — pattern noticed: _______
- - Common criticism in comments on similar posts: _______
- - Designated self-promo thread if any: _______
+ Title decisions (directional):
- ### Target Selection (this dominates comment craft)
+ | Subject | Lead with | Remove |
+ |---|---|---|
+ | Result | Supported outcome and the condition that bounds it | Unsupported magnitude or causal certainty |
+ | Artifact | What readers can inspect | Brand slogan and empty launch excitement |
+ | Question | Exact unresolved problem | Vague help request or rhetorical opener |
+ | Decision | Concrete choice and cost | Forced contrast or tidy life lesson |
- Measured across an 11-comment sample on one account: comment score tracked the host thread's score almost monotonically. A sharp 466-character comment scored 1 because its thread was quiet; a comparable one scored 18 in a busy thread. A great comment in front of nobody is worth exactly one point. This is an impressions problem wearing a quality problem's clothes.
+ Check the actual composer and local title rules. Front-load useful information; don't impose an unsupported character cap. Name the product when relevant and permitted, and identify ownership early in promotional content.
- The leading indicator is velocity at entry, not absolute score. Compute `num_comments / age_hours` before you write. Above ~5/hour is worth entering; under ~3/hour usually is not, however good the topic fit. Early entry alone is not enough — the 18-scorer went in at 1.8h into a thread doing 8.5 comments/hour, while 5h entries into slow threads all scored 1.
+ ## Launch and proof posts
- Room vetoes override velocity entirely. Skip regardless of how fast the thread is moving when:
- - top comments are all mockery of OP — the room has already decided, and a substantive answer reads as missing the joke
- - anyone has accused OP of AI-generating the post, or mocked a specific style (all-lowercase, tidy structure) as the giveaway
- - the highest-scoring replies are anti-hype, anti-vendor or anti-bot — a measured stranger with a link reads as astroturf in that crowd
- - the topic is one the sub treats as inherently suspect (get-rich schemes, miracle cures, crypto, anything mixing money with autonomy) — a technical point reads as promotion no matter how it's phrased
+ Obtain the audience and buying situation, promise, proof with sources, desired action, destination, campaign stage, and disclosure obligations before drafting. Stages include teaser, launch day, proof, objection, and recap. Record the author's role and voice samples. No CTA is a valid deliberate choice. If proof is missing, deliver a clearly nonpublishable draft with evidence placeholders inside the draft only.
- Velocity picks the candidates. The room decides whether you write at all.
+ Post shapes and qualitative length bands are craft choices (directional):
- Slow threads are still worth answering, just not for score. Comments keep working for months with no further effort: a 55-day-old comment produced the best outcome of its week, and late replies that reliably score 1 generate the best ongoing relationships. Judge those on what they change, not on karma.
+ | Shape | Native anatomy | Length band |
+ |---|---|---|
+ | Launch day | Ownership, buying problem, inspectable result, limitation, permitted action | Compact announcement with supporting context |
+ | Demo/artifact | Visible task, actual input/output, operating conditions, access path | Brief caption; extend only to explain proof |
+ | Customer outcome | Permissioned before/after, source and measurement window, other changes, unresolved limitation | Developed evidence account |
+ | Founder decision | Decision, rejected option, actual cost, current uncertainty | Compact operator account |
+ | Objection answer | Fair statement of objection, evidence relevant to it, unsuitable cases | Brief answer or developed technical explanation |
+ | Recap | What changed, what failed, unresolved question, source-specific outcomes | Developed retrospective without repeated launch copy |
- ### Title Craft
+ Apply the strip-test: after removing the product mention, the post should still teach or show something useful. A permitted announcement can identify its product openly; don't disguise a sales pitch as an unrelated question. Keep proof legible, preserve meaningful precision, redact private information, and obtain permission for customer quotes or screenshots (directional).
- Reddit titles are the entire package for most users — most scroll the feed without expanding. Rules:
+ ### Links, identity, and seeding
- - State the thing. "My experience migrating 200k LOC from Python to Go" beats "A journey of migration."
- - No clickbait. "You won't believe what happened when..." = downvote reflex. Reddit trained itself off this years ago.
- - No "How to X in Y steps." Reddit users have seen 10,000 of these. They read as SEO spam.
- - No emoji. None. Not even a single rocket.
- - Specific over vague. Numbers, names, places, time windows. "Six months of tracking every grocery receipt: what actually cut the bill" beats "Lessons learned about saving money."
- - No ALL CAPS words except proper acronyms (API, LLM). Caps read as ad copy.
- - Keep it under ~80 characters. Long titles truncate on mobile. The hook has to land early.
- - Don't put a brand, product, or shop name in the title unless the sub explicitly allows it (e.g. r/SideProject). "I built a CLI for X" or "I refinished a 1940s desk" is fine; "[MyBrand]: the best X" gets removed.
+ Put a relevant destination in the root post where permitted. Use the designated promotional thread when required. In comments, link when it directly answers the question and local rules permit; don't hide a prohibited pitch in a reply or profile detour. Prefer a direct inspectable destination (directional). Repetitive promotion and unsolicited mass outreach violate spam policy (official, Reddit Spam, 2026-05).
- ### Post Body Structure (by subreddit type)
+ Disclose ownership, employment, sponsorship, gifted products, or affiliate benefit beside the recommendation as applicable (directional). AI-generated or modified content must follow community rules and carry a tag or other disclosure; presenting generated content as human-generated is prohibited (official, Reddit Manipulated Content, 2026-05). Human review doesn't create an exemption. For automation, disclose the automated nature and check Responsible Builder requirements before enabling posting; editing for natural voice must never conceal automation.
- Subs cluster into a handful of shapes regardless of topic. Match the shape, not the subject matter.
+ Use a disclosed founder account for personal decisions and an identifiable brand account for official support (directional). Eligible Reddit Pro organizations can seek verification; individual verification remains an alpha test, and verification doesn't override community rules (official, Reddit Verified Profiles, 2026-07).
- Expertise and discussion subs (r/AskHistorians, r/programming, r/personalfinance, r/medicine): open with the specific thing, no preamble. Bring the artifact — the numbers, the source, the code, the photo, the receipt. Text-only assertions underperform evidence. Name exact figures, dates, editions, versions. End with a pointed question, not "thoughts?". Markdown belongs in posts, never in comments.
+ Participate where you have relevant contributions. Don't manufacture independent praise, coordinate votes, buy accounts, or seed repetitive employee comments; Reddit's defenses address spam and inauthentic voting (official, Reddit Safety, 2026-07). Employees should disclose their roles and contribute only relevant expertise (directional). Product Hunt's sharing guide recommends existing community participation and prohibits upvote requests or rewards for its launches (official, Product Hunt Sharing, checked 2026-09).
- Show-and-tell subs (r/SideProject, r/woodworking, r/gardening, r/mycology): say it's yours in the first line. Share what you learned rather than what you want from the reader. Include photos. One link at most, in-body, not repeated. Name a real limitation — "the joint on the left is out by 2mm", "search is slow past 10k records", "the yield was half what I expected". Uniformly positive descriptions read as marketing or LLM output.
+ For an owned subreddit, seed useful original discussion and mix in relevant reposts. Contact destination moderators before substantial outbound reposting; don't increase it when it brings no member-growth response (official, Reddit Community Seeding, 2026-05).
- Question subs (r/AskDocs, r/legaladvice, r/learnprogramming, r/cooking): the title is the question, specific and not "help pls". The body carries what you tried, what happened, what you expected, plus whatever context the sub's rules require (age/location/equipment). Never post something 30 seconds of searching would answer.
+ ### Launch-week rhythm
- Story and experience subs (r/cscareerquestions, r/relationships, r/TalesFromTechSupport, city subs): first paragraph sets who you are, the timeframe and the stakes; the middle carries specifics; the end leaves the lesson for the reader to draw.
+ Illustrative planning offsets, not measured timing optima; skip slots that lack new evidence or local permission. T denotes launch day.
- Community and hobby chat subs (fandoms, city subs, r/CasualConversation): low-stakes, high-frequency, short. These are where a real account is built — the history that keeps a later post out of the spam filter.
+ | Offset (illustrative schedule) | Work or post shape | Reply plan | Qualified-interest evidence |
+ |---|---|---|---|
+ | T-7 to T-3 | Research buyer questions; prepare demo and permission requests | Resolve scope with moderators when needed | Relevant unanswered questions; community clearance |
+ | T-2 to T-1 | Rehearse the promise; optional permitted teaser with useful artifact | Assign technical and product/support owners | Specific evaluation requests |
+ | T | Publish approved launch or demo | Cover the first hours; answer substantive questions and log objections | Relevant replies, requests to try, stated buying constraints |
+ | T+1 to T+3 | Correct the original; answer objections in context | Follow actual conversations; don't mass-message commenters | Continued evaluation; obstacles resolved or still open |
+ | T+4 to T+7 | Publish new proof or recap only if warranted | Return with evidence to unresolved questions | Repeat participation; attributed activation where available |
- ### Thread-Vibe Matching (read before you write)
+ Use Reddit Pro post views, upvote ratio, comments and shares, plus available comment views/replies and account reach/followers. Hourly post views cover the first 48 hours and remain available for 45 days (official, Reddit Pro Performance, 2026-04). Export supported fields; don't assume every visible metric is in CSV. Awards are contextual: Reddit announced expanded free-award availability, so award changes alone don't establish stronger demand (official, Reddit Changelog, 2026-08).
- Scanning the thread before replying is the single most effective anti-detection move — it makes output structurally match community behaviour in that moment.
+ Keep Reddit-native engagement separate from destination visits, activation, retention, and revenue. Record attribution uncertainty (directional). Open `reference/examples.md` when building a launch measurement package, evaluating commerce or paid follow-through, or adapting proof to a new niche.
- What to read:
- - Top 5–8 comments (or all if small)
- - OP's writing style — length, punctuation, caps, casualness
- - Dominant reply length — 2-line zingers or 6-paragraph essays?
- - Emotional register — sarcastic, earnest, technical, venting?
- - Recurring phrases, in-jokes, sub-specific slang
+ ### AMAs
- What to extract before writing:
+ Arrange moderator pre-approval and the accepted proof method before announcing an AMA. Prepare a proof photo or official identity link when requested; share only necessary identity information. Agree on topic boundaries, flair, start/end time with timezone, and answer ownership. State who is answering and disclose commercial interests (directional).
- | Signal | What to match |
- |--------|--------------|
- | Median comment length | Stay within ±30% of it |
- | Punctuation style | If nobody uses periods at end of short comments, don't |
- | Capitalization | If thread is mostly lowercase, go lowercase |
- | Emoji usage | If zero emoji in thread, use zero |
- | Markdown | If nobody uses bold/bullets, don't |
- | Tone | Match the dominant register (sarcastic, earnest, technical, casual) |
+ Answer substantive questions throughout the announced window, including difficult ones; acknowledge unknowns and return with verified answers. Mark the session closed and state any real follow-up commitment. Video comments are available where moderators enable them in eligible public SFW communities and don't autoplay; pair any video answer with useful text (official, Reddit Video Comments, 2026-06; text accompaniment: directional). Check enabled media and upload constraints in the composer; don't invent duration limits.
- Hard rule: if the thread is full of 1–3 line replies, your 8-line structured comment will stand out as AI-generated even if every word is perfect. Short thread = short reply. Long thread = you have room to breathe.
+ ## Voice on this platform
- ### Human Imperfection Protocol (replies and comments)
+ Keep the author's natural conversational register. Use surrounding comments to calibrate depth and formality, without adopting hostile behavior or slang the author doesn't use. Don't add typos, fake edits, dropped articles, or lowercase camouflage. Open `reference/imperfections.md` when calibrating register, local idiom, or a sensitive reply; it contains register decisions rather than error injection.
- Posts get proofread; replies are typed fast on a phone. Pick one or two imperfections per reply, never a whole set: a realistic typo, a missing apostrophe, a run-on joined with "and", a sentence starting with "But", a lowercase `i` mid-sentence, one sentence much shorter than the others. Not in the first word, not in a technical term or username or number, never twice the same way, never in a post title.
+ Answer the question asked. If the author lacks firsthand experience, attribute the source instead of inventing an anecdote. Name concrete tradeoffs when supported. Preserve material uncertainty without a hedge on every sentence (directional).
- Don't lowercase every sentence start as camouflage. It has been named publicly as a tell, and it backfires for a specific reason: casual casing sitting on top of immaculate punctuation and three balanced paragraphs is a costume, and the seam is what readers notice. Capitalise and punctuate normally, and put the sloppiness in the content instead — a digression, a thought that trails off, one real typo left in, an answer that covers one thing and ignores the rest of the post. Matching a genuinely all-lowercase thread is a different decision from adopting lowercase as a house style.
+ Default to prose in comments. Use formatting when it carries actual evidence or an expressly requested enumeration; a factual list may contain as many items as needed. Remove padded triads, not legitimate lists. Detailed posts can use useful headings, code, and tables (directional).
- Full typo list, grammar patterns and the per-content-type calibration table: `reference/imperfections.md`.
+ Open `reference/ai-tells.md` during the editorial pass for the scoped pattern checklist and evidence limits. Its purpose is better communication. No punctuation choice or prose cleanup proves authorship or promises avoidance of accusations.
- ### Comment Strategy
+ ## Cadence and engagement
- Comments are where most karma comes from, and where mods decide whether your account is a real member or a promo bot.
+ Choose timing from recent target-community observations and author availability; no universal ET window or weekend exclusion is supported here (directional).
- - Answer the question asked. Don't steer the conversation to your topic.
- - Top-comment early or don't bother. After the first 3 substantive comments, you're buried unless your comment is exceptional.
- - Specific beats general. "I ran the same sourdough at 72% and 80% hydration in the same oven and the 80% one spread" beats "hydration matters." The specific version works identically for a recipe, a symptom, a tax rule, or a database.
- - Don't link in comments unless asked — and when asked, link once, no UTM parameters, no tracking.
- - Agree with the top comment? Don't just say 'this' — add the next layer. Extension > echo.
- - Disagree? Cite the specific claim you disagree with. "Disagree on point 2 — here's why" beats a general "no."
- - Never start with "as someone who has worked in X…" unless you actually have. Reddit detects credentialing theatre instantly, and fabricated specifics are worse than vague ones — a fake-precise claim ("I ran this at a 10k-employee bank", "my cardiologist said") attracts replies asking which one, and the silence that follows is what mods and classifier bots escalate on. If you don't have the experience, write from what you've read or seen and say so.
- - Include a real drawback whenever you recommend something you have a stake in, or are simply enthusiastic about. Bots and marketing copy are uniformly positive. Real recommendations name a concrete trade-off — "the mobile app is weak", "the tool dulls fast on hardwood", "onboarding took me a week". Vague hedges ("not for everyone") don't count; it has to be concrete enough to verify or argue with.
- - Edit-to-add is fine and human. "Edit: to clarify…" reads normal. Silent edits on controversial comments read sketchy.
+ | Thread situation | Response decision (directional) |
+ |---|---|
+ | Relevant unanswered problem | Add the missing answer, even in a quiet or older thread |
+ | Active conversation with room for expertise | Address a specific point; don't echo the leading reply |
+ | Your product conflicts with the reader's constraints | Say so and recommend a suitable route if known |
+ | Someone else's showcase or persistent pile-on | Don't hijack it; disengage if you can't contribute constructively |
+ | Evidence contradicts your earlier advice | Correct the claim openly and state the changed implication |
- ### What Actually Converts (measured)
+ Reserve time for useful early replies and later follow-up. Admit ignorance when appropriate; when someone acts on advice, help with the next real obstacle. Don't infer a ranking multiplier from reply activity (directional).
- Measured over ~60 comments in one campaign, where the goal was influence rather than karma. The mechanism is generic: it applies to changing someone's mind about a recipe, a diagnosis to ask their doctor about, a legal step, or a piece of software.
+ For an AI accusation, choose by substance rather than escalation order (directional):
- - Refusing to pitch outperforms pitching. Telling someone the thing you're invested in is the wrong fit for their situation, and pointing at the better option, produced follow-ups that a pitch never did. The single best-scoring comment of the run said don't use our thing for this.
- - Admitting ignorance reopens dead threads. "I don't have an answer for that case" brought a stranger back days later with the answer; nothing else revived a dead thread all run.
- - Concede in the first sentence, then add something new. Both times a claim was refuted with evidence, the reply opened with "fair, I was wrong" — that is what bought the next round.
- - When someone says they took your advice, reply with the next problem it creates, not congratulation. That is what turns a thank-you into a real exchange.
- - Object to a conclusion someone reached because of your earlier argument. Agreeing with people who agree with you is where exchanges die.
- - Engage what someone is about to do, not what they already finished. Advice is still cheap to act on there.
- - Critique that argues in the other person's favour — their result is stronger, or their evidence weaker, than they thought — is the most reusable move available.
- - Read the existing comments first. Twice the obvious point had already been made, and going elsewhere in the thread is what made the comment land.
+ | Trigger | Response |
+ |---|---|
+ | Factual error identified | Correct it and provide the source |
+ | Genuine authorship or automation question | State the actual assistance used and correct missing disclosure |
+ | Unsupported insult with no question | Leave it unanswered; don't debate detector scores |
+ | Rule violation or abusive exchange | Stop; resolve the moderation issue without evasive reposting |
- When not to bring up your own thing at all: in someone else's disclosed showcase thread (hijacking it is banned, and staying out of it produced two of the wins), with a person you already mentioned it to today, with someone whose constraints rule it out (privacy, cost, they built their own), in a competitor's own sub, or across multiple posts by the same person. Recommendation threads look like the safest slot and are a trap for argument-led accounts: the reward function there is give me the name, top comments are bare names and bare links, and a three-paragraph critique with a self-link lands at -1. Post one line and a link, or skip.
+ Open `reference/imperfections.md` for worked response choices.
- Disclosed links do not suppress score (measured, n=11: the top-scoring comment carried one). The reason to skip a link is argument coherence, not imagined safety.
+ ## What gets suppressed
- ### Surviving AI Detection on Reddit (the 2026 reality)
+ Check eligibility messages: communities can gate on account age, total/subreddit karma, verified email, and approved-contributor status; thresholds are hidden. Post Check uses an LLM to flag likely rule violations but doesn't itself block submission (official, Reddit Eligibility, 2026-08).
- Most large subs run two filters: automod regex/keyword rules and classifier bots trained on LLM samples. The signature that gets caught is the cumulative shape, not one phrase.
+ AutoModerator can enforce configured domain, keyword, pattern, and affiliate-link checks (official, Reddit AutoModerator, 2026-08). Rules Hub uses LLMs to interpret rule intent under moderator control and remains in rollout (official, Reddit Infrastructure, 2026-08). Follow the meaning of rules; don't claim ubiquitous AI-text classifiers or universal phrase penalties.
- Structural tells detectors look for:
+ Repeated mass posting, rapid old-content reposting for karma, and continuously promotional bots are prohibited (official, Reddit Spam, 2026-05). If a post disappears, inspect its state and moderation messages; record the reason as unknown unless explicitly supplied. Don't diagnose removal from a logged-out view or low score alone (directional).
- 1. Tri-colon listing — "X, Y, and Z" parallels stacked across paragraphs. Humans write uneven lists: pairs, fours, single items, run-ons.
- 2. Symmetrical paragraph length. Real Redditors put a one-line zinger next to a four-line rant next to a fragment.
- 3. The "It's not X, it's Y" reframe used cleanly. The corporate version ("it's not just about features, it's about experience") is dead on arrival.
- 4. Three or more bullets in a comment, unless the question asked for a list. Native Reddit comments are prose even when listing things.
- 5. Markdown headers in a comment. Almost nobody does this; mods flag them on sight.
- 6. Bold inside flowing prose.
- 7. A closing tl;dr line restating the comment. Most people just stop, or end on a question.
- 8. Zero typos, zero contractions, zero slang. "gonna", "tbh", "kinda", missed apostrophes and the odd run-on are camouflage.
- 9. Em-dashes everywhere. One is fine; three in a paragraph is a signature. Mix in parentheses, commas, full stops.
- 10. A hedge on every claim: "it's worth noting", "that said", "ultimately", "at the end of the day". One is fine, three is a tell.
+ ## Examples
- Lexical tells, beyond the `content-voice` dead-vocabulary list: ad-copy words ("game-changer", "powerful", "robust", "seamless", "next-level"), vague stakes ("in today's competitive landscape"), empty contrast ("while X is great, Y matters more"), author-as-narrator ("let's dive in", "here's the thing"), conclusion telegraphs ("in conclusion", "the bottom line"), and "the real question/moat/problem" used without a personal anchor.
+ These fictional source briefs and drafts illustrate craft, not real testimonials or publishable claims. The stated outcomes belong only to these examples. For actual work, replace them with the author's evidence and add disclosure appropriate to the production process.
- Named tics, submission-format tells, and the register-mismatch rule live in `reference/ai-tells.md` — load it when drafting. The headline offenders: never open a sentence with "worth", never write "it's not X, it's Y", never post a three-item list, never estimate a stranger's effort, and never use the same closing disclosure twice.
+ ### Developer tool: artifact post
- Tactics that pass detectors:
+ Illustrative brief: a maintainer writes terse debugging notes; a saved trace shows a dry-run reporting error. The fix remains untested on remote storage.
- 1. Anchor with a specific lived detail in the first sentence or two — "ran into this last week on a Postgres 14 cluster", "my grandmother did it with a cast iron pan and no thermometer". A verifiable autobiographical claim lowers detector weight.
- 2. Reference another commenter by username and quote a fragment of their wording. Bots almost never do either, and it proves you read the thread.
- 3. Use exactly one casual reduction per comment (imo, tbh, fwiw, iirc, a missing apostrophe, a fragment). Several at once reads as trying too hard.
- 4. Vary sentence length hard. Three words. Then one that runs much longer because you're explaining something. Short.
- 5. Drop the closing summary and the closing recommendation. End on the example or the question.
- 6. Write the comment, then delete the first sentence — AI-trained openers live there — and skip headers and bullets unless the question demands them.
- 7. Disagree with part of what you're replying to. Pure agreement reads sycophantic; a small specific pushback reads as a thinking person.
- 8. Run it through the "would I type this on my phone at 11pm" filter, and cut if the answer is no.
- 9. Pre-empt the sub's known controversy by naming it up front. The camp that disagrees stops brigading once it sees you already heard the argument.
+ > Title: Our dry-run report skipped filenames containing tabs
+ >
+ > I maintain the tool. The files were present in the scan, but our report parser dropped those rows. The attached trace shows the point where they disappeared. The patched report includes them on local storage; remote storage is still untested. Reproducer: [source link].
- Per-sub calibration: AI suspicion varies by venue. Anywhere money, career advice, health, or software gets discussed runs hot — r/SaaS, r/startups, r/personalfinance, r/AskDocs, r/programming, r/cscareerquestions. Art, writing, and craft subs run hottest of all, since generated work is an existential topic there. Hobby, local, and casual subs run mid. Default to high-suspicion behaviour everywhere and relax only after reading recent successful posts.
+ Why it works: ownership is visible and the artifact supports the claim.
+ The limitation follows the proof rule without inventing a success story.
- Detectors read the account, not just the text. A new account whose first comment is a marketing-flavoured reply in a high-suspicion sub gets removed however human the prose is. Build history in low-stakes places first — hobby subs, your city sub, r/AskReddit — before entering venues that matter to you.
+ ### B2B SaaS: objection reply
- ### When You Get Called AI
+ Illustrative brief: an operations founder uses plain, candid replies; their product pilot still required manual weekend refunds.
- Accusations are near-certain over time. Treat them as weather, not verdicts. Across ten flags on one account, three consecutive flagged comments were net-positive, and one was the best-scoring comment of its week. The audience is split: a minority detects the shape, the majority engages with the substance. Never retreat from a sub over one flag, and never rewrite your whole voice after one.
+ > Keep your current refund workflow for now. I work on the product you're considering, and our pilot team still entered weekend refunds by hand. Your unattended-weekend requirement rules us out. The current limitation is documented at [source].
- Response ladder — take the highest rung available:
- 1. Post a substantive self-correction elsewhere in the thread if someone has supplied a fact that falsifies part of your comment. Conceding an error is the one thing an accusation cannot survive.
- 2. One short self-deprecating line at the accuser. No denial, no claim of humanity, no explanation of your writing process: "ha, fair. i write like a changelog and it doesnt help me here."
- 3. Silence. Correct when every available line either denies something untrue or concedes something that invites more.
- 4. Delete and disengage — only on a mass downvote with a pile-on.
+ Why it works: it answers the buyer's situation without steering into a pitch.
+ The source and unsuitable case apply the comment decision table.
- Hard rules:
- - Never argue, defend, relativise or joke about AI authorship, anywhere, at any length. Standing on that topic turns every reader into an inspector of your prose. Skip those threads entirely.
- - Never acknowledge a compliment about not sounding like an LLM. Answer the question and ignore the aside; responding is the most self-incriminating move available.
- - Treat "Thanks, Claude" as a fixed idiom, like "ok boomer". Three different users in three subs used it in 30 hours. It carries no information about your comment.
- - Two accusations in one day stops all cold entries for the rest of that day. Replies to people you are already in conversation with continue.
- - Prose tuning has never lowered the rate. Length caps, tic lists, sub rotation and register matching each preceded another flag; one flag landed on a twelve-word sloppy reply and another on a three-day-old comment. Control what you can: which threads you enter, and whether you discuss AI authorship.
+ ### Consumer maker: proof caption
- Before a cold entry in an unfamiliar sub, read `/about/rules.json` and search it for `slop`, `AI generated`, `LLM`, `bot`. r/rust rule 6 bans "slop, whether automatically generated or not"; r/mcp bans AI-generated content on pain of a ban; many art and writing subs go further. A sub that pre-committed in writing to policing generated text is one to enter short, link-free, or not at all. A rule is a standing property of the venue; thread mood is read per-thread and can change under you. Check both.
+ Illustrative brief: a bag maker uses tactile descriptions; ride photos show a repaired seam and persistent strap rubbing.
- Cold entries draw most accusations. Replies inside an existing exchange draw far fewer, because the reader already has context and expects a considered answer — the same prose in a different frame gets the opposite reception. In high-suspicion venues, prefer replies.
+ > Title: The bag held at the seam, but the strap still rubs
+ >
+ > This is the bag I sew for my shop. You can see the pale scuff beside the buckle in the close-up. The repaired seam held during the loaded ride; the strap rubbing hasn't improved. I'm leaving that photo in the listing so buyers can see where it wears.
- ### What Gets Auto-Removed (before anyone sees it)
+ Why it works: the caption connects visible wear to the documented use.
+ The bounded outcome follows the proof rule; no CTA is needed here.
- Account-level triggers: a new account (under a week) or under ~50 karma, activity in only one sub, a comment-only history that suddenly posts a self-link, or the same domain posted in another sub recently.
+ ### Local service: experience post
- Content-level triggers: a domain the sub has flagged (often your own, if posted before), sub-specific banned words, link shorteners, affiliate or UTM parameters, and known promo phrasing ("check out my new", "just launched", "I'd love your feedback on", "I'm excited to share").
+ Illustrative brief: a tailor writes practical job notes; the customer approved a pocket repair while leaving worn lining in place and permitted the photos.
- AI-content triggers are the structural and lexical tells above — automod and classifier bots score the same list.
+ > Title: Keeping the worn lining during a pocket repair
+ >
+ > I run the alterations shop that did this repair. The pocket is usable again. The customer wanted to keep the lining, so the fraying you can see in the photo is still there; replacing it would be a separate job. Photos shared with permission.
- If your post disappears within minutes: check modmail, and open the post URL in a logged-out browser session — if it shows as removed there, mods took it down.
+ Why it works: affiliation and job scope are explicit.
+ The remaining issue prevents a misleading before/after promise.
- ### Cross-Posting, Timing, and the First Hour
+ ## Checklist
- Cross-posting to five or more subs in a day trips the spam filter; space them over days and rewrite the title and body each time. Never post the same link to several subs at once — dedup buries the duplicates even if the first one did well. Reposting your own content a month later with a different title is fine in most subs.
+ For every draft:
- The first hour after posting is part of the post; a silent OP on a commented thread is a known classifier signal. Answer the first two or three comments within the hour, even briefly. Edit in corrections when someone catches something ("edit: u/foo pointed out X, fixed"). Concede where you're wrong instead of defending every point. If you can't be around for that hour, don't post yet.
+ - [ ] Hook/first line states the subject; the contribution has a single main idea.
+ - [ ] Current rules, eligibility, format, and flair checked; unknown clearance blocks recommendation.
+ - [ ] Link and CTA path fit the venue; no CTA is recorded when deliberate.
+ - [ ] Every specific has supplied provenance or a draft-only placeholder; incomplete drafts aren't publishable.
+ - [ ] AI-tell pass completed; author voice preserved; required affiliation and AI disclosures included.
- Timing for English subs, which skew US: weekdays 8–11am and 6–9pm ET, with Sunday evening the strongest window for discussion posts. Avoid Friday afternoon and Saturday. Niche subs run on their own rhythm — check theirs.
+ For posts:
- ### Pre-Publish Checklist
+ - [ ] Proof and strip-test checked; package includes title/body, caption, asset brief, accessible image description or alt text where supported, and video transcript/captions as needed.
+ - [ ] Reply owner and availability recorded; follow-up and measurement plan fit the goal.
- - [ ] Subreddit rules read in full, not skimmed
- - [ ] Account meets karma/age requirements for the sub
- - [ ] Title is specific, no clickbait, no emoji, under ~80 chars
- - [ ] Not using a designated self-promo thread? Make sure standalone posting is allowed
- - [ ] If promotional at all: confirmed it's within the 10% budget, and the post adds real value
- - [ ] Markdown used in the post body only (code fences, lists) and stripped from comments
- - [ ] No tracking parameters or link shorteners
- - [ ] Posted in a peak window for the sub
- - [ ] Ready to respond to the first comment within 30 minutes
- - [ ] Post doesn't sound like marketing if read aloud
- - [ ] Strip-test (anything you have a stake in): remove the mention of your own thing — is the post still useful to a reader? If not, it's marketing wearing humble clothes; rewrite around the actual lesson or don't post
- - [ ] Honest-drawback check (recommendations, showcases): at least one specific, concrete trade-off named, not a vague hedge
- - [ ] Engagement window: can be at the keyboard for the next hour to reply to first 2–3 comments — if not, postpone
- - [ ] Thread-vibe check (replies/comments): scanned the thread, matched dominant length and tone, no markdown if nobody else uses it
- - [ ] Imperfection check (replies/comments): 1–2 realistic imperfections present — typo, missing apostrophe, run-on, or casual grammar — not in the first word, not in a proper noun or number
- - [ ] AI-detection pass: opens with a specific lived detail, no headers in comments, no bold in prose, under 1 em-dash per 100 words, at least one contraction, no closing summary, no dead vocabulary, no tri-colon parallel structure, no "it's worth noting" / "that said" openers
- - [ ] High-suspicion sub (money, health, careers, software, art/writing)? Comment quotes another commenter or references a username, includes one casual reduction (imo/tbh/fwiw), and varies sentence length deliberately
- - [ ] Target check (comments): `num_comments / age_hours` computed and above ~3, no room veto present (mockery pile-on, AI accusation against OP, anti-hype top comments)
- - [ ] Sub rules checked for anti-AI-content language before any cold entry in an unfamiliar sub
- - [ ] Tic scan: no "worth X-ing" opener, no three-item list, no "it's not X, it's Y", no effort estimate, no identical closing disclosure, not three discrete paragraphs in a row
- - [ ] If replying to an accusation: taking the highest rung of the ladder, never denying, never discussing AI authorship
+ For comments:
- ## Examples
+ - [ ] Read the reply chain; answer an unresolved point at suitable depth without hijacking it.
- The worked examples live in `reference/examples.md`: title craft, a comment that earns trust, a draft rewritten to shed every detector tell, self-promotion that survives the filter, ask posts, automod removals, thread-vibe matching, and calibrated imperfections. Load that file when drafting.
+ ## References
- The reusable shape from the surviving examples: personal anchor, then the observation, then a reference to something specific in the thread, then your point, and stop. No closing summary.
+ Dates identify supplied source updates; “checked” identifies undated sources reviewed for this edition.
- ## References
+ - [Reddit Safety](https://redditinc.com/news/how-were-keeping-reddit-real-and-safe-in-the-ai-era), 2026-07-06.
+ - [Reddit Changelog](https://support.reddithelp.com/hc/en-us/articles/52393330268436-Changelog-August-12-2026), 2026-08-12.
+ - [Community Rules: r/rust](https://www.reddit.com/r/rust/about/rules.json), [r/mcp](https://www.reddit.com/r/mcp/about/rules.json), checked 2026-09.
+ - [Reddit Infrastructure](https://redditinc.com/news/modernizing-reddits-infrastructure-and-moderation-tools), 2026-08-05.
+ - [Reddit Spam Guidance](https://support.reddithelp.com/hc/en-us/articles/28012014962580-How-do-I-keep-spam-out-of-my-community), 2026-03-28.
+ - [Reddit Reposting](https://support.reddithelp.com/hc/en-us/articles/4835584113684-What-is-reposting-fka-crossposting), 2026-07-13.
+ - [Reddit Spam](https://support.reddithelp.com/hc/en-us/articles/360043504051-Spam), 2026-05-19.
+ - [Reddit Manipulated Content](https://support.reddithelp.com/hc/en-us/articles/41180423371156-Manipulated-Content-and-Misleading-Behavior), 2026-05-19.
+ - [Reddit Verified Profiles](https://redditinc.com/news/testing-verified-profiles-on-reddit), 2026-07-09.
+ - [Product Hunt Sharing](https://www.producthunt.com/launch/sharing-your-launch), checked 2026-09.
+ - [Reddit Community Seeding](https://support.reddithelp.com/hc/en-us/articles/15484360497812-Planting-seeds-aka-encouraging-and-maintaining-an-active-community), 2026-05-28.
+ - [Reddit Pro Performance](https://support.reddithelp.com/hc/en-us/articles/47618462633364-Reddit-Pro-Feature-Performance), 2026-04-02.
+ - [Reddit Video Comments](https://redditinc.com/news/a-new-way-to-connect-on-reddit-video-in-comments-is-now-available-for-users), 2026-06-11.
+ - [Reddit Eligibility](https://support.reddithelp.com/hc/en-us/articles/33702751586836-Poster-Eligibility-Guide-Post-Check), 2026-08-10.
+ - [Reddit AutoModerator](https://support.reddithelp.com/hc/en-us/articles/15484574206484-Automoderator), 2026-08-28.
- - AgentSkills spec: https://agentskills.io/specification
- - Reddit content policy: https://www.redditinc.com/policies/content-policy
- - Companion skill: `content-voice` — especially critical for Reddit, which detects corporate tone instantly
- - Validated figures: consolidated from independent 2026 Reddit-algorithm studies; Reddit publishes no ranking source — treat as directional and re-validate. Measured comment figures come from one real account's campaign log; the mechanisms generalise across topics, the exact numbers do not.
+ Re-validate when community rules or disclosure policy change; when feed, composer, API, moderation, or analytics features change; or when inspectable performance research appears.
+
+ Validated: 2026-09