agentleFS
coredevicescoredevices/PebbleOS/.agents/skills/working-with-qemu/SKILL.md

working-with-qemu

Skill1.5k starsChanged 3 days agoApache-2.0View on GitHub

Use when building, launching, debugging, or capturing screenshots of PebbleOS under QEMU.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 1 mentionFeb 2026: 2 mentionsMar 2026: 2 mentionsApr 2026: 6 mentionsMay 2026: 4 mentionsJun 2026: 5 mentionsJul 2026: 9 mentionsAug 2026: 2 mentionsSep 2026: 4 mentionsOct 2026: 11 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the coredevices/PebbleOS repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about coredevices/PebbleOS

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Hacker News (51 times).

On GitHub · 50

45 more on GitHub

On Hacker News · 1

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Read docs/development/emulation/emulator.md — it documents the full workflow: qemu_* boards, ./pbl run (monitor sockets, serial ports, …

    line 8
  2. Very specific:

    Use ./pbl emulator screenshot to validate UI changes.

    line 15

≈ “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

Working with QEMU

Read docs/development/emulation/emulator.md — it documents the full workflow: qemu_* boards, ./pbl run (monitor sockets, serial ports, uart1.log), ./pbl console, ./pbl emulator screenshot, programmatic key input via sendkey, touch injection via ./pbl emulator touch/./pbl emulator swipe, and ./pbl debug.

Agent notes:

  • Use ./pbl emulator screenshot to validate UI changes; read the resulting PNG.
  • Drive the UI over the socket monitor (build/qemu-mon.sock) with sendkey rather than the interactive QEMU window.
  • Phone-dependent features get their data from ./pbl emulator feed <feed> (e.g. ./pbl emulator feed weather); feeds live in tools/libs/pbl-cli/pbl/feeds/.

Touch

On touch-capable boards you can inject touch into a running QEMU (./pbl run exposes the QMP socket used for injection). Coordinates are screen pixels; the display size is read from the emulated pebble-touch device and scaled automatically.

./pbl emulator touch 130 130          # tap at (130, 130)
./pbl emulator swipe 130 220 130 40   # swipe up (finger bottom -> top)
./pbl emulator swipe 130 220 130 40 --duration 0.4

A tap is a finger down then up; a swipe streams intermediate moves so drag gestures are seen as continuous. Injection uses the absolute-pointer input path; multi-touch is not wired up in the device.

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.