peekaboo-cli

This skill is internally consistent for macOS UI automation: it expects you to have the Peekaboo CLI and macOS accessibility/screen-recording permissions. Before installing or enabling it, confirm you trust the skill's publisher (no homepage/source is provided here). Key things to consider: - Sensitive access: Peekaboo can capture full-screen screenshots, read/write clipboard contents, drive keystrokes, and read ~/.peekaboo config (which may contain API keys). Treat those capabilities as high-risk — they can expose secrets or private content. - Source integrity: The skill metadata shows no homepage/source. Prefer installing Peekaboo from the official repo or Homebrew tap linked in the docs (verify the tap and repository). Inspect the skill files you copy into ~/.openclaw/ or ~/.claude/ before enabling. - Least privilege: Only grant macOS Screen Recording and Accessibility permissions if you trust the tool. Consider granting permissions to a dedicated, sandboxed terminal or temporary account if you need to limit exposure. - Operation mode: Use dry-run or interactive modes first (e.g., peekaboo agent --dry-run or --chat) to confirm what the skill will run before allowing autonomous runs. Avoid enabling broad autonomous invocations for skills that can capture screens/clipboard unless publisher and code are verified. - Audit outputs: Be cautious of commands that send captured images or metadata to external AI providers (the CLI supports an "--analyze" flag and provider config). Review ~/.peekaboo/config and provider entries to ensure no accidental outward transmission of sensitive screenshots or credentials. If you need stronger assurance, obtain the upstream source (GitHub repo), inspect the CLI/tooling, and confirm the skill files haven't been tampered with. If you cannot verify the origin, treat the skill as untrusted despite internal coherence.