peekaboo
macOS screenshots, UI inspect, clicks, typing, app/window automation.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- peekaboo
- description
- macOS screenshots, UI inspect, clicks, typing, app/window automation.
02 资源文件 2
- 参考文档agents/openai.yaml237 B
- 参考文档attribution.txt165 B
03 SKILL.md 正文
Peekaboo
macOS screen capture, UI inspection, GUI automation.
Binary
Prefer ~/bin/peekaboo (local release copy). Else peekaboo.
Check: ~/bin/peekaboo --version || peekaboo --version.
Safety
- Check permissions before capture/automation:
peekaboo permissions status --json. - Screenshot needs Screen Recording; clicks/typing/window control need Accessibility.
- Remote Macs: Screenshot may be blocked (missing Screen Recording) while clicks/typing work via Accessibility; continue with clicks or DOM automation when target knowable.
- Prefer
--jsonfor machine parsing,--no-remotefor local TCC testing. - No click/type/destructive automation unless user asked or target is controlled test.
Commands
PB="${PEEKABOO_BIN:-$HOME/bin/peekaboo}"
[ -x "$PB" ] || PB="$(command -v peekaboo)"
"$PB" permissions status --json
"$PB" list screens --json
"$PB" list apps --json
"$PB" list windows --app Safari --json
"$PB" image --mode screen --screen-index 0 --path /tmp/screen.png --json --no-remote
"$PB" see --app frontmost --path /tmp/frontmost.png --json --annotate
"$PB" tools --json
"$PB" learn
"$PB" click --coords 100,100 --json
"$PB" type "text" --json
Workflow
- Resolve
PB, confirm version when install state matters. permissions status --json; report exact missing TCC grants.- Screenshots:
imagewith--path,--json, usually--no-remote. - Element targeting:
see --json --annotate, click by element id/snapshot. - Long-running capture:
capture live; video frame sampling:capture video. - Discovery:
tools --json,learnfor full agent guide. - Verify output:
sips -g pixelWidth -g pixelHeight <path>or view image.
Documentation
Use the resolved binary's tools --json, learn, or <command> --help for installed capabilities and syntax.
Local checkout documentation is optional. Use its docs/commands/ directory only after locating and verifying that checkout; do not assume a machine-specific repository path.
04 同仓库更多 Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
workflow-from-chats
Extract preferences from agent chats → skills, rules, workflow docs. For learning preferences, mining feedback, personalizing workflows.
winui3-csharp-app
WinUI 3 / Windows App SDK desktop apps in C#/XAML. MVVM, bindings, navigation, Mica/Acrylic, windowing, packaging, performance.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise status update.
weekly-review
Produce a short weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work.