agentleFS
selamy-labsselamy-labs/agent-skills/skills/reddit-research/SKILL.md

reddit-research

Skill0 starsChanged 6 days agoMITView on GitHub

Use when collecting Reddit discussion signals for research, trend discovery, or hypothesis generation. Requires terms-aware access, source lineage, rate-limit discipline, and clear uncertainty.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 10 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the current platform terms, developer documentation, and allowed use before automating collection.

    line 14
  2. Very specific:

    Default to no-credential public endpoints for low-volume discovery: JSON listing and thread URLs such as …

    line 16
  3. Distinctive:

    Keep no-credential polling bounded, cache-aware, and easy to disable.

    line 20
  4. Distinctive:

    Use a descriptive user agent or app identity where the access path supports it.

    line 21
  5. Very specific:

    If JSON listing or comment-tree endpoints return 403 from a datacenter or CI network, record that as an access-path finding and fall back …

    line 42
  6. Distinctive:

    Avoid bulk republication of user content.

    line 55
  7. Distinctive:

    Treat vote scores, awards, and comments as engagement signals with caveats, not as popularity truth.

    line 57
  8. Distinctive:

    Do not infer demographics, identity, or intent beyond what the source directly supports.

    line 65
  9. Distinctive:

    Check high-value claims against independent sources before using them for decisions.

    line 69
  10. Distinctive:

    Add tracing spans around fetch, parse, normalize, and publish steps when Reddit data feeds a product or automated decision.

    line 79
  11. Distinctive:

    Keep credentials in the repository's established secret-management path.

    line 81
  12. Distinctive:

    Every research output should include:

    line 85

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reddit Research

Reddit is a noisy public-discussion source, not a ground-truth database. Use it to generate hypotheses, locate themes, and identify examples that can be checked against independent evidence.

Access Order

  • Check the current platform terms, developer documentation, and allowed use before automating collection.
  • Default to no-credential public endpoints for low-volume discovery: JSON listing and thread URLs such as /r/<community>/top.json?t=day&limit=25 or /r/<community>/comments/<post_id>.json, and RSS feeds such as /r/<community>/.rss.
  • Keep no-credential polling bounded, cache-aware, and easy to disable.
  • Use a descriptive user agent or app identity where the access path supports it.
  • Respect rate limits and back off on 429, 401, 403, and repeated 5xx responses.
  • Escalate to official API, OAuth, or an approved provider when public endpoints are blocked, comments are unavailable, volume grows beyond light polling, or the research becomes product-critical.

Verified Envelope

Public Reddit endpoints are not a stable contract. Validate current behavior from the actual runtime network before treating the path as available.

A useful light-polling envelope is:

  • a small allowlist of communities
  • single-digit requests per run
  • conservative cadence such as minutes or hours, not tight loops
  • local caching keyed by URL and retrieval time
  • graceful partial output when listing, thread, or RSS variants differ

If JSON listing or comment-tree endpoints return 403 from a datacenter or CI network, record that as an access-path finding and fall back to RSS only for feed-level discovery. RSS does not replace comment-tree ingestion. Escalate when comments or reliable pagination are required.

Collection

  • Define the research question, communities, time window, sort order, and filters before pulling data.
  • Capture post URL, post ID, comment ID, author display handle when available, authored timestamp, retrieved timestamp, score fields, and permalink.
  • Preserve deleted, removed, locked, quarantined, mature, and unavailable states instead of silently dropping them.
  • Avoid bulk republication of user content. Quote only the minimum needed for verification and prefer short paraphrases with links.
  • Treat vote scores, awards, and comments as engagement signals with caveats, not as popularity truth.

Analysis

  • Separate observation from interpretation.
  • Label Reddit-derived outputs as sentiment, themes, objections, language, or candidate hypotheses.
  • Do not infer demographics, identity, or intent beyond what the source directly supports.
  • Watch for bots, coordinated activity, deleted context, sarcasm, stale posts, and community-specific norms.
  • Check high-value claims against independent sources before using them for decisions.

Build Requirements

  • Store raw fixtures from sanitized examples and test parsers against them.
  • Make pagination, retry, rate-limit, unavailable-content, and schema-drift behavior explicit.
  • Emit structured logs and metrics for request count, status code, latency, backoff, parse failures, and records produced.
  • Add tracing spans around fetch, parse, normalize, and publish steps when Reddit data feeds a product or automated decision.
  • Keep credentials in the repository's established secret-management path.

Output Contract

Every research output should include:

  • question and collection window
  • communities and filters queried
  • access path used
  • source links and retrieval time
  • caveats and known missing coverage
  • confidence level and recommended next verification step

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.