skills/hn-scan/SKILL.md
Scan Hacker News for trends, hot threads, or specific topics. Returns findings — titles, points, comment highlights, URLs — without writing anywhere. Use when you want to see what's trending, research a topic, or pull a specific thread. Sibling to llm-wiki/ingest-hackernews (that one persists to a vault; this one just returns findings).
npx skillsauth add RonanCodes/ronan-skills hn-scanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pull threads or topic results from Hacker News and return the distilled findings to the caller. No vault, no file writes — just a summary the caller can use.
/ro:hn-scan "agent observability" # search front page + recent
/ro:hn-scan "show hn AI agent" --since 30d # search Show HN in last 30 days
/ro:hn-scan https://news.ycombinator.com/item?id=47799856 # fetch one thread
/ro:hn-scan frontpage --limit 30 # top N current front-page stories
/ro:hn-scan show --since 7d # Show HN in last week
/ro:hn-scan ask --since 7d # Ask HN in last week
Algolia HN search — no auth, no rate limit in practice.
curl -s "https://hn.algolia.com/api/v1/search?query=<encoded-query>&tags=story&hitsPerPage=30"
# Add &numericFilters=created_at_i>$(date -v-7d +%s) for --since 7d
For each hit return:
title, points, num_comments, author, url (external link), story_id, created_athttps://news.ycombinator.com/item?id={story_id}Rank by points × recency (points / (age_hours + 2)^1.8).
If the arg is a HN URL or bare item id, fetch the full tree:
curl -s "https://hn.algolia.com/api/v1/items/{id}"
Return:
# frontpage
curl -s "https://hn.algolia.com/api/v1/search?tags=front_page&hitsPerPage=30"
# Show HN
curl -s "https://hn.algolia.com/api/v1/search_by_date?tags=show_hn&hitsPerPage=30"
# Ask HN
curl -s "https://hn.algolia.com/api/v1/search_by_date?tags=ask_hn&hitsPerPage=30"
Return a terse report the caller can reason over. No markdown files, no YAML frontmatter.
# HN scan: "<query>" (<N> results, last <window>)
1. [<points>pts, <comments>c] <title>
<external-url-if-any>
https://news.ycombinator.com/item?id=<id>
<1-line takeaway if comment count > 50 and the story is relevant>
2. ...
For single-thread mode include the top-comments summary under the header.
Algolia returns HTML-encoded text. Before returning, convert:
<p> → double newline<a href="X">Y</a> → [Y](X)<code> / <pre> → backticks / fences', &, >, <, ") → literal charsNone — uses curl + the free Algolia HN API.
llm-wiki/.claude/skills/ingest-hackernews — the sibling skill that persists full threads into an Obsidian-style vault. Use that when you want to keep the content long-term; use /ro:hn-scan when you just want to see what's there./ro:trend-scan — orchestrator that runs hn-scan + x-scan + linkedin-scan + reddit-scan in parallel for a topic./ro:x-scan, /ro:linkedin-scan, /ro:reddit-scan — siblings for other sources.testing
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
development
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
tools
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
research
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".