Scans HN, Lobsters, Reddit, and tech blogs for community experience reports. Use when gathering practitioner opinions on a technology or approach.
Scanned 5/29/2026
Install to Claude Code
npx -y skills add athola/claude-night-market --skill discourse --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Discourse?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/athola-discourse)More formats (shields.io, HTML) on the badges page.
---
name: discourse
role: library
description: Scans HN, Lobsters, Reddit, and tech blogs for community experience reports. Use when gathering practitioner opinions on a technology or approach.
alwaysApply: false
category: research
tags:
- hackernews
- reddit
- lobsters
- blogs
- discourse
estimated_tokens: 200
model_hint: standard
---
# 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...