AGENT SKILL

pp-wikipedia

Printing Press CLI for Wikipedia. Wikipedia REST API. Get article summaries, search, browse related topics, and access on-this-day events. No...

License 许可
Apache-2.0
最近更新
2026-05-22
Stars
★ 0
Forks
0

01 前言 Front Matter

name
pp-wikipedia
author
Hiten Shah
license
Apache-2.0
metadata
{ "openclaw": { "install": [ { "bins": [ "wikipedia-pp-cli" ], "kind": "go", "module": "github.com/mvanhorn/printing-press-library/library/media-and-entertainment/wikipedia/cmd/wikipedia-pp-cli" } ], "requires": { "bins": [ "wikipedia-pp-cli" ] } } }
description
Printing Press CLI for Wikipedia. Wikipedia REST API. Get article summaries, search, browse related topics, and access on-this-day events. No...
allowed-tools
Read Bash
argument-hint
<command> [args] | install cli|mcp

02 资源文件 55

03 SKILL.md 正文

Wikipedia — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the wikipedia-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:
    npx -y @mvanhorn/printing-press install wikipedia --cli-only
    
  2. Verify: wikipedia-pp-cli --version
  3. Ensure $GOPATH/bin (or $HOME/go/bin) is on $PATH.

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

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

If --version reports "command not found" after install, the install step did not put the binary on $PATH. Do not proceed with skill commands until verification succeeds.

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.

Command Reference

feed — Manage feed

  • wikipedia-pp-cli feed <day> — Returns events, births, deaths, or holidays that occurred on a given date.

page — Article content and metadata

  • wikipedia-pp-cli page get-html — Returns the full article body as styled HTML.
  • wikipedia-pp-cli page get-media — Returns images, videos, and other media files associated with an article.
  • wikipedia-pp-cli page get-random — Returns a random Wikipedia article summary.
  • wikipedia-pp-cli page get-summary — Returns a page summary including title, extract text, thumbnail, and coordinates.

Finding the right command

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

wikipedia-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.

Auth Setup

No authentication required.

Run wikipedia-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:

    wikipedia-pp-cli feed mock-value --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 — piped/agent consumers get pure JSON on stdout.

Agent Feedback

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

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

Entries are stored locally at ~/.wikipedia-pp-cli/feedback.jsonl. They are never POSTed unless WIKIPEDIA_FEEDBACK_ENDPOINT is set AND either --send is passed or WIKIPEDIA_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:

Sink Effect
stdout Default; write to stdout only
file:<path> Atomically write output to <path> (tmp + rename)
webhook:<url> POST the output body to the URL (application/json or application/x-ndjson when --compact)

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.

wikipedia-pp-cli profile save briefing --json
wikipedia-pp-cli --profile briefing feed mock-value
wikipedia-pp-cli profile list --json
wikipedia-pp-cli profile show briefing
wikipedia-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

Code Meaning
0 Success
2 Usage error (wrong arguments)
3 Resource not found
5 API error (upstream issue)
7 Rate limited (wait and retry)
10 Config error

Argument Parsing

Parse $ARGUMENTS:

  1. Empty, help, or --help → show wikipedia-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

  1. Install the MCP server:
    go install github.com/mvanhorn/printing-press-library/library/other/wikipedia-pp-cli/cmd/wikipedia-pp-mcp@latest
    
  2. Register with Claude Code:
    claude mcp add wikipedia-pp-mcp -- wikipedia-pp-mcp
    
  3. Verify: claude mcp list

Direct Use

  1. Check if installed: which wikipedia-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:
    wikipedia-pp-cli <command> [subcommand] [args] --agent
    
  4. If ambiguous, drill into subcommand help: wikipedia-pp-cli <command> --help.

04 同仓库更多 Skills

shekerkamma
shekerkamma/peopletech-marketplace

pp-trigger-dev

Every Trigger.dev management endpoint, plus offline FTS over runs, span-cost rollups, and zombie-schedule detection no other tool gives you. Trigger phrases: `trigger.dev failed runs`, `trigger.dev cost rollup`, `trigger.dev schedule health`, `audit trigger.dev env vars`, `watch trigger.dev failures`, `use trigger-dev`, `run trigger-dev`.

★ 0
shekerkamma
shekerkamma/peopletech-marketplace

pp-substack

Run your Substack growth loop from the command line — publish, schedule, engage, and measure with cross-table... Trigger phrases: `post a substack note`, `schedule a week of substack notes`, `find substack swap partners`, `which of my notes drove subs`, `what's my engagement reciprocity`, `voice-match a substack note`, `best time to post on substack`, `use substack`, `run substack`.

★ 0
shekerkamma
shekerkamma/peopletech-marketplace

pp-slack

Slack workspace CLI for the terminal. Send messages, search channels and DMs, list conversations, get user/bot/emoji info, analyze channel health, find stale threads, and sync the workspace locally for fast offline queries. Two auth surfaces coexist: SLACK_BOT_TOKEN (xoxb-, for workspace-wide read + post) and SLACK_USER_TOKEN (xoxp-, for user-scoped actions like DM history or search). Use when the user asks to send a Slack message, search Slack, check channel activity, summarize a digest, find who's on a team, find stale threads, analyze channel health, list users / emoji / reminders / pinned items, or wants offline-capable Slack queries.

★ 0
shekerkamma
shekerkamma/peopletech-marketplace

pp-scrape-creators

Every Scrape Creators endpoint, plus offline search, cross-platform compounding, and a local store no other Scrape Creators tool ships with. Trigger phrases: `scrape creators`, `tiktok profile`, `instagram profile`, `youtube channel`, `facebook ad library`, `creator on every platform`, `social media transcript search`, `use scrape-creators`, `run scrape-creators`.

★ 0
shekerkamma
shekerkamma/peopletech-marketplace

pp-postman-explore

The CLI for the public API directory at postman.com/explore — search, rank, and watch community-contributed Postman Collections, agent-native and offline. Trigger phrases: `find a postman collection for`, `what postman collection should i fork for`, `is there a postman collection for`, `browse postman api network`, `compare postman publishers`, `what changed on the postman network`, `use postman-explore`, `run postman-explore`.

★ 0
shekerkamma
shekerkamma/peopletech-marketplace

pp-podscan

Search 51M+ podcast episodes and 4.4M+ podcasts via Podscan — full transcripts, AI-extracted entities, mentions, and brand-safety analysis. Trigger phrases: `search podcast transcripts`, `find podcasts mentioning`, `who's talked about <topic> on podcasts`, `use podscan`.

★ 0