From 9d20e955903fa2f4fe233f6544824ce1ec4c2eb0 Mon Sep 17 00:00:00 2001 From: Jean-Pierre Martineau Date: Thu, 1 Oct 2026 18:21:43 -0400 Subject: [PATCH] The screenshot skill has run on the PicoCalc Two shots on 2026-10-01, the login console and MeshTerm's Public channel, came out upright, unmirrored, and in the right colours (the header's yellow count and the teal wordmark would trade places with red and blue swapped), so the untested note goes. Co-Authored-By: Claude Opus 5.5 (1M context) (cherry picked from commit 90ae2d56af2830efa36bd36bffa8c03d3ac32b20) --- .claude/skills/screenshot-picocalc/SKILL.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.claude/skills/screenshot-picocalc/SKILL.md b/.claude/skills/screenshot-picocalc/SKILL.md index 4e3f287..5b10603 100644 --- a/.claude/skills/screenshot-picocalc/SKILL.md +++ b/.claude/skills/screenshot-picocalc/SKILL.md @@ -67,10 +67,6 @@ The checkerboard flicker in the panel's top two rows will not appear in the scre That is an electrical artefact of the panel, not something in the framebuffer, so the screenshot is cleaner than the device itself. That is expected; don't try to reproduce it. -**Not yet run against the device**: the script was written while the PicoCalc was -offline and tested only against a simulated framebuffer. On the first real run, check the -orientation and the colours against the panel, then delete this note. - ## How it works `scripts/picocalc_shot.py` sends a short Python program to the device, base64-encoded so