SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillskindle-weread-setup

kindle-weread-setup

General & other

View repository

Updated 10-15 17:26

About this skill

Kindle WeRead Installation Guide

Treat the task as a device maintenance process with access controls. Do not infer the route directly from "Kindle Paperwhite" or an appearance photo. Complete the diagnostic interview first, then check same-day sources; advance only one stage at a time, and each stage must have an observable success indicator.

The first round must begin with the diagnostic interview

Before any download, copy, network connection, or device operation, read references/intake-and-routing.md, and collect all at once:

  • Kindle market name/generation; if uncertain, collect the serial number prefix, at most the first 6 characters
  • Full firmware version
  • Computer OS and version: macOS / Windows / Linux
  • Connection mode: disk mount, MTP, charging only, or not yet connected; if mounted, record the exact path/drive letter
  • Battery level, airplane mode, Amazon registration status
  • Free space and whether important books/annotations already have independent backups

If any of model or serial number prefix, firmware, or computer OS is missing, first guide the user to open the "Device Info" page and do not proceed to installation. Before making photos public, mask the full serial number, MAC, account name, QR code, and verification code.

Maintenance Status Card

Maintain it continuously in the conversation; do not write personal status back to the Skill by default:

  • Device profile: model/generation, serial number prefix, firmware
  • Host profile: OS, connection mode, path/drive letter
  • Current stage: diagnostic interview / routing / backup / update prevention / jailbreak / KOReader / WeRead / acceptance
  • Evidence: user-provided / source verified / file verified / passed on real device / failed / pending verification
  • Safety status: battery level, airplane mode, update leftovers, backup, whether current write is allowed

Do not display or save the full serial number, MAC, API Key, Cookie, QR code login result, or four-digit verification code.

Same-Day Sources and Routing Gates

Before entering the jailbreak, KOReader, or plugin stage, re-check online; do not rely only on this Skill:

  1. Model and firmware:https://kindlemodding.org/kindle-models
  2. Jailbreak entry/wizard:https://kindlemodding.org/jailbreaking/
  3. Original repository and Release of the specific jailbreak project
  4. KOReader Kindle Wiki and Release:https://github.com/koreader/koreader/wiki/Installation-on-Kindle-devices
  5. WeRead plugin repository and Release:https://github.com/finlater/weread.koplugin

Record the access date, matched model/firmware range, chosen route, and release version. If two high-priority sources conflict, the version is outside the supported range, or the device cannot be uniquely identified, stop writing and show the conflict to the user.

A device case only proves that the combination once worked; it cannot override same-day compatibility sources.references/macos-pw4-5.14.1.md is only a real-device case, not the default route.

Computer and Connection Mode

Read references/platform-access.md. Prefer the user's existing OS; do not require switching to Windows or Mac for installation:

  • Filesystem mount: cross-platform Python scripts or the platform's native file manager can be used.
  • MTP/non-mounted device: do not pretend a normal path exists; use the platform file transfer interface instead, and mark automated scripts as unavailable.
  • Charging only or frequent disconnects: first resolve the cable, port, or driver issue; do not continue.

When a cross-platform script requires an explicit path, the user or Codex must first confirm that the path actually contains the Kindle's documents directory.

Safety Boundaries

  • Do not automatically upgrade, downgrade, factory reset, deregister the device, disassemble, short-circuit, or modify partitions.
  • Do not bundle jailbreak packages, KOReader, the WeRead plugin, books, account files, or credentials within the Skill.
  • Download only from the original project release page of the day; record the version and the checksums provided by the publisher. When there is no official checksum, record the fingerprint of this download but do not pass it off as an official checksum.
  • Before each backup creation, device write, network access, jailbreak trigger, reboot, deletion, or restoration of update capability, explain the goal and impact and obtain explicit confirmation.
  • Before deletion, use read-only checks to resolve the unique target; unresolved variables, wildcards, and broad directories are prohibited. Delete only targets that were explicitly created in the current phase and have been confirmed.
  • Do not promise that it will not brick, will not get an account banned, or will work on all Kindles.
  • Do not assist with DRM removal, book distribution, preconfigured accounts, or rapid bulk scraping of content.

Complete stop conditions read references/safety-and-routing.md。

Phased workflow

  1. Intake: complete the first-round information card; perform read-only operations only.
  2. Routing: check the sources of the day and form a single route for "device + firmware + jailbreak + computer access method".
  3. Detection and backup: when the file system is mounted, run scripts/device_audit.py and scripts/backup_visible_storage.pyfirst; otherwise back up manually according to the platform reference. Verify the source/backup file count and logical bytes.
  4. Anti-update: execute only when the current route explicitly requires it. Space targets must be taken from the guide of the day; do not use cached thresholds from within scripts.
  5. Stage jailbreak files: download from the original Release, inspect the archive structure and fingerprint; write only after user confirmation. Validation rules must come from the current Release and cannot be filled in from old filenames.
  6. On-device trigger: give only the action for the current screen at a time; keep the full prompt. A reboot is not sufficient evidence of success; check the success marker for that route.
  7. Post-jailbreak wrap-up: only after confirming persistence/OTA status and update remnants, clean up the temporary filler files.
  8. KOReader: read references/koreader-weread.md, and choose KPM, Scriptlet, Booklet, or KUAL according to the current Wiki. If KPM fails, first check whether it was written to disk, then decide on a manual fallback; do not reinstall repeatedly.
  9. WeRead plugin: check the minimum KOReader version, Release structure, external links, and update boundaries; run phase verification after writing.
  10. Acceptance: test KOReader startup/exit, plugin loading, QR code login, bookshelf, one short book, offline reading, and progress sync. If long-term power consumption, standby, and account risks have not been tested, clearly mark them as unverified.

When the file system is mounted, you can run:

python3 scripts/device_audit.py <Kindle路径或盘符>
python3 scripts/backup_visible_storage.py <Kindle路径或盘符> <备份父目录>
python3 scripts/verify_stage.py <winterbreak2|koreader|weread> <Kindle路径或盘符>

If the environment does not have Python, use the platform file manager and references/platform-access.md for manual verification; do not require the user to install an additional runtime.

Reference routing

  • First-round questions and triage:references/intake-and-routing.md
  • General gates, evidence priority, and stop conditions:references/safety-and-routing.md
  • macOS / Windows / Linux / MTP：references/platform-access.md
  • KOReader, KPM fallback, and WeRead:references/koreader-weread.md
  • Error and recovery judgment:references/troubleshooting.md
  • PW4 + 5.14.1 + macOS real-device case:references/macos-pw4-5.14.1.md, read only when the device precisely matches or when studying a known case

Communication and delivery

  • Give only one operation phase per round; first state the goal, risk, success marker, and stop conditions.
  • Use "source verified / file verified / passed on real device / not yet verified" to distinguish evidence levels.
  • When an error occurs, preserve the scene; first read the error, directory, and logs; do not continuously switch jailbreak or installation methods.
  • After completion, deliver a sanitized acceptance record: device/firmware/system, adopted route and version, successful items, failed rollback, items pending verification, and rollback precautions.