Framebuffer Dump
PassAudited by ClawScan on May 1, 2026.
Overview
The skill appears aligned with its stated purpose of dumping an STM32 screen image, but it relies on external J-Link/Pillow setup and hardware memory-read commands that users should verify.
Before installing, confirm you have the intended STM32 target connected, verify the framebuffer address and dump size, and install J-Link/Pillow from trusted sources. The skill appears benign and purpose-aligned, but it will read the connected device's displayed pixels and write local dump/image files.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If run against the wrong connected device or with the wrong address/size, it could capture unintended on-device screen data or produce invalid dumps.
The skill instructs use of an external hardware debug tool to read framebuffer bytes from a connected STM32 device. This is central to the stated purpose and scoped by address/size, but users should confirm the target, dump range, and output paths.
JLinkExe -NoGui 1 -CommandFile /tmp/jlink_dump_fb.jlink > /tmp/jlink_dump_fb.log 2>&1
Use only with the intended hardware, review the generated J-Link command file, and verify framebuffer address, size, and output paths before running.
Users may need to install tools manually, and should make sure they come from trusted sources.
The README requires external tooling and a Python package, while the registry metadata declares no required binaries or install spec. This is purpose-aligned but leaves dependency installation and provenance checks to the user.
Requirements - [SEGGER J-Link](https://www.segger.com/downloads/jlink/) (`JLinkExe` in PATH) - Python 3.8+ with [Pillow](https://pypi.org/project/Pillow/): `pip install Pillow`
Install SEGGER J-Link and Pillow only from trusted sources, and consider updating the skill metadata to declare these requirements explicitly.