RonanCodes/reddit-scan
skills/reddit-scan/SKILL.md
Scan Reddit for hot threads in a subreddit, topic search, or a single-thread fetch. Uses the public .json endpoint (no auth). Returns findings without vault persistence. Sibling to llm-wiki/ingest-reddit.
research
Updated May 1, 2026
$ install --global
skillsauthnpx skillsauth add RonanCodes/ronan-skills reddit-scanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 8:43 AM171.5s1 file scanned
SKILL.md
- name:
- reddit-scan
- description:
- Scan Reddit for hot threads in a subreddit, topic search, or a single-thread fetch. Uses the public .json endpoint (no auth). Returns findings without vault persistence. Sibling to llm-wiki/ingest-reddit.
- category:
- research
- argument-hint:
- <reddit-url | r/subreddit | "search:topic"> [--limit N] [--sort hot|top|new] [--since day|week|month|year]
- allowed-tools:
- Bash(curl *) Read
- - pipeline:
- scan
- - platform:
- - role:
- scanner
Reddit Scan
Pull threads from Reddit and return distilled findings. No file writes.
Usage
/ro:reddit-scan https://www.reddit.com/r/LocalLLaMA/comments/xxx/yyy/ # single thread
/ro:reddit-scan r/LocalLLaMA --sort hot --limit 25 # hot in subreddit
/ro:reddit-scan r/LocalLLaMA --sort top --since week # top of week
/ro:reddit-scan "search:agent observability" --limit 20 # cross-subreddit search
Modes
1. Single-thread mode (URL)
curl -sL -H "User-Agent: ronan-skills-scan/1.0" \
"https://www.reddit.com/r/{subreddit}/comments/{id}/{slug}.json?sort=top&limit=500"
Response is [post, comments]:
[0].data.children[0].data→ post (title,selftext,author,score,num_comments,created_utc,url,is_self)[1].data.children[]→ comment tree (each.datahasauthor,body,score,created_utc,replies)
Return:
- Post header (title, score, author, link if external)
- Post body (selftext) trimmed to ~800 chars
- Top 10 comments by score, flattened, each trimmed to ~300 chars
- Total comment count
Skip kind === "more" placeholders and author === null (deleted).
2. Subreddit listing mode (r/<name>)
# sort = hot | top | new | rising
curl -sL -H "User-Agent: ronan-skills-scan/1.0" \
"https://www.reddit.com/r/{sub}/{sort}.json?limit={N}&t={since}"
t is one of hour|day|week|month|year|all (only relevant for top).
Return one line per thread with score, comment count, title, URL.
3. Search mode (search:<topic>)
curl -sL -H "User-Agent: ronan-skills-scan/1.0" \
"https://www.reddit.com/search.json?q=<encoded>&sort=relevance&t={since}&limit={N}"
Same output shape as subreddit listing.
Output format
# Reddit scan: <target> (<N> results)
1. [<score>pts, <comments>c] <title> r/<subreddit>
<external-url if link post>
https://www.reddit.com/<permalink>
2. ...
For single-thread mode: header + body + top comments section.
Rate limiting + fallback
The public .json endpoint is lenient but not unlimited. On 429 or 403:
- Wait ~3 seconds and retry once.
- Swap
www.reddit.com→old.reddit.com(same JSON shape, different CDN). - If still failing, report clearly — don't hammer.
Always send a descriptive User-Agent; Reddit blocks generic curl UAs more aggressively.
Dependencies
None — curl only.
See also
llm-wiki/.claude/skills/ingest-reddit— persists full threads into a vault with YAML frontmatter. Use when you want the content kept./ro:trend-scan— orchestrator running reddit-scan alongside the other source scanners./ro:hn-scan,/ro:x-scan,/ro:linkedin-scan— siblings.
Related Skills
RonanCodes/linear-update
development
VerifiedTrustedCommunity
Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
SKILL.mdUpdated Jun 12, 2026
RonanCodes/linear-nightshift
devops
VerifiedTrustedCommunity
Run a night-shift against a collaborator's Linear board. Pulls the team's Grilled tickets (/ro:linear-grill moves a ticket to Grilled once its questions are answered), VERIFIES the questions were actually answered (unanswered → bounce the ticket to the "Question for <name>" state), mirrors verified tickets to ephemeral GitHub issues with ready-for-agent, then runs the standard /ro:night-shift machinery on GitHub. Tail-calls /ro:linear-update for everything that merged + deployed. Triggers on "linear nightshift", "nightshift linear", "drain the linear board", "run the shift off linear", "/ro:linear-nightshift".
SKILL.mdUpdated Jun 12, 2026
RonanCodes/linear-grill
development
VerifiedTrustedCommunity
Grill a collaborator's Linear tickets and move every processed ticket to where it belongs. Resolves the board from the repo's .ro-linear.json, reads the collaborator's Backlog / Ready-for-agent issues, then per ticket either posts 3-5 decision-extracting questions (state moves to "Question for <name>") or confirms it build-ready (state moves to "Grilled", the gate /ro:linear-nightshift consumes); shipped-and-confirmed tickets close as Done. The async-collaborator counterpart of /ro:day-shift for people who never touch GitHub. Triggers on "grill linear", "grill eoin's tickets", "linear grill", "add questions to the linear tickets", "/ro:linear-grill".
SKILL.mdUpdated Jun 12, 2026
RonanCodes/skills/about-page
development
VerifiedTrustedCommunity
--- name: about-page description: Add a standard About page to any web app, what it is, the tech stack, and an FAQ, wired into a footer link with a sticky footer. Built with Spartan + Tailwind (the canonical component layer) and falls back to semantic HTML so it ships reliably. Use whenever building, polishing, or shipping an app, every app should have one. Triggers on "add an about page", "about page", "footer about link", or as a standard step in app build/polish. category: frontend argument-h
SKILL.mdUpdated Jun 9, 2026