SkillAgentSearch skills...

ios-ettrace-performance

Use when capturing or analyzing ETTrace profiles for a focused iOS launch or runtime flow, including exact-build dSYM UUID matching, Simulator or device capture, processed per-thread flamegraph JSON, sampled inclusive/exclusive time, unresolved symbols, and comparable verification.

Install / Use

npx skills add dpearson2699/swift-ios-skills --skill ios-ettrace-performance

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of ios-ettrace-performance

ios-ettrace-performance scores 87/100 on our quality scale, 2206th of 4,698 Development & Engineering skills we index (top 47%).

Its SKILL.md is 8.5 KB long, well organised into 15 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

With 1,143 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-02 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 86/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

ios-ettrace-performance compared with similar skills

All 4 of these similar skills score higher than ios-ettrace-performance; compare them before choosing.

SkillScoreStarsUpdatedFormat
ios-ettrace-performance (this skill)by dpearson2699871.1k4mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install ios-ettrace-performance?
Run npx skills add dpearson2699/swift-ios-skills --skill ios-ettrace-performance. The install tabs above show the steps for each supported agent.
Which AI agents does ios-ettrace-performance work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is ios-ettrace-performance safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 86/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is ios-ettrace-performance still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: ios-ettrace-performance description: "Use when capturing or analyzing ETTrace profiles for a focused iOS launch or runtime flow, including exact-build dSYM UUID matching, Simulator or device capture, processed per-thread flamegraph JSON, sampled inclusive/exclusive time, unresolved symbols, and comparable verification. Use debugging-instruments or swiftui-performance for generic profiling instead."

iOS ETTrace Performance

Use ETTrace for a bounded, symbolicated sampling experiment. Treat capture conditions and symbolication as part of the evidence, not as setup trivia.

Contents

Boundary

This skill owns ETTrace framework/CLI capture, exact-build dSYMs, processed flamegraph JSON, and like-for-like verification. Use Instruments for broad CPU, hitch, energy, or concurrency triage. Use SwiftUI performance guidance for view identity, invalidation, and layout remediation.

ETTrace periodically samples thread stacks. Its durations reconstruct sampled attribution from those intervals; do not present them as wall-clock production timings or compare them directly with a differently configured profiler.

Capture Contract

Write these down before capturing:

  • one exact user flow and its start/stop boundary;
  • launch capture or already-running runtime capture;
  • app commit, build configuration, optimization settings, and architecture;
  • ETTrace runner and framework versions, plus single-thread or multi-thread mode;
  • simulator/device model and OS build;
  • launch method, data state, cache state, and repetition count.

Reject a before/after claim when any of these materially differ. Rebuild and repeat under one contract instead.

Workflow

1. Triage before instrumenting

Confirm that ETTrace's sampled flamechart is the right next tool. Prefer Instruments first when the slow interval is unknown, spans many subsystems, or needs system-level blocking, I/O, hitch, or concurrency context.

Choose one flow small enough to repeat. Launch, first screen construction, opening one document, or applying one edit are useful boundaries; "use the app" is not.

2. Record and hold ETTrace versions fixed

Install the runner from the official tap and link the ETTrace package product into the app target being measured. Record the runner version and the framework revision or tag separately, then keep both fixed across compared captures. The bundled analyzer supports the verified v1.1.1 processed output shape; re-check upstream and the parser before using a different format.

brew install emergetools/homebrew-tap/ettrace

Run the instrumented app once and confirm the Starting ETTrace log. Absence of that message means capture evidence is not trustworthy. Keep this wiring out of shipping configurations unless the project deliberately owns that tradeoff.

3. Build first, then collect matching dSYMs

Use the final instrumented build for both capture and dSYM collection. Never choose a dSYM by filename, modification time, or Derived Data proximity.

mkdir -p /tmp/myapp-ettrace
python3 scripts/collect_dsyms.py \
  --app /path/to/Build/Products/Release-iphonesimulator/MyApp.app \
  --search-root /path/to/Build/Products \
  --search-root /path/to/Archives \
  --output /tmp/myapp-ettrace/dsyms \
  --pretty > /tmp/myapp-ettrace/dsym-report.json

The helper compares dwarfdump --uuid output for the app executable and embedded binaries. Missing or ambiguous UUID matches stop the run by default. Read and preserve dsym-report.json rather than assuming every copied symbol file is relevant. The helper fails when UUID matches cannot be copied to unique flat destination names that ETTrace 1.1.1 can discover.

4. Capture from a clean artifact directory

Run ETTrace from an empty directory because processed files are written to the current working directory. Use --simulator for Simulator and --dsyms for the exact dSYM directory. Add --launch only for launch work, and follow the runner's two-launch prompts exactly.

mkdir -p /tmp/myapp-ettrace
mkdir /tmp/myapp-ettrace/run-01
cd /tmp/myapp-ettrace/run-01
ettrace --simulator --dsyms /tmp/myapp-ettrace/dsyms

The second mkdir must fail if that per-run directory already exists. Choose a new run name instead of mixing processed captures from retries.

Launch by tapping the app on the Home Screen when the runner asks. Launching from Xcode can change the launch path and timing. For device capture, omit --simulator; keep all other experiment fields stable.

Stop immediately after the bounded flow and preserve every fresh output_<threadId>.json with the capture contract. ETTrace 1.1.1 creates these processed files after symbolication. Its internal raw runner output.json is a different artifact and is not accepted by the analyzer below.

5. Validate and summarize processed output

python3 scripts/analyze_ettrace.py \
  /tmp/myapp-ettrace/run-01/output_*.json \
  --top 25 --pretty > /tmp/myapp-ettrace/run-01/summary.json

The helper validates the v1.1.1 processed node shape, rejects duplicate inputs or mixed osBuild/device/isSimulator metadata, handles the serializer's object-or-array children field, and emits deterministic JSON. It does not rewrite the capture files. Keep those originals beside the summary.

Stop and repair symbolication when important app frames are <unknown>, raw addresses, or attributed to the wrong binary. An unsymbolicated hot address is an evidence gap, not a code recommendation. ETTrace 1.1.1 address-bearing nodes are listed under unresolved_frames and excluded from ordinary hotspots.

6. Change one cause and repeat

Make the smallest code or configuration change supported by a hot app-owned path. Rebuild, recollect UUID-matched dSYMs, and capture the same flow at least twice. Report variance and the full capture contract with the result.

Interpret the Report

  • Exclusive seconds approximate sampled time charged directly to a symbol after subtracting direct child durations. Start with high exclusive app-owned work.
  • Inclusive seconds show the weight of an entire call subtree. Use them to find expensive entry paths, not to blame every parent frame.
  • Aggregated inclusive time can exceed the root duration because recursive or nested appearances count each frame. Exclusive percentages use root duration.
  • <unattributed> is reported separately. A large value weakens conclusions about what happened in the missing interval.
  • A framework hotspot may still be caused by app call frequency, data shape, or configuration. Walk upward to the first controllable app-owned caller.
  • Multi-thread files sum thread time, not wall-clock latency. Do not describe their combined root duration as elapsed time.

Common Mistakes

  • Profiling an unbounded session and then guessing which samples match the bug.
  • Capturing one build while supplying dSYMs from another build or architecture.
  • Treating ETTrace's raw runner JSON as a processed flamegraph.
  • Comparing launch capture with runtime capture, or single-thread with multi-thread capture.
  • Optimizing the top inclusive parent without inspecting exclusive work and child paths.
  • Claiming improvement from one noisy run.
  • Leaving ETTrace instrumentation in production by accident.

Review Checklist

  • [ ] One reproducible flow and start/stop boundary are recorded.
  • [ ] Launch/runtime capture mode, single/multi-thread mode, runner version, and framework revision match.
  • [ ] Build configuration, architecture, target/OS, launch method, and app data/cache state match.
  • [ ] Every capture starts in a fresh, empty per-run artifact directory.
  • [ ] App and embedded-binary UUIDs match the supplied dSYMs.
  • [ ] The dSYM collection JSON report is preserved with source/destination and missing, ambiguous, collision, or incompatibility evidence.
  • [ ] Processed output_<threadId>.json files are preserved unchanged.
  • [ ] Important app frames are symbolicated.
  • [ ] Exclusive, inclusive, unattributed, and multi-thread semantics are clear.
  • [ ] The recommendation names an app-controlled path and supporting evidence.
  • [ ] Verification repeats the same contract and reports more than one run.
  • [ ] Temporary instrumentation is removed or intentionally scoped.

References

Related Skills

View on GitHub
GitHub Stars1.1k
CategoryDevelopment
Updated3mo ago
Forks58

Languages

Python

Trust signals

86/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 info
ios-ettrace-performance — Universal Skill: Install & Safety Check | SkillAgent