remarkable-axi
An AXI CLI for the reMarkable cloud. No install needed —
every command below runs as npx -y remarkable-axi …. Run it bare first to
see current pairing status and what's on the tablet:
npx -y remarkable-axi
If it reports NOT_AUTHENTICATED, pair with an 8-character code from
https://my.remarkable.com/device/desktop/connect:
npx -y remarkable-axi login <code>.
The design → send → pull loop
- Design against the panel, not a monitor — get the page box and a CSS
block to author against:
npx -y remarkable-axi page --css.
- Check before sending — rasterize at the device's density and lint
hairlines, contrast, type size, and page box:
npx -y remarkable-axi check flyer.html.
- Send —
npx -y remarkable-axi put flyer.html "/Talks". Replacing an
inked document refuses by default; see put --help for --replace and
--discard-ink (let it go) or --keep-ink (carry the strokes onto the
replacement — the route that costs nothing).
- Pull ink back —
npx -y remarkable-axi get "/Talks/Flyer" --overlay
for annotations drawn over the original, or --as text for OCR'd text.
Handwriting looks lost — stop and read this first
"Cloud shows zero ink but I know I wrote something", "the tablet has blank
pages that had notes on them", "did that replace eat my annotations" — these
are all the same failure: strokes the device hadn't synced up yet, orphaned by
a replace or a sync restart that won the cloud's side. They are not
destroyed; they are recoverable, but only if nobody touches the tablet before
the backup is taken.
Open references/ink-recovery.md now, before
opening any document on the device, writing anything, or launching the desktop
app. It carries the triage, the hands-off discipline, and the manual SSH
recovery procedure — proven end to end in two real incidents.
Reference files
- references/ink-recovery.md — open when
ink or annotations look missing. Triage, the hands-off rule, backup, and the
manual SSH reattach procedure.
- references/ssh-setup.md — open the first time
device recovery is needed and SSH isn't set up yet: enabling SSH on-device,
installing a key, direct vs. relayed access.
Command reference
Design
npx -y remarkable-axi page [--device <model>] [--landscape] [--css] — Report the target device's page box, and the CSS to author against itnpx -y remarkable-axi render <html> [--out <path>] [--device <model>] [--landscape] [--device-page] — Print an HTML document to a PDF sized for the target device's page boxnpx -y remarkable-axi check <file> [--pages <spec>] [--device <model>] [--out <dir>] [--full-res] [--no-images] — Rasterize a PDF or HTML document at the device's density and lint it against the panel
Move
npx -y remarkable-axi put <src> <dest> — Send a local PDF/EPUB or a URL to the tablet — source first, destination lastnpx -y remarkable-axi get <path> [<dest>] — Bring a document down off the tablet — rendered ink, typed text, or the original file
Browse
npx -y remarkable-axi ls [<path>] — List the contents of a folder (default: /)npx -y remarkable-axi find <pattern> — Search every document and folder name by substring or regexnpx -y remarkable-axi devices — Show known reMarkable models with screen specs and PDF page sizes
Organize
npx -y remarkable-axi mkdir <path> — Create a folder and every missing parent (idempotent)npx -y remarkable-axi mv <path> <dest-dir> [--name <name>] — Move a document or folder into another folder, optionally renaming itnpx -y remarkable-axi rm <path> — Move a document or folder to the trash
Setup
npx -y remarkable-axi login <code> — Pair this machine using an 8-character code from my.remarkable.comnpx -y remarkable-axi doctor — Check pairing, connectivity, external tools, duplicate paths, and the cachenpx -y remarkable-axi setup device <model> — Set the device to design for; its specs then appear in every sessionnpx -y remarkable-axi setup hooks — Install SessionStart hooks so agents see tablet state automaticallynpx -y remarkable-axi setup ssh <destination> [--via <jump>] — Configure direct or relayed SSH access to the tablet, for the device command group
Device
npx -y remarkable-axi device status [--ssh <dest>] [--via <jump>] — Check tablet reachability, xochitl, storage free, and local document countnpx -y remarkable-axi device backup <path> [--out <tar>] [--force] [--ssh <dest>] [--via <jump>] — Tar a document's complete on-device file set to a local archive — the first step of every recoverynpx -y remarkable-axi device orphans [<path>] [--render] [--out <dir>] [--ssh <dest>] [--via <jump>] — List .rm stroke files no page index references — the tablet's own unsynced/clobbered inknpx -y remarkable-axi device reattach <path> --map <stroke-uuid>=<page-uuid>[,...] | --restore-index [--ssh <dest>] [--via <jump>] — Write recovered strokes back into a document's index — backup, stop xochitl, write, sync, restart
Every command supports --help for its full flag reference and examples.
Notes
- Nothing above is exclusive to this skill — every workflow works from the
CLI's own
--help and ambient output with no skill installed. This skill
adds the recovery judgment and one-time SSH setup that command output alone
can't teach.
- The
device command group (device status, device backup,
device orphans, device reattach) is fully shipped. The ink-recovery
playbook drives recovery through those commands now; the raw SSH procedure
that shipped first is kept in the playbook as a fallback appendix, for a
step no command covers or a connection the commands themselves can't reach.
1---2name: remarkable-axi3description: Use this skill for anything involving a reMarkable tablet. That includes sending or uploading a PDF, EPUB, or URL to the tablet; designing, rendering, or checking a page, flyer, or document against the reMarkable's e-ink screen; browsing or organizing what's on the tablet; and downloading handwriting, ink, annotations, or typed notes off it. Use it immediately whenever notes or handwriting on a reMarkable appear missing or lost — blank pages the user knows they wrote on, ink gone after a sync, or annotations possibly destroyed by replacing a document — because it contains the step-by-step ink-recovery procedure, and the first rule is to stop touching the device. If a query mentions a reMarkable (or "my tablet" in a reMarkable context) plus documents, pages, notes, ink, or sync, use this skill. Do not use it for other devices or apps (iPad, Kindle, Notion), generic file recovery, or printing questions unrelated to the tablet.4---56# remarkable-axi78An [AXI](https://axi.md) CLI for the reMarkable cloud. No install needed —9every command below runs as `npx -y remarkable-axi …`. Run it bare first to10see current pairing status and what's on the tablet:1112```sh13npx -y remarkable-axi14```1516If it reports `NOT_AUTHENTICATED`, pair with an 8-character code from17<https://my.remarkable.com/device/desktop/connect>:18`npx -y remarkable-axi login <code>`.1920## The design → send → pull loop21221. **Design against the panel, not a monitor** — get the page box and a CSS23 block to author against: `npx -y remarkable-axi page --css`.242. **Check before sending** — rasterize at the device's density and lint25 hairlines, contrast, type size, and page box:26 `npx -y remarkable-axi check flyer.html`.273. **Send** — `npx -y remarkable-axi put flyer.html "/Talks"`. Replacing an28 inked document refuses by default; see `put --help` for `--replace` and29 `--discard-ink` (let it go) or `--keep-ink` (carry the strokes onto the30 replacement — the route that costs nothing).314. **Pull ink back** — `npx -y remarkable-axi get "/Talks/Flyer" --overlay`32 for annotations drawn over the original, or `--as text` for OCR'd text.3334## Handwriting looks lost — stop and read this first3536"Cloud shows zero ink but I know I wrote something", "the tablet has blank37pages that had notes on them", "did that replace eat my annotations" — these38are all the same failure: strokes the device hadn't synced up yet, orphaned by39a replace or a sync restart that won the cloud's side. **They are not40destroyed; they are recoverable, but only if nobody touches the tablet before41the backup is taken.**4243Open [references/ink-recovery.md](references/ink-recovery.md) now, before44opening any document on the device, writing anything, or launching the desktop45app. It carries the triage, the hands-off discipline, and the manual SSH46recovery procedure — proven end to end in two real incidents.4748## Reference files4950- **[references/ink-recovery.md](references/ink-recovery.md)** — open when51 ink or annotations look missing. Triage, the hands-off rule, backup, and the52 manual SSH reattach procedure.53- **[references/ssh-setup.md](references/ssh-setup.md)** — open the first time54 device recovery is needed and SSH isn't set up yet: enabling SSH on-device,55 installing a key, direct vs. relayed access.5657## Command reference5859<!-- BEGIN GENERATED: command-reference -->6061### Design6263- `npx -y remarkable-axi page [--device <model>] [--landscape] [--css]` — Report the target device's page box, and the CSS to author against it64- `npx -y remarkable-axi render <html> [--out <path>] [--device <model>] [--landscape] [--device-page]` — Print an HTML document to a PDF sized for the target device's page box65- `npx -y remarkable-axi check <file> [--pages <spec>] [--device <model>] [--out <dir>] [--full-res] [--no-images]` — Rasterize a PDF or HTML document at the device's density and lint it against the panel6667### Move6869- `npx -y remarkable-axi put <src> <dest>` — Send a local PDF/EPUB or a URL to the tablet — source first, destination last70- `npx -y remarkable-axi get <path> [<dest>]` — Bring a document down off the tablet — rendered ink, typed text, or the original file7172### Browse7374- `npx -y remarkable-axi ls [<path>]` — List the contents of a folder (default: /)75- `npx -y remarkable-axi find <pattern>` — Search every document and folder name by substring or regex76- `npx -y remarkable-axi devices` — Show known reMarkable models with screen specs and PDF page sizes7778### Organize7980- `npx -y remarkable-axi mkdir <path>` — Create a folder and every missing parent (idempotent)81- `npx -y remarkable-axi mv <path> <dest-dir> [--name <name>]` — Move a document or folder into another folder, optionally renaming it82- `npx -y remarkable-axi rm <path>` — Move a document or folder to the trash8384### Setup8586- `npx -y remarkable-axi login <code>` — Pair this machine using an 8-character code from my.remarkable.com87- `npx -y remarkable-axi doctor` — Check pairing, connectivity, external tools, duplicate paths, and the cache88- `npx -y remarkable-axi setup device <model>` — Set the device to design for; its specs then appear in every session89- `npx -y remarkable-axi setup hooks` — Install SessionStart hooks so agents see tablet state automatically90- `npx -y remarkable-axi setup ssh <destination> [--via <jump>]` — Configure direct or relayed SSH access to the tablet, for the device command group9192### Device9394- `npx -y remarkable-axi device status [--ssh <dest>] [--via <jump>]` — Check tablet reachability, xochitl, storage free, and local document count95- `npx -y remarkable-axi device backup <path> [--out <tar>] [--force] [--ssh <dest>] [--via <jump>]` — Tar a document's complete on-device file set to a local archive — the first step of every recovery96- `npx -y remarkable-axi device orphans [<path>] [--render] [--out <dir>] [--ssh <dest>] [--via <jump>]` — List .rm stroke files no page index references — the tablet's own unsynced/clobbered ink97- `npx -y remarkable-axi device reattach <path> --map <stroke-uuid>=<page-uuid>[,...] | --restore-index [--ssh <dest>] [--via <jump>]` — Write recovered strokes back into a document's index — backup, stop xochitl, write, sync, restart9899<!-- END GENERATED: command-reference -->100101Every command supports `--help` for its full flag reference and examples.102103## Notes104105- Nothing above is exclusive to this skill — every workflow works from the106 CLI's own `--help` and ambient output with no skill installed. This skill107 adds the recovery judgment and one-time SSH setup that command output alone108 can't teach.109- The `device` command group (`device status`, `device backup`,110 `device orphans`, `device reattach`) is fully shipped. The ink-recovery111 playbook drives recovery through those commands now; the raw SSH procedure112 that shipped first is kept in the playbook as a fallback appendix, for a113 step no command covers or a connection the commands themselves can't reach.
JarvusInnovations