discourse
Scans HN, Lobsters, Reddit, and tech blogs for community experience reports. Use when gathering practitioner opinions on a technology or approach.
npx skills add majiayu000/claude-skill-registry --skill discourse --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Discourse Search ## When To Use - Gathering community opinions on a technology or approach - Finding experience reports from HN, Reddit, or Lobsters ## When NOT To Use - Academic research (use `/tome:papers`) - Code examples (use `/tome:code-search`) Scan community channels for discussions on a topic. ## Channels - **Hacker News**: Algolia API at hn.algolia.com - **Lobsters**: WebSearch with site:lobste.rs - **Reddit**: JSON API (append .json to URLs) - **Tech blogs**: WebSearch targeting curated domains ## Workflow 1. Build search URLs/queries per channel using `tome.channels.discourse.*` functions 2. Execute via WebFetch (APIs) or WebSearch (fallback) 3. Parse responses into Finding objects 4. Merge across sources with source attribution
- When To Use
- When NOT To Use
- Channels
- Workflow
What does the discourse skill do?
Scans HN, Lobsters, Reddit, and tech blogs for community experience reports. Use when gathering practitioner opinions on a technology or approach.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill discourse --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
