Podscan — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the

podscan-pp-cli

binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

Install via the Printing Press installer:

bash

npx -y @mvanhorn/printing-press install podscan --cli-only

Verify:
```
podscan-pp-cli --version
```
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):

bash

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

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

Podscan REST API — search 51M+ podcast episodes and 4.4M+ podcasts. Full transcripts, AI-extracted entities, mentions, brand-safety analysis.

Command Reference

alerts — Manage alerts

```
podscan-pp-cli alerts create
```
— Create a new alert
```
podscan-pp-cli alerts delete
```
— Delete an alert
```
podscan-pp-cli alerts get
```
— Get an alert
```
podscan-pp-cli alerts list
```
— List configured alerts

categories — Manage categories

```
podscan-pp-cli categories
```
— List all podcast categories

episodes — Manage episodes

```
podscan-pp-cli episodes get
```
— Get an episode by ID
```
podscan-pp-cli episodes search
```
— Search episodes by transcript content

exports — Manage exports

```
podscan-pp-cli exports download
```
— Download an export file
```
podscan-pp-cli exports list-episode
```
— List daily episode export files
```
podscan-pp-cli exports list-podcast
```
— List podcast catalog export files

podcasts — Manage podcasts

```
podscan-pp-cli podcasts get
```
— Get a podcast by ID
```
podscan-pp-cli podcasts search
```
— Search podcasts by name or description

Finding the right command

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

bash

podscan-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

means at least one match; exit code

means no confident match — fall back to

--help

or use a narrower query.

Auth Setup

Store your access token:

bash

podscan-pp-cli auth set-token YOUR_TOKEN_HERE

Or set

PODSCAN_BEARER_AUTH

as an environment variable.

Run

podscan-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:
bash
```
podscan-pp-cli alerts list --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
Explicit retries — use
```
--idempotent
```
only when an already-existing create should count as success, and
```
--ignore-missing
```
only when a missing delete target should count as success

Response envelope

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

json

{
  "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:

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

Entries are stored locally at

~/.podscan-pp-cli/feedback.jsonl

. They are never POSTed unless

PODSCAN_FEEDBACK_ENDPOINT

is set AND either

--send

is passed or

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

podscan-pp-cli profile save briefing --json
podscan-pp-cli --profile briefing alerts list
podscan-pp-cli profile list --json
podscan-pp-cli profile show briefing
podscan-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
4	Authentication required
5	API error (upstream issue)
7	Rate limited (wait and retry)
10	Config error

Argument Parsing

Parse

$ARGUMENTS

Empty,
help
, or
--help
→ show
```
podscan-pp-cli --help
```
output
Starts with
install
→ ends with
```
mcp
```
→ MCP installation; otherwise → see Prerequisites above
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:

bash

claude mcp add podscan-pp-mcp -- podscan-pp-mcp

Verify:

claude mcp list

Direct Use

Check if installed:
```
which podscan-pp-cli
```
If not found, offer to install (see Prerequisites at the top of this skill).
Match the user query to the best command from the Unique Capabilities and Command Reference above.

Execute with the

--agent

flag:

bash

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

If ambiguous, drill into subcommand help:
```
podscan-pp-cli <command> --help
```
.

pp-podscan

NPX Install

Tags

SKILL.md Content

Podscan — Printing Press CLI

Prerequisites: Install the CLI

Command Reference

Finding the right command

Auth Setup

Agent Mode

Response envelope

Agent Feedback

Output Delivery

Named Profiles

Exit Codes

Argument Parsing

MCP Server Installation

Direct Use