--- layout: tap site_name: hackernews tap_name: submit description: "Submit a story to Hacker News" intent: write columns: - status - url args: - name: title type: string - name: link type: string description: "URL to submit (optional if text provided)" - name: text type: string description: "Text body for Ask HN / Show HN (optional if link provided)" args_json: | {"title":{"type":"string"},"link":{"type":"string","description":"URL to submit (optional if text provided)"},"text":{"type":"string","description":"Text body for Ask HN / Show HN (optional if link provided)"}} health_json: | {"min_rows":1,"non_empty":[]} example_args: "" source_url: https://github.com/LeonTing1010/tap-skills/blob/main/showcase/hackernews/submit.plan.json license: MIT ---

## What it does

Submit a story to Hacker News

## 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/submit`

Terminal, once installed:

    tap run hackernews/submit

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

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

## 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/hot` | Hacker News top stories