Run any Skill in Manus with one click

Get Started

peekaboo

macOS screenshots, UI inspect, clicks, typing, app/window automation.

Run Skill in Manus

Overview

macOS screenshots, UI inspect, clicks, typing, app/window automation.

Install command

npx skills add https://github.com/BumpyClock/dotfiles --skill peekaboo

Copy and paste this command into Claude Code to install the skill

Source

BumpyClock/dotfiles

Stars1

Forks1

UpdatedJune 3, 2026 at 20:56

File Explorer

2 files

SKILL.md

readonly

name	peekaboo
description	macOS screenshots, UI inspect, clicks, typing, app/window automation.

Peekaboo

Use for macOS screen capture, UI inspection, and GUI automation.

Binary

Prefer ~/bin/peekaboo when present; it is Peter's local release copy.
Else use peekaboo.
Check first: ~/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.
On remote Macs, Screenshot may be blocked by missing Screen Recording while clicks/typing still work through Accessibility; continue with clicks or DOM automation when the target is otherwise knowable.
Prefer --json for machine parsing and --no-remote when testing local TCC.
Do not click/type/destructively automate unless user asked or target is a controlled test.

Common 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 as above and confirm version when install state matters.
Run permissions status --json; if missing TCC, report exact missing grant.
For screenshots, use image; include --path, --json, and usually --no-remote.
For element targeting, run see --json --annotate, then click by element id/snapshot.
For long-running/change-aware screen capture, use capture live; for video frame sampling, use capture video.
Use tools --json for command/tool discovery and learn when the full agent guide is useful.
Verify output files with sips -g pixelWidth -g pixelHeight <path> or view the image.

Docs: ~/Projects/Peekaboo/docs/commands/.

More from this repository

same repository

workflow-from-chats

BumpyClock/dotfiles

Extract durable working preferences from recent local agent chats and convert them into skills, rules, or workflow docs. Use when asked to learn preferences, mine feedback, personalize workflows, or generate user/team-specific agent guidance.

2026-06-031

use-spark

BumpyClock/dotfiles

Use the spark CLI to access the user's Spark email data - list emails, search by topic, read threads, check calendar events, find availability, look up contacts, and view team info. Use when the user asks about their emails, calendar, contacts, meetings, or scheduling.

2026-06-031

beeper

BumpyClock/dotfiles

Beeper cache: contact hints, room lookup, WhatsApp/iMessage traces, FTS.

2026-06-031

brainstorming

BumpyClock/dotfiles

Use for new features, UX/UI changes, behavior changes, architecture decisions, or ambiguous work where intent/design must be clarified before implementation. Use micro-flow only for trivial mechanical/non-behavior changes.

2026-06-031

browser-use

BumpyClock/dotfiles

Chrome DevTools MCP automation: existing Chrome tabs, no AppleScript.

2026-06-031

opentui

BumpyClock/dotfiles

Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.

2026-06-031

Source

BumpyClock

BumpyClock/dotfiles

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

name	peekaboo
description	macOS screenshots, UI inspect, clicks, typing, app/window automation.

Peekaboo

Use for macOS screen capture, UI inspection, and GUI automation.

Binary

Prefer ~/bin/peekaboo when present; it is Peter's local release copy.
Else use peekaboo.
Check first: ~/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.
On remote Macs, Screenshot may be blocked by missing Screen Recording while clicks/typing still work through Accessibility; continue with clicks or DOM automation when the target is otherwise knowable.
Prefer --json for machine parsing and --no-remote when testing local TCC.
Do not click/type/destructively automate unless user asked or target is a controlled test.

Common 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 as above and confirm version when install state matters.
Run permissions status --json; if missing TCC, report exact missing grant.
For screenshots, use image; include --path, --json, and usually --no-remote.
For element targeting, run see --json --annotate, then click by element id/snapshot.
For long-running/change-aware screen capture, use capture live; for video frame sampling, use capture video.
Use tools --json for command/tool discovery and learn when the full agent guide is useful.
Verify output files with sips -g pixelWidth -g pixelHeight <path> or view the image.

Docs: ~/Projects/Peekaboo/docs/commands/.