LogoAwesome Skills
  • Search
  • Category
  • Tag
  • Blog
LogoAwesome Skills
LogoAwesome Skills

Discover Open-Source Agent Skills for AI Coding Assistants

Product

  • Search
  • Category
  • Tag
  • Blog

Resources

  • Claude Skill Docs
  • Antigravity Skills Docs

Tools

  • Claude Code
  • OpenCode
  • Cursor
  • Codex
  • Antigravity

Company

  • Privacy Policy
  • Terms of Service
  • Sitemap

©2026 Awesome Skills. All rights reserved.

Privacy PolicyTerms
Back to Skills

native-app-performance

Native macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces. Use when asked to profile, attach, record, or analyze Instruments .trace files, find hotspots, or optimize native app performance without opening Instruments UI.

1,738stars165forksUpdated 2/10/2026
Developer Tools#ios#performance-profiling#macos#command-line#optimization#xctrace

Security Assessment

Safe(100/100)
Security Score100/100

About native-app-performance

The 'native-app-performance' skill provides a powerful CLI-based solution for profiling macOS/iOS app performance without needing to open the Instruments UI. By leveraging xctrace's Time Profiler template and offering a set of Python scripts for analyzing .trace files, this skill enables users to efficiently detect performance bottlenecks, extract time samples, symbolicate, and rank hotspots. It allows developers to focus on app performance optimization directly from the command line, offering an essential toolset for anyone looking to improve the efficiency of native apps on macOS/iOS platforms.

FAQ

How do I record a Time Profiler trace for an existing app?

You can record a Time Profiler trace by using the command `xcrun xctrace record --template 'Time Profiler' --time-limit 90s --output /tmp/App.trace --attach <pid>` after starting the app. Alternatively, you can launch the app directly using `--launch`.

What is the purpose of extracting time samples from a trace?

Extracting time samples from a trace helps you capture detailed performance data of the app, which can then be analyzed to identify slow or inefficient parts of the application.

Is there a way to analyze performance without opening the Instruments UI?

Yes, this skill is designed for CLI-only usage, allowing you to analyze Instruments .trace files without launching the Instruments UI. You can symbolicate and rank hotspots directly via command-line scripts.

What are the system requirements for using this skill?

The skill requires macOS/iOS devices, along with the 'xcrun' tool for running xctrace commands. It also requires Python scripts for sample extraction and hotspot ranking, and the appropriate binary paths for symbolication.

Can I use this skill for apps not built locally?

It is recommended to use the direct binary path for profiling, especially for local builds. If profiling apps from `/Applications`, ensure you're working with the correct binary and symbols to avoid discrepancies.

Install native-app-performance

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

steipete/agent-scripts

Related Skills

import-on-interaction

256

radon-mcp

296

investigating-incidents-with-aws-devops-agent

2,945

mantis-structural-index

2,518