agentleFS
lucasrafaldinilucasrafaldini/paperdeck/.agents/skills/diagnose-kindle/SKILL.md

diagnose-kindle

Skill1 starsChanged 47 days agoMITView on GitHub

Procedures for debugging Kindle SSH communication, daemon autostart, network discovery, and FBInk rendering.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when diagnosing device connectivity, script installation, or display issues on a Kindle Paperwhite/Touch.

    line 8
  2. Very specific:

    Ensure port 8787 is open on the host firewall.

    line 14
  3. Distinctive:

    Test reachability from host:

    line 15
  4. Very specific:

    Check KINDLE_INSTALLATION.md for prerequisites:

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Diagnose Kindle Skill

Use this skill when diagnosing device connectivity, script installation, or display issues on a Kindle Paperwhite/Touch.

1. Network Connectivity & Discovery

  • The Kindle display loop (kindle/dash-loop.sh) attempts to find the host computer using:
    1. mDNS (paperdeck.local, localhost).
    2. Local subnet sweep on port 8787 (/api/ping).
  • Ensure port 8787 is open on the host firewall.
  • Test reachability from host:
    curl -I http://localhost:8787/api/ping

2. SSH Connection Verification

  • The Electron app uses ssh2 to connect as root (port 22).
  • Check KINDLE_INSTALLATION.md for prerequisites:
    • SSH enabled via USBNetwork or KUAL.
    • Device and computer connected to the same Wi-Fi subnet.
    • Password or authorized keys configured on Kindle.

3. Remote Filesystem Checks

The Kindle requires:

  • /mnt/us/dash-loop.sh
  • /mnt/us/dash-autostart.sh
  • /mnt/us/dash-autostart.env
  • /etc/upstart/kindle-dashboard.conf (Upstart job)
  • fbink executable in /usr/bin/fbink, /mnt/us/bin/fbink, or in $PATH.

4. Test Manual Display

On the Kindle via SSH:

# Draw PNG directly to e-ink screen
fbink -c -g file=/mnt/us/dash.png
  • Flag -c: clears the screen before drawing.
  • Flag -g: draws a grayscale image.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.