Amazon Seller — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the

amazon-seller-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 amazon-seller --cli-only

Verify:
```
amazon-seller-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.23+):

bash

go install github.com/mvanhorn/printing-press-library/library/commerce/amazon-seller/cmd/amazon-seller-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.

Command Reference

catalog — Read Catalog Items API item data.

```
amazon-seller-pp-cli catalog get
```
— Get one catalog item by ASIN.
```
amazon-seller-pp-cli catalog search
```
— Search catalog items. Provide marketplaceIds plus one valid search mode such as keywords or identifiers with...

fba-inventory — Inspect Fulfillment by Amazon inventory summaries.

```
amazon-seller-pp-cli fba-inventory
```
— List FBA inventory summaries. For North America marketplace-level inventory, pass granularityType=Marketplace,...

listings — Read Listings Items API data for seller SKUs.

```
amazon-seller-pp-cli listings get
```
— Get one listing item by seller ID and SKU.
```
amazon-seller-pp-cli listings search
```
— Search listing items for a seller.

orders — Search and inspect Orders API v2026-01-01 order records.

```
amazon-seller-pp-cli orders get
```
— Get one Orders API v2026-01-01 order.
```
amazon-seller-pp-cli orders search
```
— Search orders. Provide exactly one of createdAfter or lastUpdatedAfter; Amazon returns 400 for invalid combinations.

reports — Create reports, poll report status, and inspect report document metadata.

```
amazon-seller-pp-cli reports create
```
— Create a report request. Prefer --stdin for JSON bodies so marketplaceIds remains a JSON array and reportOptions...
```
amazon-seller-pp-cli reports document
```
— Get report document metadata and the presigned download URL. This command does not download or open the document.
```
amazon-seller-pp-cli reports get
```
— Get one report by report ID. This is the manual polling endpoint for report processing status.
```
amazon-seller-pp-cli reports list
```
— List reports. If nextToken is set, Amazon requires it to be the only query parameter; pass no other filters with...

sellers — Verify seller authorization and list marketplace participations.

```
amazon-seller-pp-cli sellers
```
— List marketplace participations for the authorized seller account.

Finding the right command

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

bash

amazon-seller-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

Self-authorize your private application in the provider console, export the OAuth client ID, OAuth client secret, and refresh token, then run doctor:

bash

export SP_API_LWA_CLIENT_ID="<client-id>"
export SP_API_LWA_CLIENT_SECRET="<client-secret>"
export SP_API_REFRESH_TOKEN="<refresh-token>"
amazon-seller-pp-cli doctor

The CLI exchanges the refresh token for an access token on first live use and caches the access token locally.

Run

amazon-seller-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
```
amazon-seller-pp-cli catalog get <asin> --marketplace-ids ATVPDKIKX0DER --agent --select asin,attributes,summaries
```
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

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:

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

Entries are stored locally at

~/.amazon-seller-pp-cli/feedback.jsonl

. They are never POSTed unless

AMAZON_SELLER_FEEDBACK_ENDPOINT

is set AND either

--send

is passed or

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

amazon-seller-pp-cli profile save briefing --json
amazon-seller-pp-cli --profile briefing sellers marketplaces
amazon-seller-pp-cli profile list --json
amazon-seller-pp-cli profile show briefing
amazon-seller-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
```
amazon-seller-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 server:

bash

go install github.com/mvanhorn/printing-press-library/library/commerce/amazon-seller/cmd/amazon-seller-pp-mcp@latest

bash

claude mcp add amazon-seller-pp-mcp -- amazon-seller-pp-mcp

Verify:
```
claude mcp list
```

Direct Use

Check if installed:
```
which amazon-seller-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

amazon-seller-pp-cli <command> [subcommand] [args] --agent

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

pp-amazon-seller

NPX Install

Tags

SKILL.md Content

Amazon Seller — 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