Pp Logitech Docs

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/devices/logitech-docs/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Logitech — Printing Press CLI

Prerequisites: Install the CLI

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

2. Verify: logitech-docs-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/devices/logitech-docs/cmd/logitech-docs-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.

support.logi.com is a Zendesk portal with a clean JSON API hiding behind it. logitech-docs turns 33k+ reference documents into a greppable local index: find specs by product, pull install guides, and full-text search inside manuals without touching a browser.

When to Use This CLI

When an agent or technician needs a Logitech spec sheet, install guide, or manual without opening support.logi.com.

Anti-triggers

Do not use this CLI for:

• Do not use for controlling Logitech devices or G HUB
• Do not use for live support chat or warranty claims
• Do not use for Logitech account management

Unique Capabilities

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

Doc discovery

• docs — Search Logitech support docs by friendly type: spec sheet, manual, install guide, FAQ, download, warranty.

  Agents reach for this instead of guessing Zendesk label strings for spec sheets vs install guides.

  logitech-docs-pp-cli docs spec "MeetUp" --agent

• download — Resolve download01.logi.com file links in an article and fetch them (with --dry-run and local cache).

  Scriptable downloads of firmware/software/PDF manuals without clicking through the site.

  logitech-docs-pp-cli download 360023302754 --dry-run

Local state that compounds

• find — Full-text search inside synced manuals and spec sheets from the local store.

  Search manuals offline, across a product family at once, without the Cloudflare-fronted site.

  logitech-docs-pp-cli find "camera dimensions" --agent

• compare — Side-by-side spec comparison between two products from synced spec sheets.

  AV integrators compare dimensions and compatibility across products before quoting.

  logitech-docs-pp-cli compare "MeetUp" "Rally Bar" --agent

Command Reference

articles — Support articles: manuals, spec sheets, install guides, FAQs, downloads

• logitech-docs-pp-cli articles by-section — List articles in one section (server-side scoped)
• logitech-docs-pp-cli articles get — Get a single article including its HTML body
• logitech-docs-pp-cli articles list — List articles (filter by label)
• logitech-docs-pp-cli articles search — Search articles by text

Article listing is cursor-paginated (--page-size, --cursor, or --all to walk every page). There is no --section-id filter on articles list: the upstream API silently ignores a section_id query param on the flat list and returns the whole corpus, so section scoping goes through articles by-section <section-id>, which uses the server-side scoped path.

Syncing articles requires sections. sync reaches articles by walking each section, so articles is a dependent of sections. Plain sync handles this: it syncs sections first, then fans out across them. sync --resources sections also covers articles, because naming a parent cascades to its dependents.

sync --resources articles against a database that has never synced sections fetches nothing — there are no parent rows to walk. It reports this as a sync_warning with reason dependent_parent_table_empty and exits non-zero, so it will not look like a successful empty sync. Run plain sync first.

Deletions are not pruned. Articles removed upstream stay in the local store even after sync --full; reconciliation is not wired up for this resource.

categories — Support categories (Mice and Pointers, Keyboards, Webcams, Gaming, ...)

• logitech-docs-pp-cli categories — List support categories

sections — Product-family sections within the support site

• logitech-docs-pp-cli sections — List sections (optionally filtered by category)

Finding the right command

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

logitech-docs-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

Grab a spec sheet

logitech-docs-pp-cli docs spec "MeetUp" --select title,html_url

narrow a large search response to just name and link

Full-text search inside manuals

logitech-docs-pp-cli docs manual "pairing" --agent --select title,html_url

live full-text search across manual bodies, narrowed for agents

Preview a download

logitech-docs-pp-cli download 360023302754 --dry-run

see the resolved file URL before fetching

Auth Setup

No authentication required. The support site and its Help Center API are public.

Run logitech-docs-pp-cli doctor to verify setup.

Agent Mode

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

• 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:

  logitech-docs-pp-cli articles list --agent --select id,name,title

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

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 LOGITECH_DOCS_HOME=<dir> to relocate all four path kinds under one root.

• Use per-kind env vars only when a specific kind must diverge: LOGITECH_DOCS_CONFIG_DIR, LOGITECH_DOCS_DATA_DIR, LOGITECH_DOCS_STATE_DIR, LOGITECH_DOCS_CACHE_DIR.

• Resolution order is per-kind env var, --home, LOGITECH_DOCS_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 logitech-docs-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": {
      "logitech-docs": {
        "command": "logitech-docs-pp-mcp",
        "env": {
          "LOGITECH_DOCS_HOME": "/srv/logitech-docs"
        }
      }
    }
  }

Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use LOGITECH_DOCS_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 LOGITECH_DOCS_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:

logitech-docs-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>", "logitech-docs-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 `logitech-docs-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; logitech-docs-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 logitech-docs-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.