macos-accessibility

Automate macOS GUI tasks via AXUIElement with TCC permission checks.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands --skill macos-accessibility-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: macos-accessibility
Source: https://github.com/cloudofgeorge/AI-hands/tree/main/skills/macos-accessibility
Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill macos-accessibility-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates macOS GUI tasks safely using Accessibility APIs, enforcing TCC permissions and strict security boundaries to prevent unauthorized automation.

Core Features & Use Cases

  • AXUIElement-based automation for desktop interactions across macOS apps.
  • TCC permission validation, prompt handling, and secure operation within sandbox boundaries.
  • Safe element discovery with security checks, blocklists for sensitive apps, and audit-logging.
  • Timeout enforcement and robust error handling to ensure reliable automation.

Quick Start

Describe a secure macOS GUI automation task you want performed, and the agent will validate TCC permissions and safely automate it.

Frequently Asked Questions about macos-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate macOS GUI tasks safely using AXUIElement?

macOS GUI automation via AXUIElement requires strict TCC permission validation to ensure secure desktop interactions. It enforces security boundaries like code-signature verification and app blocklists to prevent unauthorized automation of sensitive macOS apps.

What is TCC permission validation for macOS accessibility automation?

TCC permission validation is a mandatory security check verifying application authorization to use macOS Accessibility APIs. It ensures AXUIElement automation operates strictly within sandbox boundaries and prevents unauthorized GUI control.

Can I automate desktop interactions across any macOS app using accessibility APIs?

You can automate interactions across macOS apps using accessibility APIs, but sensitive applications can be excluded via blocklists. The automation enforces timeouts and audit logging to ensure reliable and secure operation.

How do I handle TCC permission prompts during macOS desktop automation?

Handling TCC permission prompts involves validating accessibility permissions and verifying code signatures before executing actions. The workflow includes robust error handling and timeout enforcement to manage permission delays securely.

Why does my macOS accessibility automation fail due to security boundaries?

macOS accessibility automation fails when encountering strict security boundaries like TCC permission blocks, app blocklists, or code-signature mismatches. It enforces these constraints to prevent unauthorized access.