Reddit Scraper

**Quick judgment** A solid, focused Reddit reader/searcher skill that leverages Reddit’s public JSON endpoints without needing authentication. It covers the most important read-only capabilities (subreddit feeds, search, sorting, time filters, JSON output) and is well-suited as a general-purpose “pull Reddit context” utility for other agents or workflows. Main weaknesses are dependency on Reddit’s rate limits and API/HTML stability, plus the usual content-safety concerns inherent to Reddit data. **What it does well** - Fetches posts from specific subreddits with configurable sort (`hot`, `new`, `top`, `rising`, plus some localized sort names) and time filters. - Supports both global Reddit search and subreddit-scoped search, with a straightforward CLI-style interface. - Provides a JSON mode with useful fields (title, author, score, comments count, URL, permalink, subreddit, timestamp, partial selftext, upvote ratio), making it easy to integrate into automation or analysis pipelines. - Read-only design reduces risk of unintended interactions with Reddit (no posting, commenting, or voting). **Key risks / limitations** - **Reliance on Reddit’s public interface**: Any change in Reddit’s JSON structure, old.reddit.com behavior, or tighter anti-scraping measures can break functionality. - **Rate limiting and blocking**: Heavy or frequent use may hit Reddit rate limits or trigger temporary blocking; large-scale monitoring is not guaranteed to be stable. - **Content safety**: Reddit content can include NSFW material, hate speech, harassment, misinformation, and other harmful content. The skill itself does not filter or classify content; downstream consumers must handle safety filtering and policy enforcement. - **Coverage gaps**: No authenticated access means restricted/private subreddits, quarantined communities, and some filtered content will be inaccessible. - **Internationalization quirks**: The presence of localized sort names (`populares`, `nuevos`) suggests behavior may depend on how endpoints are called or environment settings; this could introduce subtle inconsistencies. **Recommended scenarios** - Use as a **context-gathering tool** when an assistant needs up-to-date Reddit discussions about a topic, product, or error message. - Use for **lightweight monitoring** of a few key communities (e.g., daily or hourly fetches for summarization), with expectations set around occasional rate-limit failures. - Use when you need **structured Reddit data** (JSON) for downstream summarization, clustering, or simple analytics, but do not require comments, voting, or any form of interaction. - Avoid relying on it for **high-volume, continuous scraping** or mission-critical workflows that demand strong reliability guarantees; in such cases, pair it with robust retry logic, caching, and fallback strategies.