--- layout: tap site_name: hackernews tap_name: hot description: "Hacker News top stories" intent: read columns: [] args: [] args_json: | {} health_json: | {"min_rows":10,"non_empty":["title","score"]} example_args: "" source_url: https://github.com/LeonTing1010/tap-skills/blob/main/showcase/hackernews/hot.plan.json license: MIT ---

## What it does

Hacker News top stories

## Install Taprun once

Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:

    brew install LeonTing1010/tap/taprun
    tap mcp connect

Or drop this into your `claude_desktop_config.json` (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):

    {
      "mcpServers": {
        "tap": {
          "command": "tap",
          "args": ["mcp", "start"]
        }
      }
    }

## Call `hackernews/hot`

Terminal, once installed:

    tap run hackernews/hot

From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:

    tap.run({ site: "hackernews", name: "hot" })

## Why compile it once

This plan was forged once — the AI read `hackernews`, picked stable structural addresses (JSON-LD, ARIA, RSS, or declared API endpoints, in that priority order), and saved them to a `.plan.json`. Every replay since then has used zero LLM tokens. When `hackernews` ships a site change that breaks the extraction, `tap verify` surfaces it before your data goes stale — not after your pipeline silently writes garbage for a week.

## Related hackernews taps

tap | description
--- | ---
`hackernews/submit` | Submit a story to Hacker News