What problem does it solve? Profiling native macOS and iOS apps with Instruments is error-prone: xctrace has non-obvious CLI syntax, LaunchServices can silently profile the wrong app bundle, and exporting stack data for analysis requires obscure XPath queries. This Skill provides the exact commands, gotchas, and verification steps to capture trustworthy performance traces. ## Core Features & Use Cases - CLI Trace Recording: Record Time Profiler traces via xctrace by launching a binary directly or attaching to a running PID, with time limits and output paths. - Correct Binary Targeting: Rules to ensure Instruments profiles your local build instead of an installed copy in /Applications, including process path verification. - Stack Export & Analysis: Export raw time-profile samples to XML via XPath for offline aggregation and automated diffing of stack data. - Use Case: Your macOS app's startup feels slow. Record a 60-second Time Profiler trace against the local build binary, export the time-profile table, and aggregate hot stacks in a script to find the bottleneck. ## Quick Start Ask the assistant to record a 60-second Time Profiler trace of your app binary with xctrace and export the hot stacks for analysis.