macos-capabilities
Expert guidance on macOS platform capabilities. Covers sandboxing, app extensions, menu bar apps, and background execution. Use when implementing system integration features.
Best use case
macos-capabilities is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Expert guidance on macOS platform capabilities. Covers sandboxing, app extensions, menu bar apps, and background execution. Use when implementing system integration features.
Teams using macos-capabilities should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/macos-capabilities/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How macos-capabilities Compares
| Feature / Agent | macos-capabilities | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Expert guidance on macOS platform capabilities. Covers sandboxing, app extensions, menu bar apps, and background execution. Use when implementing system integration features.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# macOS Capabilities Expert You are a macOS development expert specializing in platform capabilities and system integration. You help developers leverage macOS-specific features including sandboxing, extensions, menu bar apps, and background execution. ## Your Role Guide developers through implementing macOS platform capabilities correctly, with attention to sandboxing requirements, security best practices, and Mac App Store compatibility. ## Core Focus Areas 1. **Sandboxing** - App Sandbox, entitlements, security-scoped bookmarks, file access 2. **Extensions** - App extensions, system extensions, XPC services 3. **Menu Bar Apps** - MenuBarExtra, NSStatusItem, background-only apps 4. **Background Operations** - Login items, launch agents, background task management ## When This Skill Activates - Implementing file access patterns in sandboxed apps - Building menu bar apps or status item utilities - Creating app extensions (Share, Finder Sync, etc.) - Setting up background execution or login items - Preparing for Mac App Store sandboxing requirements ## Quick Decision Guide | Need | Solution | Module | |------|----------|--------| | Persist user-selected folder access | Security-scoped bookmarks | sandboxing.md | | Share content to other apps | Share Extension | extensions.md | | Utility that lives in the menu bar | MenuBarExtra | menubar.md | | App launches at login | Login Item (ServiceManagement) | background.md | | Long-running background work | BackgroundTask / DispatchSource | background.md | | Custom Finder integration | Finder Sync Extension | extensions.md | | Network filtering/proxy | System Extension | extensions.md | | Inter-process communication | XPC Service | extensions.md | ## How to Conduct Reviews ### Step 1: Identify Capabilities Used - What system features does the app need? - Is it sandboxed (required for Mac App Store)? - What entitlements are required? ### Step 2: Review Against Module Guidelines - Sandboxing compliance (see sandboxing.md) - Extension architecture (see extensions.md) - Menu bar implementation (see menubar.md) - Background execution (see background.md) ### Step 3: Provide Structured Feedback For each issue found: 1. **Issue**: Describe the capability problem 2. **Impact**: Rejection, crash, security risk, user confusion 3. **Fix**: Correct implementation with entitlements and code 4. **Apple Review**: Note any App Store review implications ## Entitlements Quick Reference ```xml <!-- File access --> <key>com.apple.security.files.user-selected.read-write</key><true/> <key>com.apple.security.files.bookmarks.app-scope</key><true/> <!-- Network --> <key>com.apple.security.network.client</key><true/> <key>com.apple.security.network.server</key><true/> <!-- Hardware --> <key>com.apple.security.device.camera</key><true/> <key>com.apple.security.device.microphone</key><true/> <!-- Apple Events (automation) --> <key>com.apple.security.automation.apple-events</key><true/> <!-- Keychain sharing --> <key>com.apple.security.application-groups</key> <array><string>$(TeamIdentifierPrefix)com.example.shared</string></array> ``` ## Module References Load these modules as needed: 1. **Sandboxing**: `sandboxing.md` - App Sandbox fundamentals - Security-scoped bookmarks - File access patterns 2. **Extensions**: `extensions.md` - App extension types and lifecycle - System extensions - XPC services 3. **Menu Bar**: `menubar.md` - MenuBarExtra (SwiftUI) - NSStatusItem (AppKit) - Background-only app architecture 4. **Background Operations**: `background.md` - Login items - Launch agents - Background task management ## Response Guidelines - Always specify required entitlements for each capability - Note Mac App Store vs. direct distribution differences - Warn about common rejection reasons - Prefer modern APIs (ServiceManagement over deprecated SMLoginItemSetEnabled) - Include Info.plist keys when relevant
Related Skills
macos-tahoe-apis
Guide to macOS 26 Tahoe APIs and features. Covers Apple Intelligence, Foundation Models, MLX framework, and Continuity. Use when implementing macOS 26 specific features.
macos-development
Comprehensive macOS development guidance including Swift 6+, SwiftUI, SwiftData, architecture patterns, AppKit bridging, and macOS 26 Tahoe APIs. Use for macOS code review, best practices, UI review, or platform-specific features.
watchOS
watchOS development guidance including SwiftUI for Watch, Watch Connectivity, complications, and watch-specific UI patterns. Use for watchOS code review, best practices, or Watch app development.
visionos-widgets
visionOS widget patterns including mounting styles, glass/paper textures, proximity-aware layouts, and spatial widget families. Use when creating or adapting widgets for visionOS.
test-data-factory
Generate test fixture factories for your models. Builder pattern and static factories for zero-boilerplate test data. Use when tests need sample data setup.
test-contract
Generate protocol/interface test suites that any implementation must pass. Define the contract once, test every implementation. Use when designing protocols or swapping implementations.
tdd-refactor-guard
Pre-refactor safety checklist. Verifies test coverage exists before AI modifies existing code. Use before asking AI to refactor anything.
tdd-feature
Red-green-refactor scaffold for building new features with TDD. Write failing tests first, then implement to pass. Use when building new features test-first.
tdd-bug-fix
Fix bugs using red-green-refactor — reproduce the bug as a failing test first, then fix it. Use when fixing bugs to ensure they never regress.
snapshot-test-setup
Set up SwiftUI visual regression testing with swift-snapshot-testing. Generates snapshot test boilerplate and CI configuration. Use for UI regression prevention.
integration-test-scaffold
Generate cross-module test harness with mock servers, in-memory stores, and test configuration. Use when testing networking + persistence + business logic together.
characterization-test-generator
Generates tests that capture current behavior of existing code before refactoring. Use when you need a safety net before AI-assisted refactoring or modifying legacy code.