Reddit

Write something a particular community would want to read, discuss, or use. Earn attention with a concrete subject and a worthwhile payoff. Preserve the author's actual experience and connection to the topic.

Shared foundation: Read social-content once, then its relevant references. Install both sibling skills together. Reddit-specific choices below govern local presentation; shared truthfulness and scope constraints still apply. If the companion is unavailable, say so briefly and proceed from this playbook without inventing claims or unavailable knowledge.

Establish the destination

For a named community, inspect current rules, pinned guidance, and relevant recent posts using available read access. Read the linked source before rewriting a news or article submission. Capture required title conventions, post type/flair, promotion and AI rules, and any appropriate megathread. Look at ordinary posts and comments as well as high-scoring examples.

For new ideas or a posting strategy, apply the shared research workflow before choosing hooks. Inspect recent top posts and current discussions in the target subreddit, using available time filters and hot/new views. Search the same problem, competing products, and relevant creators; read comments for recurring questions and gaps. Include ordinary comparable posts so a giveaway or old outlier does not define the strategy. Ground each idea in specific observed examples, explain the author's fresh contribution, and include source links or supplied identifiers outside the draft. Use current supplied research when sufficient; do not repeat the same research pass.

Use the playbook for community research, selecting a format, drafting, and reviewing performance. This skill teaches content judgment; it does not install a Reddit client or imply access to an account.

If rules or live content cannot be read, identify the gap and work from supplied excerpts. Never claim compliance or current research you did not verify. With no subreddit specified, draft provisionally and ask for the destination only if needed to finalize it. A title-only rewrite does not require an unrelated audience interview.

Draft for the community

• Put the specific topic, finding, problem, or useful artifact in the title. Leave an interesting detail for the body without withholding the subject. Follow source-title requirements for news/link posts; do not sensationalize a source to manufacture a different takeaway.
• Open with the substantive point. Use normal paragraphs and the author's vocabulary. Copying another platform's sales cadence is not adaptation.
• Supply the value inside the post: relevant details, method, evidence, tradeoffs, or a concrete question. Do not imply a working feature produced unmeasured savings or that a proposed solution fixed an unverified problem.
• For an owned product, say the author built or benefits from it. A relevant connection can be one plain sentence, not a disclaimer wall. A free tool can still be promotion; links, comments, and DMs are not loopholes.
• Finish with a specific question only when the author wants an answer. Giveaways, vote requests, comment gates, and generic calls for engagement are not default writing devices.

If the requested placement conflicts with the community's rules, explain the concrete conflict and offer a permitted format, destination, or private revision. Do not hide promotion or AI authorship to evade the rule.

Deliver

Honor the requested format. Otherwise return a few distinct titles, the recommended title and post, and at most a short note about a material assumption or unresolved rule. Keep the research brief and factual audit out of the copy. Do not post, message moderators, or contact commenters without authorization for that action.

For a video post, also read the shared video-script reference. For a reply, answer the actual comment and account for the surrounding discussion; do not turn every answer into a product mention.