--- name: pp-raindrop description: "Printing Press CLI for Raindrop. Complete REST API specification for Raindrop.io bookmark management" author: "srijits" license: "Apache-2.0" argument-hint: " [args] | install cli|mcp" allowed-tools: "Read Bash" metadata: openclaw: requires: bins: - raindrop-pp-cli install: - kind: go bins: [raindrop-pp-cli] module: github.com/mvanhorn/printing-press-library/library/productivity/raindrop/cmd/raindrop-pp-cli --- # Raindrop — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `raindrop-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 raindrop --cli-only ``` 2. Verify: `raindrop-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/productivity/raindrop/cmd/raindrop-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. Use every documented bookmark, collection, tag, highlight, file, import, export and backup operation from one Go CLI. SQLite sync powers historical diffs, resumable review, explainable related-bookmark search and crash-safe automation while the matching MCP server exposes the same command tree to agents. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Local state that compounds - **`sync`** — Mirror bookmarks, collections, tags and highlights for instant offline search. _Use before local analysis or when repeated remote scans would waste rate limit._ ```bash raindrop sync --agent --home /tmp/raindrop-pp ``` - **`changes`** — Show field-level bookmark changes between sync snapshots. _Use to audit automation and discover recent library edits._ ```bash raindrop changes --since 7d --agent ``` ### Safe organization - **`inbox review`** — Process Unsorted bookmarks in resumable, bounded review sessions. _Use for safe inbox-zero organization without repeated prompts._ ```bash raindrop inbox review --limit 10 --agent ``` - **`tag health`** — Discover case variants, near-duplicates, singleton tags and merge candidates. _Use before bulk tag cleanup instead of guessing merge targets._ ```bash raindrop tag health --agent ``` - **`duplicates plan`** — Choose canonical bookmarks while preserving tags, notes and highlights. _Use when duplicate cleanup must not discard richer metadata._ ```bash raindrop duplicates plan --canonical richest --agent ``` ### Knowledge workflows - **`revisit`** — Resurface useful forgotten bookmarks without repeating recent suggestions. _Use to turn a bookmark archive back into an active reading system._ ```bash raindrop revisit --older-than 180d --limit 20 --agent ``` - **`related`** — Find explainable related bookmarks offline using text, tags and domains. _Use for research synthesis without a hosted semantic-search dependency._ ```bash raindrop related --limit 10 --agent ``` - **`highlights digest`** — Create deduplicated Markdown or JSONL study digests from highlights. _Use to turn annotations into portable research output._ ```bash raindrop highlights digest --since 30d --group-by tag --agent ``` ### Automation safety - **`workflow status`** — Run crash-safe bounded triage queues with retry and manual-review states. _Use for unattended agents that must resume safely after failures._ ```bash raindrop workflow status --agent --home /tmp/raindrop-pp ``` ## Recipes ### Narrow remote search ```bash raindrop raindrops search --collection 0 --search 'site:github.com #go' --agent --select items._id,items.title,items.link,items.tags ``` Return only fields an agent needs. ### Refresh offline mirror ```bash raindrop sync --agent --home /tmp/raindrop-pp ``` Incrementally fetch library resources into SQLite. ### Audit tags ```bash raindrop tag health --agent ``` Find deterministic cleanup candidates without mutation. ### Build reading queue ```bash raindrop revisit --older-than 180d --limit 20 --agent ``` Resurface forgotten high-value items. ## Command Reference **bookmark_transfer** — Manage bookmark transfer - `raindrop-pp-cli bookmark-transfer export-bookmarks` — Export bookmarks in various formats - `raindrop-pp-cli bookmark-transfer import-bookmarks` — Import bookmarks from files or external services - `raindrop-pp-cli bookmark-transfer import-from-url` — Import bookmarks from a remote URL hosting a bookmarks file **collection** — Manage collection - `raindrop-pp-cli collection create` — Creates a new collection with the specified properties - `raindrop-pp-cli collection delete` — Permanently deletes a collection and all its bookmarks - `raindrop-pp-cli collection empty-trash` — Permanently delete all bookmarks in the trash collection - `raindrop-pp-cli collection get` — Retrieves detailed information about a specific collection - `raindrop-pp-cli collection update` — Updates properties of an existing collection **collections** — Manage collections - `raindrop-pp-cli collections get-all` — Retrieves all collections for the authenticated user - `raindrop-pp-cli collections remove-empty` — Remove all empty collections from the account - `raindrop-pp-cli collections reorder` — Change the sort order of collections - `raindrop-pp-cli collections toggle-expansion` — Expand or collapse collections in the UI **file** — Manage file - `raindrop-pp-cli file delete` — Delete an uploaded file - `raindrop-pp-cli file get` — Download or retrieve information about an uploaded file **filters** — Manage filters - `raindrop-pp-cli filters` — Returns available filters such as tags, domains, and highlights to refine searches **highlights** — Manage highlights - `raindrop-pp-cli highlights add-to-bookmark` — Creates a new text highlight for a specific bookmark - `raindrop-pp-cli highlights delete` — Permanently removes a highlight from a bookmark - `raindrop-pp-cli highlights get-all` — Retrieves all highlights from a user's bookmarks with pagination - `raindrop-pp-cli highlights get-by-collection` — Retrieves all highlights from bookmarks in a specific collection - `raindrop-pp-cli highlights update` — Modifies an existing highlight's text, note, or color **raindrop** — Manage raindrop - `raindrop-pp-cli raindrop create-bookmark` — Creates a new bookmark with automatic metadata extraction - `raindrop-pp-cli raindrop delete-bookmark` — Moves a bookmark to trash (soft delete) - `raindrop-pp-cli raindrop get-bookmark` — Retrieves detailed information about a specific bookmark - `raindrop-pp-cli raindrop suggest-for-url` — Suggest tags and collections for a new URL - `raindrop-pp-cli raindrop update-bookmark` — Updates properties of an existing bookmark - `raindrop-pp-cli raindrop upload-file` — Upload a file and create a bookmark from it **raindrops** — Manage raindrops - `raindrop-pp-cli raindrops batch-delete-bookmarks` — Delete multiple bookmarks at once - `raindrop-pp-cli raindrops batch-delete-bookmarks-in-collection` — Delete multiple bookmarks in a specific collection or empty trash/collection - `raindrop-pp-cli raindrops batch-tag-bookmarks` — Batch operation to add or remove tags from multiple bookmarks - `raindrop-pp-cli raindrops batch-update-bookmarks` — Update multiple bookmarks across all collections - `raindrop-pp-cli raindrops batch-update-bookmarks-in-collection` — Update properties of multiple bookmarks in a specific collection at once - `raindrop-pp-cli raindrops bulk-move-bookmarks` — Move multiple bookmarks to a different collection - `raindrop-pp-cli raindrops get-all-bookmarks` — Retrieves all bookmarks from all collections with filtering options - `raindrop-pp-cli raindrops get-bookmarks-by-collection` — Retrieves bookmarks from a specific collection with filtering options - `raindrop-pp-cli raindrops get-multiple-bookmarks` — Retrieves multiple bookmarks by their IDs - `raindrop-pp-cli raindrops get-single-bookmark` — Retrieves comprehensive details about a specific bookmark by ID - `raindrop-pp-cli raindrops search` — Search bookmarks with advanced filtering options **tags** — Manage tags - `raindrop-pp-cli tags delete-all` — Delete multiple tags from all bookmarks - `raindrop-pp-cli tags delete-collection` — Delete multiple tags from bookmarks in a specific collection - `raindrop-pp-cli tags get-all` — Retrieves all unique tags used in the user's bookmarks - `raindrop-pp-cli tags get-all-alt` — Alternative endpoint to retrieve all tags - `raindrop-pp-cli tags get-by-collection` — Retrieves all tags used in bookmarks within a specific collection - `raindrop-pp-cli tags rename-or-merge-all` — Rename or merge tags across all collections - `raindrop-pp-cli tags rename-or-merge-collection` — Rename or merge tags within a specific collection **user** — Manage user - `raindrop-pp-cli user get-profile` — Retrieves the authenticated user's profile information - `raindrop-pp-cli user get-stats` — Retrieves account-wide statistics for the authenticated user ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash raindrop-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 Set RAINDROP_TOKEN, run `raindrop auth set-token`, or place a test token in `.raindrop-token`. Tokens are sent only as `Authorization: Bearer` to api.raindrop.io and are never written into output artifacts. Run `raindrop-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 raindrop-pp-cli collection get mock-value --agent --select item,result ``` - **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: ```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. ## Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: - Use `--home ` for one invocation, or set `RAINDROP_HOME=` to relocate all four path kinds under one root. - Use per-kind env vars only when a specific kind must diverge: `RAINDROP_CONFIG_DIR`, `RAINDROP_DATA_DIR`, `RAINDROP_STATE_DIR`, `RAINDROP_CACHE_DIR`. - Resolution order is per-kind env var, `--home`, `RAINDROP_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 `raindrop-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: ```json { "mcpServers": { "raindrop": { "command": "raindrop-pp-mcp", "env": { "RAINDROP_HOME": "/srv/raindrop" } } } } ``` Fleet precedence: an inherited per-kind env var overrides an explicit `--home` for that kind. Use `RAINDROP_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 `RAINDROP_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: ```bash raindrop-pp-cli recall "" --agent ``` The response envelope: ```json { "query": "...", "normalized": "", "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": ["", "raindrop-pp-cli learnings confirm 12"] } ], "playbook": { "query_family": "...", "playbook": { "steps": [ { "cmd": "", "purpose": "..." } ], "entity_slots": ["$ENTITY"], "expected_tool_calls": 3 }, "slots_resolved": { "$ENTITY": { "token": "", "canonical": "" } }, "notes": "" }, "notes": "" } ``` 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 ` only after the trial verified the behavior. Reject a wrong candidate with `learnings reject `. -> 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 `raindrop-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 ` prints the candidate's full payload before materializing it - check that the printed payload matches the behavior you verified. `learnings reject ` tombstones the derivation signature so the same candidate does not resurface. The envelope carries only the few candidates worth acting on now; `raindrop-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:` (top-level): a struc