# Pp Linq > Printing Press CLI for Linq. Community-curated OpenAPI 3.1 blueprint for the Linq Partner API, derived from https://docs.linqapp. - Skill: `mvanhorn-printing-press-libra/pp-linq` (Agent Skill) - Install (CLI): `npx skillmds add mvanhorn-printing-press-libra/pp-linq` - Raw SKILL.md: https://api.skillmd.com/api/skills/mvanhorn-printing-press-libra/pp-linq/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Integrations & APIs - License: Apache-2.0 - Author: mvanhorn (https://skillmd.com/u/mvanhorn-printing-press-libra) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/mvanhorn-printing-press-libra/pp-linq --- # Linq — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `linq-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: ```bash npx -y @mvanhorn/printing-press-library install linq --cli-only ``` 2. Verify: `linq-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: ```bash go install github.com/mvanhorn/printing-press-library/library/social-and-messaging/linq/cmd/linq-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. Community-curated OpenAPI 3.1 blueprint for the Linq Partner API, derived from https://docs.linqapp.com/api and cross-checked against github.com/linq-team/linq-go/api.md. The blueprint is generic and contains no private deployment-specific behavior or examples. ## Generic Linq messaging experience Use these commands for ordinary Linq rich messaging. Core workflow: ```bash linq-pp-cli compose preview --text "Congrats!" --effect screen:confetti --decorate 0:8:bold --preferred-service iMessage --agent linq-pp-cli compose send --chat-id ch_123 --text "Congrats!" --effect screen:confetti --idempotency-key req_123 --agent --dry-run ``` Typing indicators: ```bash linq-pp-cli typing start --chat-id ch_123 --agent --dry-run linq-pp-cli typing stop --chat-id ch_123 --agent --dry-run linq-pp-cli typing pulse --chat-id ch_123 --dwell 800ms --agent --dry-run tail -f ./debug/linq-webhooks.ndjson | linq-pp-cli typing watch --agent linq-pp-cli webhooks add-event sub_123 chat.typing_indicator.started chat.typing_indicator.stopped --agent --dry-run linq-pp-cli webhooks doctor --subscription-id sub_123 --agent linq-pp-cli capability check +15551234567 --agent ``` Effects and decorations: ```bash linq-pp-cli effects list --agent linq-pp-cli effects preview --text "Hello world" --decorate 0:5:bold --decorate 6:11:shake --agent ``` Attachments: ```bash linq-pp-cli attachments plan --file ./photo.jpg --agent linq-pp-cli attachments upload --file ./photo.jpg --agent --dry-run linq-pp-cli attachments send-url --chat-id ch_123 --url https://cdn.example/photo.jpg --text "Photo attached" --agent --dry-run linq-pp-cli attachments send-id --chat-id ch_123 --attachment-id att_123 --text "Photo attached" --agent --dry-run linq-pp-cli attachments audit-url https://cdn.example/photo.jpg --agent linq-pp-cli attachments cleanup --attachment-id att_123 --agent --dry-run ``` Rich link previews: ```bash linq-pp-cli link-preview audit https://example.com --agent linq-pp-cli link-preview send --chat-id ch_123 --url https://example.com --agent --dry-run linq-pp-cli link-preview metadata https://example.com --agent --dry-run ``` Reactions and contact sharing: ```bash linq-pp-cli react add --message-id msg_123 --type like --agent --dry-run linq-pp-cli react remove --message-id msg_123 --type like --agent --dry-run linq-pp-cli react custom --message-id msg_123 --emoji "tada" --agent --dry-run linq-pp-cli contact-share preflight --chat-id ch_123 --from +16282893046 --agent --dry-run linq-pp-cli contact-share send --chat-id ch_123 --from +16282893046 --yes --agent --dry-run ``` Protocol rules to preserve: typing, effects, and decorations are iMessage-only; inbound typing indicators are push-only webhook events and this CLI only manages subscriptions or inspects captured streams; rich previews and reactions work on iMessage/RCS and simplify on SMS; link preview parts must be the only part; first outbound chat openers must not contain links. For inbound typing awareness, enable both typing events on the target subscription with a dry-run first: ```bash linq-pp-cli webhooks add-event sub_123 chat.typing_indicator.started chat.typing_indicator.stopped --agent --dry-run linq-pp-cli webhooks doctor --subscription-id sub_123 --agent ``` `webhook-subscriptions update-awebhook-subscription` sends a full replacement `subscribed_events` array for that field, not a delta. Prefer `webhooks add-event` / `remove-event` so the CLI fetches the current set, validates event names against `webhook-events`, computes the union/diff, and sends the correct replacement array. ## Command Reference **attachments** — Plan, upload, audit, send, and clean up attachments - `linq-pp-cli attachments plan` — Decide direct URL versus pre-upload based on local file size. - `linq-pp-cli attachments upload` — Request a pre-upload URL and upload file bytes. - `linq-pp-cli attachments send-url` — Send a public HTTPS media URL in a message. - `linq-pp-cli attachments send-id` — Send a pre-uploaded attachment ID in a message. - `linq-pp-cli attachments audit-url` — Check HTTPS and attachment lifecycle guidance for a media URL. - `linq-pp-cli attachments cleanup` — Delete an owned Linq attachment. - `linq-pp-cli attachments delete-an` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli attachments get-metadata` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli attachments pre-upload-afile` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **capability** — Check whether an address can use iMessage, RCS, or SMS - `linq-pp-cli capability check
...` — Resolve addresses to `imessage`, `rcs`, or `sms`; masks the full address in output and reports typing/effects/read receipt support. - `linq-pp-cli capability check-imessage` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli capability check-rcscapability` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **chats** — Manage chats - `linq-pp-cli chats create-anew` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli chats get-achat-by-id` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli chats list-all` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli chats update-achat` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **contact-card** — Manage iMessage contact cards for sending phone numbers - `linq-pp-cli contact-card get` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli contact-card create --phone-number +15551234567 --first-name Acme --last-name Support --image-url https://cdn.example.com/contact-card.jpg` — Create a contact card for a sending phone number. `setup` remains available as an alias. - `linq-pp-cli contact-card update --phone-number +15551234567 --first-name Acme --last-name Support` — Update an existing active contact card. Use `--stdin` for raw JSON bodies. **messages** — Manage messages - `linq-pp-cli messages delete-amessage-from-system` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli messages edit-the-content-of-amessage-part` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli messages get-amessage-by-id` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **phone-numbers** — Manage phone numbers - `linq-pp-cli phone-numbers` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **phonenumbers** — Manage phonenumbers - `linq-pp-cli phonenumbers` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **webhook-events** — Manage webhook events - `linq-pp-cli webhook-events` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **webhook-subscriptions** — Manage webhook subscriptions - `linq-pp-cli webhook-subscriptions create-anew` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli webhook-subscriptions delete-awebhook-subscription` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli webhook-subscriptions get-awebhook-subscription-by-id` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli webhook-subscriptions list-all` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. - `linq-pp-cli webhook-subscriptions update-awebhook-subscription` — Source: https://docs.linqapp.com/api. Cross-check: github.com/linq-team/linq-go/api.md. **webhooks** — Manage webhook subscriptions safely - `linq-pp-cli webhooks list` — List subscriptions with target URLs and subscribed event sets. - `linq-pp-cli webhooks show ` — Show one subscription with its subscribed event set. - `linq-pp-cli webhooks add-event ...` — Fetch current events, validate requested events, union them, and send the full replacement `subscribed_events` array. - `linq-pp-cli webhooks remove-event ...` — Fetch current events, validate requested events, remove them, and send the full replacement `subscribed_events` array. - `linq-pp-cli webhooks set-events ...` — Explicitly replace the subscription's event set. - `linq-pp-cli webhooks doctor` — Compare subscriptions against expected events and warn when inbound typing events are missing. ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash linq-pp-cli which "" ``` `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 Run `linq-pp-cli auth setup` for the URL and steps to obtain a token (add `--launch` to open the URL). Then store it: ```bash linq-pp-cli auth set-token YOUR_TOKEN_HERE ``` Or set `LINQ_API_V3_API_KEY` as an environment variable. Run `linq-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 linq-pp-cli contact-card get --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": } ``` 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. ## Agent Feedback When you (or the agent) notice something off about this CLI, record it: ``` linq-pp-cli feedback "the --since flag is inclusive but docs say exclusive" linq-pp-cli feedback --stdin < notes.txt linq-pp-cli feedback list --json --limit 10 ``` Entries are stored locally at `~/.local/share/linq-pp-cli/feedback.jsonl`. They are never POSTed unless `LINQ_FEEDBACK_ENDPOINT` is set AND either `--send` is passed or `LINQ_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 `. 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:` | Atomically write output to `` (tmp + rename) | | `webhook:` | 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. ``` linq-pp-cli profile save briefing --json linq-pp-cli --profile briefing contact-card get linq-pp-cli profile list --json linq-pp-cli profile show briefing linq-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`: 1. **Empty, `help`, or `--help`** → show `linq-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: ```bash go install github.com/mvanhorn/printing-press-library/library/social-and-messaging/linq/cmd/linq-pp-mcp@latest ``` 2. Register with Claude Code: ```bash claude mcp add linq-pp-mcp -- linq-pp-mcp ``` 3. Verify: `claude mcp list` ## Direct Use 1. Check if installed: `which linq-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: ```bash linq-pp-cli [subcommand] [args] --agent ``` 4. If ambiguous, drill into subcommand help: `linq-pp-cli --help`.