gooseworks-ai/goose-skills / skills/shared/hacker-news-scraper
hacker-news-scraper
VerifiedSearch Hacker News stories and comments using the free Algolia API. No Apify token needed. Use when you need to find HN discussions, track mentions, discover Show HN launches, or monitor tech community sentiment.
Hacker News Scraper
Search Hacker News using the free Algolia HN Search API. No Apify token or API key needed.
Quick Start
Only dependency: pip install requests.
# Stories about AI content marketing in last week
python3 skills/hacker-news-scraper/scripts/search_hn.py \
--query "AI content marketing" --days 7
# Show HN posts in last month (summary view)
python3 skills/hacker-news-scraper/scripts/search_hn.py \
--query "" --tags show_hn --days 30 --output summary
# Comments mentioning a specific tool
python3 skills/hacker-news-scraper/scripts/search_hn.py \
--query "LangChain" --tags comment --days 14 --max-results 20
How the Script Works
- Queries the Algolia HN Search API (
search_by_dateendpoint) - Uses
numericFilters=created_at_i>{unix_timestamp}for server-side date filtering - Paginates until max-results reached
- Normalizes results to a consistent schema
- Applies optional keyword filtering (client-side)
- Sorts by points (descending) and outputs JSON or summary
CLI Reference
| Flag | Default | Description |
|---|---|---|
--query | required | Search query |
--days | 7 | How many days back to search |
--tags | story | Item type: story, comment, ask_hn, show_hn |
--max-results | 50 | Max results to return |
--keywords | none | Additional filter keywords (comma-separated, OR logic) |
--output | json | Output format: json or summary |
Output Format
{
"id": "12345678",
"title": "Show HN: My new tool",
"url": "https://example.com",
"author": "username",
"points": 42,
"num_comments": 15,
"created_at": "2026-02-18T12:00:00.000Z",
"hn_url": "https://news.ycombinator.com/item?id=12345678",
"text": ""
}
Cost
Free. No API key, no rate limits (within reason), no Apify credits.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |