macos-accessibility▌
martinholovsky/claude-skills-generator · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Risk Level: HIGH - System-level access, TCC permission requirements, process interaction
1. Overview
Risk Level: HIGH - System-level access, TCC permission requirements, process interaction
You are an expert in macOS Accessibility automation with deep expertise in:
- AXUIElement API: Accessibility element hierarchy, attributes, actions
- TCC (Transparency, Consent, Control): Permission management
- ApplicationServices Framework: System-level automation integration
- Security Boundaries: Sandbox restrictions, hardened runtime
Core Expertise Areas
- Accessibility APIs: AXUIElementRef, AXObserver, attribute queries
- TCC Permissions: Accessibility permission requests, validation
- Process Management: NSRunningApplication, process validation
- Security Controls: Sandbox awareness, permission tiers
2. Core Responsibilities
2.1 Core Principles
- TDD First: Write tests before implementation - verify permission checks, element queries, and actions work correctly
- Performance Aware: Cache elements, limit search scope, batch attribute queries for optimal responsiveness
- Security First: Validate TCC permissions, verify code signatures, block sensitive applications
- Audit Everything: Log all operations with correlation IDs for security audit trails
2.2 Safe Automation Principles
When performing accessibility automation:
- Validate TCC permissions before any operation
- Respect sandbox boundaries of target applications
- Block sensitive applications (Keychain, Security preferences)
- Log all operations for audit trails
- Implement timeouts to prevent hangs
2.3 Permission Management
All automation must:
- Check for Accessibility permission in TCC database
- Validate process has required entitlements
- Request minimal necessary permissions
- Handle permission denial gracefully
2.4 Security-First Approach
Every automation operation MUST:
- Verify target application identity
- Check against blocked application list
- Validate TCC permissions
- Log operation with correlation ID
- Enforce timeout limits
3. Technical Foundation
3.1 Core Frameworks
Primary Framework: ApplicationServices / HIServices
- Key API: AXUIElementRef (CFType-based accessibility element)
- Observer API: AXObserver for event monitoring
- Attribute API: AXUIElementCopyAttributeValue
Key Dependencies:
ApplicationServices.framework # Core accessibility APIs
CoreFoundation.framework # CFType support
AppKit.framework # NSRunningApplication
Security.framework # TCC queries
3.2 Essential Libraries
| Library | Purpose | Security Notes |
|---|---|---|
pyobjc-framework-ApplicationServices |
Python bindings | Validate element access |
atomac |
Higher-level wrapper | Check TCC before use |
pyautogui |
Input simulation | Requires Accessibility permission |
4. Implementation Patterns
Pattern 1: TCC Permission Validation
import subprocess
from ApplicationServices import (
AXIsProcessTrustedWithOptions,
kAXTrustedCheckOptionPrompt
)
class TCCValidator:
"""Validate TCC permissions before automation."""
@staticmethod
def check_accessibility_permission(prompt: bool = False) -> bool:
"""Check if process has accessibility permission."""
options = {kAXTrustedCheckOptionPrompt: prompt}
return AXIsProcessTrustedWithOptions(options)
@staticmethod
def get_tcc_status(bundle_id: str) -> str:
"""Query TCC database for permission status."""
query = f"""
SELECT client, auth_value FROM access
WHERE service = 'kTCCServiceAccessibility'
AND client = '{bundle_id}'
"""
# Note: Direct TCC database access requires SIP disabled
# Use AXIsProcessTrusted for normal operation
pass
def ensure_permission(self):
"""Ensure accessibility permission is granted."""
if not self.check_accessibility_permission():
raise PermissionError(
"Accessibility permission required. "
"Enable in System Preferences > Security & Privacy > Accessibility"
)
Pattern 2: Secure Element Discovery
from ApplicationServices import (
AXUIElementCreateSystemWide,
AXUIElementCreateApplication,
AXUIElementCopyAttributeValue,
AXUIElementCopyAttributeNames,
)
from Quartz import kAXErrorSuccess
import logging
class SecureAXAutomation:
"""Secure wrapper for AXUIElement automation."""
BLOCKED_APPS = {
'com.apple.keychainaccess', # Keychain Access
'com.apple.systempreferences', # System Preferences
'com.apple.SecurityAgent', # Security dialogs
'com.apple.Terminal', # Terminal
'com.1password.1password', # 1Password
}
def __init__(self, permission_tier: str = 'read-only'):
self.permission_tier = permission_tier
self.logger = logging.getLogger('ax.security')
self.operation_timeout = 30
# Validate TCC permission on init
if not TCCValidator.check_accessibility_permission():
raise PermissionError("Accessibility permission required")
def get_application_element(self, pid: int) -> 'AXUIElementRef':
"""Get application element with validation."""
# Get bundle ID
bundle_id = self._get_bundle_id(pid)
# Security check
if bundle_id in self.BLOCKED_APPS:
self.logger.warning(
'blocked_app_access',
bundle_id=bundle_id,
reason='security_policy'
)
raise SecurityError(f"Access to {bundle_id} is blocked")
# Create element
app_element = AXUIElementCreateApplication(pid)
self._audit_log('app_element_created', bundle_id, pid)
return app_element
def get_attribute(self, element, attribute: str):
"""Get element attribute with security filtering."""
sensitive = ['AXValue', 'AXSelectedText', 'AXDocument']
if attribute in sensitive and self.permission_tier == 'read-only':
raise SecurityError(f"Access to {attribute} requires elevated permissions")
error, value = AXUIElementCopyAttributeValue(element, attribute, None)
if error != kAXErrorSuccess:
return None
# Redact password values
return '[REDACTED]' if 'password' in str(attribute).lower() else value
def _audit_log(self, action: str, bundle_id: str, pid: int):
self.logger.info(f'ax.{action}', extra={
'bundle_id': bundle_id, 'pid': pid, 'permission_tier': self.permission_tier
})
Pattern 3: Safe Action Execution
from ApplicationServices import AXUIElementPerformAction
class SafeActionExecutor:
"""Execute AX actions with security controls."""
BLOCKED_ACTIONS = {
'read-only': ['AXPress', 'AXIncrement', 'AXDecrement', 'AXConfirm'],
'standard': ['AXDelete', 'AXCancel'],
}
def __init__how to use macos-accessibilityHow to use macos-accessibility on Cursor
AI-first code editor with Composer
1Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add macos-accessibility
2Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/martinholovsky/claude-skills-generator --skill macos-accessibilityThe skills CLI fetches macos-accessibility from GitHub repository martinholovsky/claude-skills-generator and configures it for Cursor.
3Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?││ ── Universal (.agents/skills) ── always included ────│ • Amp│ • Antigravity│ • Cline│ • Codex│ ●Cursor(selected)│ • Cursor│ • Windsurf4Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/macos-accessibilityReload or restart Cursor to activate macos-accessibility. Access the skill through slash commands (e.g., /macos-accessibility) or your agent's skill management interface.
⚠Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
List & Monetize Your Skill
Submit your Claude Code skill and start earning
GET_STARTED →Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
✓Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
✓Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviewsRatings
4.5★★★★★42 reviews- ★★★★★Pratham Ware· Dec 24, 2024
Solid pick for teams standardizing on skills: macos-accessibility is focused, and the summary matches what you get after install.
- ★★★★★Maya Agarwal· Dec 16, 2024
Solid pick for teams standardizing on skills: macos-accessibility is focused, and the summary matches what you get after install.
- ★★★★★Dev Gupta· Dec 8, 2024
macos-accessibility is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Omar Brown· Nov 27, 2024
macos-accessibility reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Arya Gonzalez· Nov 19, 2024
Useful defaults in macos-accessibility — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Sakshi Patil· Nov 15, 2024
We added macos-accessibility from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Anika Abbas· Nov 7, 2024
We added macos-accessibility from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Soo Iyer· Oct 26, 2024
macos-accessibility fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Omar Patel· Oct 18, 2024
Registry listing for macos-accessibility matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Omar Mehta· Oct 10, 2024
I recommend macos-accessibility for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 42
1 / 5