Pp Judgeme

Judge.me — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the judgeme-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 judgeme --cli-only
   

2. Verify: judgeme-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.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/marketing/judgeme/cmd/judgeme-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.

Wrap the full Judge.me API while defending review workflows against the silent 10,000-row pagination loop. Sync once into a documented SQLite mirror, then export, count, and deduplicate published or internal review populations with provenance on every agent response.

When to Use This CLI

Use this CLI for Judge.me review synchronization, moderation inspection, export, storefront-widget access, and syndication-aware customer-language analysis. Prefer the local review mirror when exact corpus completeness or repeatable filtering matters.

Anti-triggers

Do not use this CLI for:

• Do not use this CLI to infer which syndicated product association is the true one.
• Do not use raw reviews index pagination as proof of full-corpus completeness.
• Do not use mutation commands without reviewing the dry-run and passing the explicit apply flag.

Unique Capabilities

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

Verified local corpus

• sync — Mirror the complete review corpus and refuse success when unique IDs do not equal Judge.me's live count.

  Use this before any analysis that depends on corpus completeness.

  judgeme-pp-cli sync --resources reviews --full --max-pages 1 --agent
  

• reviews export — Export explicit published, hidden, pending, or all populations as JSON or CSV.

  Use this to hand a bounded, provenance-labeled review slice to downstream analysis tools.

  judgeme-pp-cli reviews export --population published --rating 5 --csv --dry-run
  

Population integrity

• reviews populations — Count storefront-visible and internal moderation populations with unambiguous labels.

  Use this whenever published-vs-hidden population differences affect a report or decision.

  judgeme-pp-cli reviews populations --agent --dry-run
  

• reviews syndication — Find identical normalized review bodies attached to multiple products.

  Use this before attributing customer language to a specific SKU or product.

  judgeme-pp-cli reviews syndication --population all --min-products 2 --agent --dry-run
  

• reviews unique-bodies — Return one deterministic representative per normalized review body while retaining source row counts.

  Use this when independent customer voices matter more than API row count.

  judgeme-pp-cli reviews unique-bodies --population published --agent --dry-run
  

Command Reference

private-replies — Manage private replies

• judgeme-pp-cli private-replies — Create a private email reply to a Judge.me review privately via your app interface.

replies — Manage replies

• judgeme-pp-cli replies — Create a reply to a Judge.me review on the public Judge.me review widget via your app interface.

reviewers — Manage reviewers

• judgeme-pp-cli reviewers data-request — Data Request
• judgeme-pp-cli reviewers get — Get information of the reviewers such as name and email.
• judgeme-pp-cli reviewers update — Create or update a reviewer via your app interface.

reviews — You can use the reviews endpoints to access review information. Common use cases include:

• Synchronize and display reviews in your admin dashboard.

• Get event of new reviews (via webhook) to perform an action on your side.

• Let users manage reviews (publish/hide) on your side. *Note: these endpoints respond raw review information, which may include unpublished reviews, or review content that is not sanitized yet (so risks of XSS). To render review content on storefront, please use widget endpoints instead.

• judgeme-pp-cli reviews create — Create a web review in background

• judgeme-pp-cli reviews get — Get info of a specific review.

• judgeme-pp-cli reviews index — Get info of reviews of a product. If product_id is not provided, return all product and store reviews of that store.

• judgeme-pp-cli reviews reviewers-count — Get count of reviews for a specific product or reviewer.

• judgeme-pp-cli reviews update — Publish or hide a Judge.me review via your app interface.

settings — Manage settings

• judgeme-pp-cli settings — Get multiple settings values of the store in [Judge.me](http://judge.

shops — Manage shops

• judgeme-pp-cli shops comments-create — Create a checkout comment. Available in Checkout Comments app only.
• judgeme-pp-cli shops destroy — Uninstall the store from Judge.me
• judgeme-pp-cli shops get — Get the basic information of the store such as [Judge.me](http://judge.
• judgeme-pp-cli shops update — Update store information

webhooks — Subscribe to an event happens in Judge.me. Judge.me will send a POST request to the registered URL containing relevant information for each event.

Common webhook keys:

1. review/created or review/created_fail: to know when a review is created, or not.
2. review/updated: to know when a review is updated in Judge.me. In particular, when a review is:

• curated or mass curated
• pinned/featured in carousel
• moved to another product
• edited from admin or user profile
• verified review via request emails
• added/hidden/shown review photos from admin or user profile

3. Widgets update webhooks (e.g. widget/settings/updated): to know when Judge.me updates a widget. *Note: You can learn how to verify webhooks from Judge.me following this guide.

• judgeme-pp-cli webhooks bulk-create — Bulk Create
• judgeme-pp-cli webhooks create — Create a webhook in Judge.me with a key and a url. When an event associated with key happens, Judge.
• judgeme-pp-cli webhooks destroy — Delete
• judgeme-pp-cli webhooks get — Get
• judgeme-pp-cli webhooks index — Index
• judgeme-pp-cli webhooks update — Update

widgets — Manage widgets

• judgeme-pp-cli widgets all-reviews-count — Return a single total number of product and store reviews.
• judgeme-pp-cli widgets all-reviews-page — All Reviews Page is a dedicated page to showcase all product and store reviews all in one place.
• judgeme-pp-cli widgets all-reviews-rating — Return a single number of average rating of product reviews and store reviews.
• judgeme-pp-cli widgets checkout-comments — Return Checkout Comments widget for a product (for Checkout Comments app only).
• judgeme-pp-cli widgets featured-carousel — Reviews Carousel is usually placed on the homepage to showcase specific reviews featured by the store.
• judgeme-pp-cli widgets html-miracle — Return special HTML that helps show essential parts of widgets before the JS and CSS files are loaded.
• judgeme-pp-cli widgets preview-badge — Preview Badge is usually placed below product titles on product pages or inside product thumbnails on collection pages.
• judgeme-pp-cli widgets product-review — Review Widget is usually placed at the bottom of each product page, displaying all reviews of a product.
• judgeme-pp-cli widgets reviews-tab — Floating Reviews Tab display all product and store reviews via a floating button on any pages.
• judgeme-pp-cli widgets settings — Return widget settings of the shop, under HTML format, containing a <script> tag and a <style> tag.
• judgeme-pp-cli widgets shop-reviews-count — Return a single total number of store reviews.
• judgeme-pp-cli widgets shop-reviews-rating — Return a single number of average rating of store reviews.
• judgeme-pp-cli widgets verified-badge — Verified Reviews Count Badge displays the number of verified published reviews.

Freshness Contract

This printed CLI owns bounded freshness only for registered store-backed read command paths. In --data-source auto mode, those paths check sync_state and may run a bounded refresh before reading local data. --data-source local never refreshes. --data-source live reads the API and does not mutate the local store. Set JUDGEME_NO_AUTO_REFRESH=1 to skip the freshness hook without changing source selection.

Covered paths:

• judgeme-pp-cli reviews
• judgeme-pp-cli reviews get
• judgeme-pp-cli reviews list
• judgeme-pp-cli reviews search
• judgeme-pp-cli settings
• judgeme-pp-cli settings get
• judgeme-pp-cli settings list
• judgeme-pp-cli settings search
• judgeme-pp-cli webhooks
• judgeme-pp-cli webhooks get
• judgeme-pp-cli webhooks list
• judgeme-pp-cli webhooks search
• judgeme-pp-cli widgets
• judgeme-pp-cli widgets get
• judgeme-pp-cli widgets list
• judgeme-pp-cli widgets search
• judgeme-pp-cli widgets-all-reviews-count
• judgeme-pp-cli widgets-all-reviews-count get
• judgeme-pp-cli widgets-all-reviews-count list
• judgeme-pp-cli widgets-all-reviews-count search
• judgeme-pp-cli widgets-all-reviews-page
• judgeme-pp-cli widgets-all-reviews-page get
• judgeme-pp-cli widgets-all-reviews-page list
• judgeme-pp-cli widgets-all-reviews-page search
• judgeme-pp-cli widgets-all-reviews-rating
• judgeme-pp-cli widgets-all-reviews-rating get
• judgeme-pp-cli widgets-all-reviews-rating list
• judgeme-pp-cli widgets-all-reviews-rating search
• judgeme-pp-cli widgets-product-review
• judgeme-pp-cli widgets-product-review get
• judgeme-pp-cli widgets-product-review list
• judgeme-pp-cli widgets-product-review search

When JSON output uses the generated provenance envelope, freshness metadata appears at meta.freshness. Treat it as current-cache freshness for the covered command path, not a guarantee of complete historical backfill or API-specific enrichment.

Finding the right command

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

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

Narrow a published corpus for an agent

judgeme-pp-cli reviews export --population published --agent --select meta.source,meta.synced_at,results.id,results.rating,results.body

Return only storefront-visible review fields needed for downstream analysis.

Measure population differences

judgeme-pp-cli reviews populations --agent

Compare all, published, pending, and hidden review populations.

Find bundle syndication

judgeme-pp-cli reviews syndication --min-products 2 --agent

Identify one body hash associated with multiple products.

Export independent voices

judgeme-pp-cli reviews unique-bodies --population published --csv

Produce one representative row per normalized review body.

Auth Setup

Set JUDGEME_API_KEY to the private token and JUDGEME_SHOP_DOMAIN to the store's myshopify.com domain. The private token is sent only in the X-Api-Token header and is redacted from logs; it is never placed in a request URL.

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

  judgeme-pp-cli reviewers get 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

• Explicit retries — use --idempotent only when an already-existing create should count as success, and use --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:

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

Paths and state

Agents should treat the CLI's path resolver as part of the runtime contract:

• Use --home <dir> for one invocation, or set JUDGEME_HOME=<dir> to relocate all four path kinds under one root.

• Use per-kind env vars only when a specific kind must diverge: JUDGEME_CONFIG_DIR, JUDGEME_DATA_DIR, JUDGEME_STATE_DIR, JUDGEME_CACHE_DIR.

• Resolution order is per-kind env var, --home, JUDGEME_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.

• config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.

• Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.

• Run judgeme-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.

• For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:

  {
    "mcpServers": {
      "judgeme": {
        "command": "judgeme-pp-mcp",
        "env": {
          "JUDGEME_HOME": "/srv/judgeme"
        }
      }
    }
  }
  

Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use JUDGEME_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing JUDGEME_HOME, or doctor will not find credentials left under the former root.

Automatic learning

This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a flag_alias candidate, and a teach on a query family without a playbook auto-synthesizes a playbook_candidate from the session's journal. Your job is judgment only: recall first, act on surfaced candidates, teach the final answer, playbook amend when you observe a correction. You never record failures by hand.

Step 1: recall before any discovery

Before list/search/drill commands on a new user question, run:

judgeme-pp-cli recall "<user's question>" --agent

The response envelope:

{
  "query": "...",
  "normalized": "<normalized form>",
  "query_entities": ["..."],
  "found": true | false,
  "match_score": 0.0,
  "results": [
    { "resource_id": "...", "resource_type": "...", "venue": "...",
      "confidence": 2, "entity_match": "exact|partial|unknown",
      "source": "taught|preseed|pattern", "warnings": ["..."] }
  ],
  "mismatches": [ /* only when --debug-mismatches */ ],
  "warnings": [ /* top-level */ ],
  "candidates": [
    { "id": 12, "class": "flag_alias | playbook_candidate",
      "summary": "...", "sightings": 3, "last_seen": "...",
      "rationale": "...",
      "next_action": ["<trial command>", "judgeme-pp-cli learnings confirm 12"] }
  ],
  "playbook": {
    "query_family": "...",
    "playbook": {
      "steps": [ { "cmd": "<command with {slot} substitution>", "purpose": "..." } ],
      "entity_slots": ["$ENTITY"],
      "expected_tool_calls": 3
    },
    "slots_resolved": { "$ENTITY": { "token": "<live token>", "canonical": "<canonical>" } },
    "notes": "<workarounds + gotchas for this query family>"
  },
  "notes": "<duplicate surface for non-playbook callers>"
}

Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and learnings list and learnings candidates are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught.

Step 2: decision tree

Read candidates, playbook, notes, results[0], and warnings in that order:

if Candidates present (warnings include "candidates_present"):
    -> candidates are try-then-confirm, never facts. Follow each candidate's
       two-step next_action verbatim: run the trial command first, then run
       `learnings confirm <id>` only after the trial verified the behavior.
       Reject a wrong candidate with `learnings reject <id>`.
    -> NEVER re-teach something recall surfaced as a candidate; confirm or
       reject that candidate instead of teaching a duplicate.
    -> candidates ride alongside playbooks and resource hits, not instead of
       them; continue with the branches below after acting on them.

if Playbook present:
    -> READ Playbook.notes verbatim FIRST (workarounds + gotchas the CLI surface doesn't expose)
    -> replay Playbook.steps in order, substituting Playbook.slots_resolved entries
       for the entity slot tokens. If a step's slot is unresolved, fall back to
       discovery for that step only.
    -> the Playbook's expected_tool_calls is a budget; if you find yourself running
       materially more, record the divergence via `judgeme-pp-cli playbook amend`
       at end-of-session.

elif Notes present (no Playbook):
    -> read Notes verbatim before any discovery step; they carry known gotchas
       for this query family even when no structured choreography exists yet.

elif Found AND Results[0].EntityMatch == "exact" AND Results[0].Confidence >= 2:
    -> skip discovery; fetch live data for Results[*].ResourceID in parallel

elif Found AND Results[0].EntityMatch == "partial":
    -> candidate hint, NOT a hit; read the resource title to validate before trusting

elif (any row in Mismatches[] when --debug-mismatches was passed):
    -> treat as cold start; the stored learning is for a different entity
       (different canonical resolved from query_entities)

else:  // Found == false, no playbook, no notes
    -> cold start; run discovery normally; teach the answer afterward (Step 4).
       If the family has no playbook yet, that teach auto-synthesizes a
       playbook candidate from this session's journal - you do not need to
       record one by hand.

Playbook and Notes are orthogonal to the per-resource path. A recall response can carry both a Playbook AND a Results[] hit - use both: the Playbook tells you which choreography to run; the resource hits short-circuit specific steps. Default to skipping mismatches; pass --debug-mismatches only when investigating cold-start surprises.

Candidate judgment details: learnings confirm <id> prints the candidate's full payload before materializing it - check that the printed payload matches the behavior you verified. learnings reject <id> tombstones the derivation signature so the same candidate does not resurface. The envelope carries only the few candidates worth acting on now; judgeme-pp-cli learnings candidates lists the full open set.

Graceful degradation: if learnings confirm is an unknown command, you are driving an older binary - ignore the candidates guidance and follow the rest of the protocol.

Step 3: always read warnings

• low_confidence: row exists at confidence<2. Treat as a hint, not a skip-discovery hit.
• resource_not_in_store: the local store doesn't have the resource the learning points at. The match validator couldn't classify entities — direct-fetch and re-evaluate.
• cross_alias_match (per-result): the row was taught under a different alias and matched the live query's canonical via entity_lookups (e.g., a "USA" teach satisfying a "United States" recall). Trust the resource_id.
• similar_shape_different_entity:<canonical> (top-level): a structurally matching row exists but its canonical entity differs from the live query's. Treated as cold start; the warning carries the conflicting canonical as a hint, but the row is NOT promoted into Results.
• ambiguous_alias (top-level): a single query entity resolved to multiple canonicals (e.g., "Cards" → Arizona Cardinals + St. Louis Cardinals). Surface the ambiguity from context before committing to a resource.
• candidates_present (top-level): the envelope carries a candidates section. Handle it via the candidates branch in Step 2 before anything else.
• lookup_refresh_available (top-level): an entity in the query has no lookup row yet, but synced data could provide one. Run judgeme-pp-cli sync to refresh entity lookups.
• Top-level no_learnings_for_query_family: the table had no rows above the Jaccard floor. Pure cold start.

Step 4: teach & after finalizing your response - always

Teaching is unconditional. After resolving a query the store could not answer, background-teach the final resource mapping - no call-count threshold, no judging whether it was "worth" learning. The teach is the anchor of the loop: it triggers playbook synthesis for a family without a playbook, and same-referent phrasings fold into one family so near-duplicate teaches do not fragment the store. Fire it after assembling your user-facing response but BEFORE emitting it, with a shell & so the call returns immediately:

judgeme-pp-cli teach --query "<user's question>" --resource-type <type> --resource <id1> --resource <id2>
# (append shell `&` to background it)

Silent on success. Errors only land in teach.log under the resolved state dir. Teach the most specific resource - if the user asked a broad question and you walked through parent records to find the specific answer, teach the leaf id, not the parent. The CLI uses seeded entity_lookups for cross-alias resolution at recall time, so a teach under one alias (e.g., "Niners") satisfies future queries under another alias (e.g., "49ers", "San Francisco") automatically.

PII rule: teach the structural question with identifiers stripped - never include names, emails, phone numbers, account ids, or other personal identifiers in taught queries or notes. The CLI scans teach queries for obvious email/phone shapes and warns, but does not block; strip before teaching rather than relying on the warning.

Step 5: playbooks - optional flags, automatic synthesis

You do not need to decide whether a session "deserves" a playbook: a teach on a family without one auto-synthesizes a playbook_candidate from the session's journal, and the next session judges it via confirm/reject. Attach explicit playbook flags only when you already hold choreography worth recording verbatim - workarounds the CLI didn't surface (silently-dropped flags, undocumented params, pagination tricks, payload gotchas). Prefer the integrated one-call form - record the resource learning and the playbook in the same teach invocation:

# Common case: record both the resource learning AND the playbook in one call.
judgeme-pp-cli teach \
  --query "<user's question>" \
  --resource <id> \
  --playbook-file ~/playbooks/<shape>.json \
  --playbook-notes-file ~/playbooks/<shape>-notes.md
# (append shell `&` to background it)

# Alternate: playbook-only (no resource to record alongside).
judgeme-pp-cli teach-playbook \
  --query "<user's question>" \
  --playbook-file ~/playbooks/<shape>.json \
  --notes-file ~/playbooks/<shape>-notes.md

Playbook files are JSON with steps, entity_slots, expected_tool_calls. Notes files are markdown carrying the gotchas verbatim. File-free callers (MCP-only agents) pass the same content inline: --playbook-json and --playbook-notes on the integrated teach form, --playbook-json and --notes on teach-playbook. On the integrated teach form, the playbook flags are optional - omit them entirely for a resource-only teach. On the standalone teach-playbook form, at least one of the playbook and notes flags must be set; both empty is rejected. Playbooks are keyed on the structural query family (entities stripped) so a recipe taught from one entity-shaped query applies to every other query of the same shape, with slots_resolved binding the live query's canonical at recall time.

When you DO find a playbook on a future recall, treat it as ground truth: replay the steps with slots_resolved substitutions, skip the discovery that the choreography already documents, and read notes before any step.

Step 6: playbook amend & when your debug response identifies a correction

If your debug-protocol response identifies a concrete correction the notes or playbook should know — a workaround, an undocumented endpoint shape, a stale field name, observed schema drift, an empty-payload fallback — fire playbook amend BEFORE emitting your user-facing response. Same fire-and-forget posture as teach.

judgeme-pp-cli playbook amend \
  --query "<exact recall query string>" \
  --add-note "<your concrete correction>"
# (append shell `&` to background it)

What counts as worth amending: a behavior you OBSERVED this session that future-you would benefit from knowing. Examples worth amending:

• A workaround for a CLI surface that silently drops or misorders a flag.
• An undocumented endpoint shape (response wrapped in {meta, results}, payload nested two levels deeper than the docs claim).
• Observed schema drift (a field renamed, an index that shifted between seasons, a category label that the API now returns lower-cased).

What does NOT belong in notes:

• The year-specific or entity-specific answer to the user's question. That's the response, not a learning.
• Per-team / per-athlete / per-row data the playbook already retrieves at runtime.
• Statements that paraphrase what the existing notes already say.

The amend command appends to the family's existing notes with a timestamped marker ([amend YYYY-MM-DDTHH:MMZ]: <text>). Multiple amends accumulate; the audit trail is visible. If no playbook exists yet for the family, amend creates a notes-only one (so cold-start corrections still land).

PII discipline for amend notes

playbook amend notes are designed to potentially flow upstream as shared knowledge in future versions of the Printing Press. Keep them clean of user-identifying content so the upstream-contribution path stays open without retroactive scrubbing:

• Do NOT embed paths to user filesystems, personal API keys or tokens, user email addresses, user GitHub handles, or specific query histories tied to a single user.
• Acceptable: endpoint shapes, undocumented field names, API gotchas, observed schema drift, workarounds for CLI surfaces, generalizable pagination or retry tactics.

If a correction is only meaningful with user-specific context, it belongs in a personal note, not in the playbook amend.

Measuring the loop

judgeme-pp-cli learnings stats reports recall hit rate, teach-to-reuse, playbook resolution rate, and candidate confirm/reject counts from the local learn_events table. Rates are null until they have a denominator; everything stays on this machine. Use it to check whether the loop is earning its keep for this CLI.

Disabling learning

• --no-learn on a single command short-circuits both recall and the teach write path. Use for deterministic agent flows or tests that must not be affected by accumulated learnings.
• JUDGEME_NO_LEARN=true in the environment globally disables the pipeline.

Agent Feedback

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

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

Entries are stored locally as feedback.jsonl under the resolved data dir. They are never POSTed unless JUDGEME_FEEDBACK_ENDPOINT is set AND either --send is passed or JUDGEME_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 or recurring agent reuses the same saved flags while providing different input each run.

judgeme-pp-cli profile save briefing --json
judgeme-pp-cli --profile briefing reviewers get mock-value
judgeme-pp-cli profile list --json
judgeme-pp-cli profile show briefing
judgeme-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 judgeme-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/marketing/judgeme/cmd/judgeme-pp-mcp@latest
   

2. Register with Claude Code:

   claude mcp add judgeme-pp-mcp -- judgeme-pp-mcp
   

3. Verify: claude mcp list

Direct Use

1. Check if installed: which judgeme-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:

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

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