Menu

Individual skill

subreddit-research

0upvotes

Use this skill when the user needs to find or vet Reddit communities — "which subreddits should we be in," "is r/X worth targeting," "research communities for this product." Searches live Reddit data, inspects community size, rules, content, and traffic, and produces a vetted shortlist worth adding to a campaign — plus the reasons to skip the rest.

skills/yahav-fuchs/subreddit-research/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use when choosing which Reddit communities a brand belongs in. Produces a vetted shortlist with evidence, not a keyword dump. Exact commands live in `references/commands.md`.

## Procedure

1. **search wide** — query by topic, problem language, and adjacent niches, not just the product category. The communities where buyers ask questions rarely carry the category name
2. **inspect each candidate**: subscriber count, community type (restricted or private → drop it), posting rules, and what the top posts this week actually look like
3. **judge fit from content, not size** — browse top and rising posts: is anyone asking the questions this product answers? A 40k-subscriber community with daily buying questions beats a 2M-subscriber meme feed
4. **check the wiki and traffic** for posting norms and activity trends
5. **deliver the shortlist**: for each community — name, size, why it fits (with a sample thread), the rules that constrain posting there. Let the user choose what gets added to tracking

Work gradually: vet five candidates at a time, one line of verdict each, then continue.

## What good looks like
Back to top