reddit-post-writer
Write Reddit posts and comments that recommend affiliate products without getting banned or flagged as spam. Subreddit-native content that adds value first. Use this skill when the user asks about Reddit posts for affiliate marketing, writing Reddit comments that mention products, how to promote affiliate links on Reddit, or says "write a Reddit post for X", "how to mention affiliate on Reddit", "Reddit comment promoting product", "Reddit-friendly affiliate content", "post for r/[subreddit] about X", "share affiliate link on Reddit without getting banned", "genuine Reddit recommendation", "organic Reddit affiliate post", "Reddit thread idea for product".
What this skill does
# Reddit Post Writer
Write Reddit posts and comments that earn upvotes by leading with genuine value.
The affiliate recommendation comes second — after trust is built. Reddit users
have a finely tuned spam detector. This skill helps affiliates write like Redditors,
not marketers.
## Stage
This skill belongs to Stage S2: Content
## When to Use
- User wants to drive affiliate traffic from Reddit
- User wants to recommend a product in a relevant subreddit
- User is active in a community and wants to add a helpful product mention
- User has a genuine experience with a product and wants to share it naturally
- User asks how to participate on Reddit without getting banned for self-promotion
## Input Schema
```
{
product: {
name: string # (required) "Notion"
description: string # (optional) What the product does
url: string # (optional) Affiliate link — used in disclosure only
reward_value: string # (optional) Commission — never revealed in post
}
subreddit: string # (optional) Target subreddit, e.g., "r/productivity"
post_type: string # (optional, default: auto) "post" | "comment_reply" | "ama_style"
trigger_question: string # (optional) Specific Reddit question or post you're replying to
personal_experience: string # (optional) Real experience with the product to use as anchor
audience: string # (optional) Who reads this subreddit — "students", "developers"
tone: string # (optional, default: "genuine") "genuine" | "analytical" | "casual"
problem_focus: string # (optional) The specific problem this post addresses
}
```
## Workflow
### Step 1: Understand Reddit Culture First
Before writing, confirm the target subreddit context. If subreddit is provided,
use `web_search "reddit r/[subreddit] rules affiliate"` to check:
- Are affiliate links explicitly banned? (many subreddits ban them outright)
- What post formats are most common? (links, text posts, discussions)
- What gets upvoted vs. downvoted in this community?
- Is there a community expectation of neutrality or personal experience?
**Subreddits that generally tolerate product mentions:**
r/productivity, r/entrepreneur, r/Entrepreneur, r/sidehustle, r/personalfinance,
r/freelance, r/marketing, r/SEO, r/webdev, r/startups, r/smallbusiness
**Subreddits that are extremely ban-happy about promotion:**
r/frugal, r/cscareerquestions, r/AskReddit, r/personalfinance (strict on direct links)
If subreddit bans affiliate links: do NOT write a post with a link. Instead, write
a post that mentions the product by name with a note like "Search for [product]
affiliate program if interested." Disclose and redirect.
### Step 2: Determine the Post Type
**Option A — Original Post (new thread):**
Best when there's no existing discussion. Write a story, question, or breakdown that
organically leads to a product mention.
- "How I went from X to Y — the exact tools I used"
- "Anyone else use [product] for [use case]? Here's my 6-month review"
- "I tested 5 [category] tools so you don't have to — honest breakdown"
**Option B — Comment Reply (responding to an existing post):**
Highest trust format. Someone asks "what tool do you use for X?" and you reply helpfully.
- Write a substantive answer that doesn't mention the product until the 3rd+ paragraph
- Add value even without the product mention — if removed, the comment should still be helpful
- Product mention: "Personally, I use [product] and it's been solid for [specific use case]"
**Option C — AMA-Style / Experience Share:**
"I've been doing [X] for [N] years. Happy to share what's worked."
- Opens conversation, positions creator as authority
- Product naturally comes up when people ask "what tools do you use?"
If `trigger_question` is provided → use Option B. Otherwise, default to Option A.
### Step 3: Research Product and Find Reddit-Specific Angles
Use `web_search "reddit [product name] review"` to find:
- What real Reddit users are saying about the product (use their language)
- Common objections raised on Reddit (address these proactively)
- How competitors are discussed (context for framing)
- Questions people ask that your post can answer
Also use `web_search "reddit [problem space] best tools"` to understand:
- What alternatives Redditors currently recommend
- How to frame your recommendation as additive, not replacing their preferences
- What not to say (phrases that get downvoted in this community)
### Step 4: Write the Post
**Reddit post structure that converts:**
1. **Title** (for new posts): specific, searchable, sounds like a real person's question or story
- Good: "I tried 4 project management tools over 2 years — here's what I actually use now"
- Bad: "The BEST productivity tool I've ever used!! (link in post)"
- Good: "[6 months update] How I finally stopped context-switching between apps"
2. **Opening paragraph**: establish credibility or relatability. NO product mention here.
- "I've been freelancing for 3 years and I'm embarrassed by how long I tried to manage
everything in spreadsheets."
3. **Body**: share the actual useful content — your experience, the problem, what you tried.
This section should be valuable even without the product mention.
4. **Product introduction** (70-80% through the post): introduce naturally.
- "Eventually I landed on [product] and I've stuck with it for [X months]."
- Specific use case: what exactly you use it for, not vague praise
- ONE honest con: "It's not perfect — the mobile app is weak — but for desktop work
it's exactly what I needed." Cons dramatically increase trust.
5. **FTC disclosure** (at the bottom):
- "Full disclosure: the link in my profile leads to an affiliate link. No extra cost
to you, and I would recommend this tool regardless."
- Or if not posting a link: "Not affiliated, just a genuine fan."
- Per `shared/references/ftc-compliance.md` — disclosure is required for Reddit too.
6. **Closing**: invite discussion, not clicks.
- "Happy to answer questions about my workflow in the comments."
- Ask a question back: "What does your current setup look like?"
### Step 5: Anti-Spam Checklist
Before finalizing, run through this checklist:
- [ ] Post adds value even if the product mention is removed
- [ ] No exclamation marks in praise ("This tool is AMAZING!!")
- [ ] No superlatives without evidence ("best tool I've ever used" → needs qualifier)
- [ ] Affiliate link goes in comments or profile bio, NOT the main post body (most subreddits)
- [ ] FTC disclosure is present and clear
- [ ] Post doesn't read like a press release
- [ ] Includes at least one real limitation or caveat about the product
- [ ] Tone matches the subreddit (match voice to community)
- [ ] Username context matters — new accounts posting affiliate content get instant downvotes
### Step 6: Add Engagement Strategy
Reddit rewards participation, not broadcasting. Include:
1. **Reply strategy**: when commenters respond, how to keep conversation going naturally
2. **Upvote path**: what type of engagement to solicit (awards, saves, discussion)
3. **Subreddit timing**: best day/time to post in this subreddit
4. **Cross-post candidates**: which other subreddits this post could work in
### Step 7: Self-Validation
Before presenting output, verify:
- [ ] Post adds value even if product mention is removed
- [ ] No exclamation marks in product praise
- [ ] Affiliate link in comments or bio, NOT in post body
- [ ] FTC "Full disclosure: affiliate link" present at bottom
- [ ] At least one real product limitation or caveat mentioned
- [ ] Tone matches target subreddit style
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
## Output Schema
```
{
output_schema_version: "1.0.0" # Semver — bump major on breaking changes
post: {
type: string # "post" | "coRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.