pp-drudgereport

name: pp-drudgereport description: "Drudge Report in your terminal, with the editorial signal (splash, red, slot, tenure) the live page broadcasts but... Trigger phrases: what's on drudge, drudge splash, drudge breaking, what changed on drudge, drudge tenure, drudge sources this week, use drudgereport, run drudgereport." author: "Matt Van Horn" license: "Apache-2.0" argument-hint: " [args] | install cli|mcp" allowed-tools: "Read Bash" metadata: openclaw: requires: bins: - drudgereport-pp-cli

Drudge Report — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the drudgereport-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install drudgereport --cli-only
   

2. Verify: drudgereport-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer):

go install github.com/mvanhorn/printing-press-library/library/media-and-entertainment/drudgereport/cmd/drudgereport-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

When to Use This CLI

Reach for this CLI when the task is 'what is Drudge featuring' or 'how has Drudge framed X over time.' It is read-only, the local SQLite store rewards repeated sync runs with deeper analytics, and the agent surface returns bounded JSON. Not the right tool for live breaking news outside Drudge's curation.

When Not to Use This CLI

Do not activate this CLI for requests that require creating, updating, deleting, publishing, commenting, upvoting, inviting, ordering, sending messages, booking, purchasing, or changing remote state. This printed CLI exposes read-only commands for inspection, export, sync, and analysis.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Editorial signal-aware reading

• splash — Just the current center-slot splash headline with image, outbound URL, red flag, and how long it has been on splash.

  When an agent is asked 'what's on Drudge right now?' this is the one-shot bounded answer; no HTML soup to re-parse.

  drudgereport splash --json
  

• breaking — Every headline currently set in red by Drudge's editor, ordered by slot importance.

  Tells an agent the difference between 'on Drudge' and 'Drudge thinks this is breaking,' a high-signal filter at zero token cost.

  drudgereport breaking --json
  

• headlines — All current headlines ranked by composite editorial weight (slot + red + image), not by chronology.

  Returns Drudge in priority order with bounded payloads agents can pipe.

  drudgereport headlines --limit 10 --json --select title,slot,is_red,url
  

Local state that compounds

• tail — Slot transitions and color changes between consecutive snapshots: promoted to splash, demoted from splash, went red, disappeared, appeared.

  Lets an agent answer 'what changed on Drudge?' without re-fetching the page or diffing screenshots.

  drudgereport tail --since 6h --json
  

• tenure — How long the current splash has been the splash, plus the all-time longest-tenured splash leaderboard.

  Distinguishes 'breaking right now' from 'Drudge wants this to stick,' a question agents and journalists both need.

  drudgereport tenure --history --json
  

• sources — Outbound-domain frequency leaderboard over a window with rising/falling delta vs the prior window, optionally crosstabbed by slot.

  Surfaces editorial bent shifts week over week; high-leverage for media analysts and agents writing about narrative pickup.

  drudgereport sources --window 168h --by-slot --json
  

• on-date — Reconstruct Drudge at any past timestamp the CLI has observed: splash, red items, ranked headlines as of that moment.

  Answers 'what was Drudge leading with when X happened?' — a question the live site cannot.

  drudgereport on-date 2026-04-15T08:30 --json
  

• bent — Ratio of red items by outbound domain over a window: which outlets Drudge tends to break vs which he tends to merely column.

  Quantifies a previously gut-feel media-criticism observation; agents writing media-analysis copy can cite numbers.

  drudgereport bent --window 168h --json
  

• story — Every slot_event for one story_id ordered by timestamp: when it appeared, where it moved, when it went red, when it dropped, total tenure.

  Lets an agent reconstruct one story's editorial life on Drudge, useful for retrospective newsletter analysis.

  drudgereport story abc123 --json
  

Agent-native plumbing

• digest — One-pager: splash count, longest-tenured splash, top 5 outbound domains, biggest red-surge stories over the week.

  Replaces the 'what did Drudge feature this week' graf that journalists currently assemble by hand.

  drudgereport digest --week --json
  

Command Reference

feed — Unofficial community RSS feed mirror of Drudge Report (feedpress.me). Used as a cross-check source for pubDate and pre-grouped Related stories.

• drudgereport-pp-cli feed — Fetch the unofficial RSS feed mirror. Items embed position labels (Main headline / First column / Second column) in...

page — Drudge Report's curated home page. Most users should run sync then splash/headlines/breaking; the raw fetch is exposed for debugging.

• drudgereport-pp-cli page — Fetch the raw drudgereport.com HTML page. The CLI's parser turns this into ranked headlines with slot, is_red,...

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

drudgereport-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Recipes

Just the splash, for a daily briefing

drudgereport splash --json --select title,url,image_url,is_red,splash_tenure_seconds

Bounded payload with every signal an agent needs to summarize Drudge's lead in one sentence.

What's red right now

drudgereport breaking --json --select title,url,slot

Every red headline with its slot; lets the agent distinguish splash-red from column-red without re-parsing the page.

Top 10 ranked headlines with select-narrowing

drudgereport headlines --limit 10 --json --select title,slot,is_red,url,outbound_domain

Returns the priority-ordered list of stories in agent-friendly shape with only the fields needed for downstream framing.

What changed in the last 6 hours

drudgereport tail --since 6h --json

Slot_event rows for promotions, demotions, color changes, and disappearances; cheaper than diffing two fetches.

Which outlets Drudge leaned on this week

drudgereport sources --window 7d --by-slot --json

Outbound-domain leaderboard split by slot (splash vs red vs column) over the trailing 7 days, with rising/falling delta vs the prior 7 days.

Auth Setup

No authentication required.

Run drudgereport-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  drudgereport-pp-cli feed --agent --select id,name,status
  

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.

Agent Feedback

When you (or the agent) notice something off about this CLI, record it:

drudgereport-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
drudgereport-pp-cli feedback --stdin < notes.txt
drudgereport-pp-cli feedback list --json --limit 10

Entries are stored locally at ~/.drudgereport-pp-cli/feedback.jsonl. They are never POSTed unless DRUDGEREPORT_FEEDBACK_ENDPOINT is set AND either --send is passed or DRUDGEREPORT_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

Output Delivery

Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

Named Profiles

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

drudgereport-pp-cli profile save briefing --json
drudgereport-pp-cli --profile briefing feed
drudgereport-pp-cli profile list --json
drudgereport-pp-cli profile show briefing
drudgereport-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.

Exit Codes

Argument Parsing

Parse $ARGUMENTS:

1. Empty, help, or --help → show drudgereport-pp-cli --help output
2. Starts with install → ends with mcp → MCP installation; otherwise → see Prerequisites above
3. Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:

claude mcp add drudgereport-pp-mcp -- drudgereport-pp-mcp

Verify: claude mcp list

Direct Use

1. Check if installed: which drudgereport-pp-cli If not found, offer to install (see Prerequisites at the top of this skill).
2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
3. Execute with the --agent flag:

   drudgereport-pp-cli <command> [subcommand] [args] --agent
   

4. If ambiguous, drill into subcommand help: drudgereport-pp-cli <command> --help.