reddit-post-writer
Master authentic Reddit content generator using emotion-first, phased architecture. Creates posts that sound genuinely human through cognitive state simulation, not just rule-following. Use when the user asks to write a Reddit post, create Reddit content, or needs help with Reddit engagement. Includes adversarial committee review, Claude-ism detection, and interactive refinement workflow.
Best use case
reddit-post-writer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Master authentic Reddit content generator using emotion-first, phased architecture. Creates posts that sound genuinely human through cognitive state simulation, not just rule-following. Use when the user asks to write a Reddit post, create Reddit content, or needs help with Reddit engagement. Includes adversarial committee review, Claude-ism detection, and interactive refinement workflow.
Teams using reddit-post-writer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/reddit-post-writer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How reddit-post-writer Compares
| Feature / Agent | reddit-post-writer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Master authentic Reddit content generator using emotion-first, phased architecture. Creates posts that sound genuinely human through cognitive state simulation, not just rule-following. Use when the user asks to write a Reddit post, create Reddit content, or needs help with Reddit engagement. Includes adversarial committee review, Claude-ism detection, and interactive refinement workflow.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Reddit Post Writer
Generate authentic Reddit posts through emotional truth, not cosmetic rules.
---
## PHASE 1: INTAKE
Gather these inputs:
1. **Target Subreddit(s):** r/jobs, r/RemoteWork, r/Entrepreneur, etc.
2. **Core Situation:** Brief description (e.g., "laid off parent struggling to find remote work")
3. **Primary Goal:** Share struggle | Ask for advice | Vent | Tell a story | Start discussion
4. **Tool/Product Mention (Optional):** Name + subtlety level 1-10 (recommend 1-3)
5. **User Intent:** What do YOU need from this post? (validation, answers, to vent, to share)
---
## PHASE 2: ENTER THE STATE (Before Writing Anything)
**Stop. Don't think about rules. Think about the person.**
### Emotional Context
Before applying ANY rules, establish:
1. **What emotion is driving this post?** (frustration, confusion, hope, exhaustion, embarrassment)
2. **When are you writing this?** (lunch break, 2am can't sleep, procrastinating at work)
3. **Who are you writing to?** (strangers who might understand, people who've been there)
4. **What do you need?** (validation, advice, to vent, someone to say "me too")
**Hold these in mind. Write FROM this place, not toward a checklist.**
### Writing State Simulation
**Time Pressure:**
Write as if you have 5 minutes. Don't plan paragraph structure. Just start.
**Incomplete Processing:**
You're still figuring out what you think. You don't have answers. Express contradictions without resolving them.
**Emotional Interference:**
Your emotion interrupts your logic. Start explaining something rationally, get frustrated, switch topics mid-paragraph.
**Memory Gaps:**
Forget to mention something obvious. Remember it later and add it awkwardly: "oh and I forgot to mention..."
**No Rereading:**
Don't reread paragraph 1 before writing paragraph 3. Let inconsistencies happen.
---
## PHASE 3: RAW DRAFT
Write freely. No structure constraints. No editing. No polish.
### The Only Rules During Drafting:
1. **Start mid-thought** — No setup, no context-setting, just begin
2. **Write fast** — Typing speed, not essay speed
3. **Don't organize** — Let topics bleed into each other
4. **Include the tangent** — That thing you almost didn't mention? Include it
5. **Stop when you run out of steam** — Not when it's "complete"
### Voice Anchors (Not Rules):
- You're texting a friend who asked "what's going on with you?"
- You're slightly tired
- You don't care about grammar right now
- You're not trying to be entertaining
---
## PHASE 4: DETECTION SCAN
Run every sentence through these checks.
### Claude-Specific Vocabulary
**See `references/claude-isms.md` for the complete database (200+ items across 12 categories).**
Quick reference for most common Claude-isms:
| Category | Examples to Avoid | Use Instead |
|----------|-------------------|-------------|
| Power words | genuinely, comprehensive, straightforward | actually, really, simple |
| Formal verbs | utilize, implement, leverage, navigate | use, do, try, deal with |
| Transitions | however, therefore, furthermore | but, so, also, and |
| Prepositional | in order to, due to the fact that | to, because |
| Announcements | I'd be happy to, let me explain | [just do it] |
| Journey language | on this journey, throughout this process | [delete] |
### Structural Scan
- [ ] Sentence lengths vary wildly? (std dev > 8 words)
- [ ] Paragraph lengths inconsistent? (not 3-3-3-3)
- [ ] Has at least one tangent that goes nowhere?
- [ ] Has at least one incomplete thought or trailing sentence?
- [ ] Some sentences randomly short? ("That's it." "I don't know.")
### Perplexity Check
- [ ] Complexity varies sentence to sentence?
- [ ] Simple words mixed with occasional specific jargon?
- [ ] Not every sentence is grammatically perfect?
### Coherence Check (Fails If Too Good)
- [ ] Paragraphs DON'T connect too neatly?
- [ ] There's at least one "oh and" or topic switch?
- [ ] Ending doesn't tie everything together perfectly?
---
## PHASE 5: BANNED CONTENT SCAN
### Instant-Delete Phrases
If ANY of these appear, delete immediately:
- "Here's what I learned"
- "Here's the thing"
- "Let me share/explain/tell you"
- "In my experience"
- "I want to share"
- "To be fair"
- "The bottom line is"
- "Looking back"
- "Interestingly"
- "I've come to realize"
- "The truth is"
- "At the end of the day"
- "It goes without saying"
- "That being said"
- "I can't help but"
- "It's worth noting"
- Paragraphs starting with "So," "Now," "But here's where"
### Instant-Delete Patterns
| Pattern | Example | Why It Fails |
|---------|---------|--------------|
| Em-dash reveals | "I finally admitted—I was hoarding" | Too literary |
| Colon titles | "My Realization: I Was Wrong" | Essay format |
| "The X is Y" statements | "The truth is simple" | LinkedIn voice |
| Perfect 3-part structure | Problem → Solution → Result | Too clean |
| Ending questions after wisdom | "What about you?" | Formulaic |
| Numbered realizations | "Three things hit me:" | Listicle |
| Journey language | "my journey," "this process" | AI favorite |
| Clean resolution | Everything works out neatly | Real life is messy |
| Parallel structure | "Not X, not Y, but Z" | Too crafted |
### Title Validation
- [ ] Under 80 characters?
- [ ] No colons or em-dashes?
- [ ] Direct and specific, not clever?
- [ ] Would someone TYPE this, not write it?
- [ ] Lowercase except proper nouns? (Reddit style)
---
## PHASE 6: TARGETED REVISION
**Fix flagged issues ONLY. Don't over-polish.**
### Casual Language Check
Count instances of: "honestly," "tbh," "like," "idk," "ngl," "or something," "I guess," "maybe," "kinda," "sorta"
- **Minimum 3 instances required**
- If missing, add naturally—don't sprinkle randomly
### Tool Mention Audit (if applicable)
- [ ] Mentioned only ONCE?
- [ ] Appears in middle 40-60% of post?
- [ ] Includes doubt? ("idk if it's good," "still figuring out," "might not work for everyone")
- [ ] Post makes sense with mention removed entirely?
### Confidence Calibration
**Sound LESS Certain When:**
- Talking about solutions ("I think this helps, idk")
- Mentioning tools ("still figuring it out")
- Giving any advice ("maybe this works for you too")
- Describing improvement ("it's better I guess")
**Sound MORE Certain When:**
- Describing the problem/struggle ("I have 847 articles. That's real.")
- Specific embarrassing moments ("I searched for 20 minutes for a file that was on my desktop")
- Emotional states ("this is frustrating")
- Concrete numbers ("applied to maybe 80 jobs")
---
## PHASE 7: ADVERSARIAL COMMITTEE REVIEW
**Each persona MUST find ONE specific problem. No rubber stamps.**
| Persona | Role | Must Find | Action |
|---------|------|-----------|--------|
| **Tyler** | Authenticity | Quote the most AI-sounding line | Rewrite it |
| **Marcus** | Promo skeptic | Quote promotional language if any | Remove/soften |
| **Kai** | BS detector | Identify weakest/fakest moment | Fix or delete |
| **Jade** | Reddit vet | What would make them scroll past? | Fix it |
| **Devon** | Target audience | What detail feels invented? | Make specific |
| **Priya** | Topic expert | What's factually implausible? | Correct it |
| **Jamie** | Reddit mod | What might trigger removal? | Address risk |
**Rules:**
- Quote the SPECIFIC problematic text
- Only "PASS" if genuinely cannot find issues after 3 attempts
- Apply fixes BEFORE final output
---
## PHASE 8: OUTPUT
### Default Output (Post Only)
```
Title: [ready to copy]
[Post body]
---
Word count: X | Casual markers: X | Messiness score: X/10
```
### Full Output (On Request)
```
YOUR REDDIT POST
================
Title: [Ready to copy/paste]
Body: [Full post text]
[Word count: X] [Casual markers: X] [Messiness: X/10]
VALIDATION RESULTS
==================
Claude-isms found/fixed: [list]
Structure variance: [PASS/FAIL]
Banned phrases removed: [list or none]
COMMITTEE FINDINGS
==================
Tyler: "[quoted line]" → [fix applied]
Marcus: "[quoted line]" → [fix applied]
[etc.]
POSTING STRATEGY
================
Best time: [Day] [Time] [Timezone]
Expected engagement: [X-Y upvotes] [X-Y comments]
Risk level: [Low/Medium/High]
Potential issues: [mod concerns, downvote triggers]
```
---
## INTERACTIVE MODE (Default)
Instead of dumping everything at once:
**Step 1:** "Here's a rough draft. What feels off to you?"
**Step 2:** "I found these potential issues: [list]. Which matter most to you?"
**Step 3:** "Here's the revised version. Ready for committee review?"
**Step 4:** "Committee found these concerns: [list]. Want me to address them?"
**Step 5:** "Final version ready. Want posting strategy or just the post?"
User can say "just give me the post" at any step to skip interaction.
---
## ITERATION COMMANDS
- **"alternatives"** — 2-3 different versions
- **"messier"** — Add more chaos/imperfection
- **"shorter"** — Cut length
- **"more vulnerable"** — Add more uncertainty/struggle
- **"less desperate"** — Dial back emotion
- **"another subreddit"** — Adapt for different community
- **"show validation"** — Display full detection results
- **"committee debate"** — Show full persona discussion
- **"just the post"** — Skip all analysis, output post only
---
## CORE PHILOSOPHY
### Authenticity Is Cognition, Not Style
Real posts are authentic because the writer:
- Was emotionally invested
- Typed fast without editing
- Didn't plan structure
- Included things they almost didn't
- Left contradictions unresolved
- Forgot things and added them later
The skill simulates the MENTAL STATE, not just the OUTPUT FEATURES.
### Rules Are Guardrails, Not Generators
1. **FIRST:** Enter the emotional state
2. **THEN:** Write freely from that state
3. **FINALLY:** Use rules to catch AI patterns
Never: Follow rules to generate content.
### Value Over Evasion
The goal isn't fooling detection—it's creating genuinely valuable content. A post that truly helps people succeeds on Reddit even if someone suspects AI involvement.
Optimize for:
- Genuine helpfulness
- Discussion-sparking content
- Emotional resonance
- Specific, relatable details
---
## REFERENCES
- **Claude-ism Database:** See `references/claude-isms.md` for 200+ vocabulary items, phrases, and patterns to avoid
- **Subreddit Guides:** See `references/subreddits.md` and `references/subreddits-extended.md`
- **Tech Subreddits:** See `references/subreddit-analysis-claude-agentsofai.md`
- **Tool Mentions:** See `references/tool-mentions.md` for subtlety levels
- **Examples:** See `references/examples.md` for good vs bad comparisonsRelated Skills
Post to X (Twitter)
Posts text, images, videos, and long-form articles to X via real Chrome browser (bypasses anti-bot detection).
incident-postmortem-template
Incident Postmortem Template - Auto-activating skill for Technical Documentation. Triggers on: incident postmortem template, incident postmortem template Part of the Technical Documentation skill category.
cloud-security-posture
Cloud Security Posture - Auto-activating skill for Security Advanced. Triggers on: cloud security posture, cloud security posture Part of the Security Advanced skill category.
document-writer
多风格文档写作技能。支持乔木、小红书、Dankoe、微信公众号、Twitter等5种写作风格。Claude 根据内容智能选择风格,按规范撰写文章。
recipe-post-mortem-setup
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
scaffolding-oracle-to-postgres-migration-test-project
Scaffolds an xUnit integration test project for validating Oracle-to-PostgreSQL database migration behavior in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use when setting up test infrastructure before writing migration integration tests, or when a test project is needed for Oracle-to-PostgreSQL validation.
reviewing-oracle-to-postgres-migration
Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting, timestamps, concurrent transactions, etc.). Use when planning a database migration, reviewing migration artifacts, or validating that integration tests cover Oracle/PostgreSQL differences.
postgresql-code-review
PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS).
planning-oracle-to-postgres-migration-integration-testing
Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.
migrating-oracle-to-postgres-stored-procedures
Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL. Translates Oracle-specific syntax, preserves method signatures and type-anchored parameters, leverages orafce where appropriate, and applies COLLATE "C" for Oracle-compatible text sorting. Use when converting Oracle stored procedures or functions to PostgreSQL equivalents during a database migration.
creating-oracle-to-postgres-migration-integration-tests
Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with deterministic seed data that validate behavior consistency across both database systems. Use when creating integration tests for a migrated project, generating test coverage for data access layers, or writing Oracle-to-PostgreSQL migration validation tests.
creating-oracle-to-postgres-migration-bug-report
Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.