菜单
Load when a user provides an Instruments .trace bundle and wants performance, hang, lifecycle, thermal, or timeline analysis. Use the bundled script to export xctrace tables, summarize run windows, and correlate trace timestamps with session logs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build, launch, and capture debug logs from the iOS simulator. Use when you need to verify runtime behavior, measure timing, or diagnose issues without asking the user to manually capture logs.
Use when the user asks to visually test, touch, automate, or walk every Ensemble app surface across iOS/iPadOS and macOS, including agent-run UI sweeps, issue detection, reproduction, log inspection, fix-plan reports, platform parity checks, and repeatable screenshot/accessibility evidence runs.
Canonical Ensemble behavior policy router. Load before changing app behavior, playback, queue, offline/connectivity, downloads, sync/refresh, mutations, platform UI behavior, or verification expectations; update the relevant policy reference when implementation changes or clarifies behavior.
Plex Media Server API reference. Load when implementing or debugging Plex API integration.
Load before designing features, adding services, or touching multiple packages. Compact ownership, dependency, and subsystem rules for Ensemble.
Load when locating files, adding files, or checking package ownership. Compact map plus discovery commands; use rg for live file lists.
| name | trace-analysis |
| description | Load when a user provides an Instruments .trace bundle and wants performance, hang, lifecycle, thermal, or timeline analysis. Use the bundled script to export xctrace tables, summarize run windows, and correlate trace timestamps with session logs. |
Use this skill when a user provides an Instruments .trace bundle and wants a concrete read on what the trace does or does not confirm.
Primary command:
python3 .claude/skills/trace-analysis/scripts/analyze_trace.py /absolute/path/to/session.trace --run latest
Useful variants:
python3 .claude/skills/trace-analysis/scripts/analyze_trace.py /absolute/path/to/session.trace --run 8
python3 .claude/skills/trace-analysis/scripts/analyze_trace.py /absolute/path/to/session.trace --run 8 --output-dir /tmp/trace8-export
python3 .claude/skills/trace-analysis/scripts/analyze_trace.py /absolute/path/to/session.trace --run 8 --include-time-profile
python3 .claude/skills/trace-analysis/scripts/analyze_trace.py /absolute/path/to/session.trace --run 8 --symbol "MyType.myMethod"
open.creqgcd-perf-event--include-time-profile when you need deeper CPU sampling and can tolerate a slower export.hang-risks / potential-hangs does not mean the app was smooth. It only means Instruments did not record a qualifying hang.open.creq reports unsupported engineering types or topology warnings, note that some exports may still work even when Instruments UI is unreliable.trace-toc.xmllife-cycle-period.xmldevice-thermal-state-intervals.xmlhang-risks.xmlpotential-hangs.xmlgcd-perf-event.xmlregion-of-interest.xmlrunloop-events.xmltime-profile.xmlThe bundled script already looks for common hot paths in this repo:
OfflineDownloadServiceDownloadManagerLibraryViewModel.fetchAndMapInBackgroundLibraryRepository.fetchArtistsPlaybackServiceAudioPlaybackEngineSyncCoordinatorPlexAPIClientPlexWebSocketCoordinatorAdd extra --symbol values when you are investigating a narrower subsystem.