Show HN: Claude skill for Apple Instruments performance traces (iOS/Mac)(github.com)

5 pointsby jlreyes5 hours ago1 comment

HelloMCP5 hours ago
This feels like a preview of where debugging is going. Dashboards are good for people but we also need to make raw telemetry directly queryable by agents.
Curious how well this holds up across different traces. Instruments data can be pretty noisy and context-dependent. @jlreyes - do the derived views generalize, or do you end up encoding a lot of assumptions about what “jank” looks like?
- jlreyes4 hours ago
  Identifying bottlenecks is pretty generalizable. There is a distinction the skill tries to draw between targeting median FPS and P95, but from there the AI is quite good at narrowing to the relevant data.
  Where the AI trips up is getting distracted by aggregate signals instead of digging deep into root causing specific frame drops, but I see humans and existing tooling getting distracted by that too.
  Root causes are often context-dependent, but they tend to cluster into a handful of common issues. If you're able to enable the new swiftui instrument (from WWDC 2025), the entire attribute graph is encoded, and it can get you to the precise issue quite well.