Agent skill

Debugging Instruments

by dpearson2699 in dpearson2699/swift-ios-skills

Debug iOS apps and profile performance using LLDB, the interactive Memory Graph Debugger, and Instruments.

Custom licenceAuto-check passedDevelopment

Install Debugging Instruments

skills CLI
$ npx skills add dpearson2699/swift-ios-skills --skill debugging-instruments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dpearson2699/swift-ios-skills debugging-instruments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dpearson2699/swift-ios-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/debugging-instruments .claude/skills/debugging-instruments && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debugging-instruments
GitHub stars
1.2k
Token cost
~3.6k tokens
SKILL.md length
1,095 words
Files
4 (incl. references)
Skills in repo
86
Repo updated
First seen
Licence
Custom licence

At a glance

Debug iOS apps and profile performance using LLDB, the interactive Memory Graph Debugger, and Instruments.

  • Works in 4 steps: Reproduce in a Debug build and stop at… → Inspect locals without executing code,… → Move to the relevant frame or thread and… → …
  • Retain-cycle inspection
  • SKILL.md covers Contents, LLDB Debugging, Memory Debugging and Hang Diagnostics, plus 5 more sections
  • Calls xcrun

What it does

Debugging Instruments is an agent skill from dpearson2699/swift-ios-skills. Debug iOS apps and profile performance using LLDB, the interactive Memory Graph Debugger, and Instruments. Use for crashes, retain-cycle inspection, hangs, build failures, and generic CPU, memory, energy, or network profiling. Use ios-memgraph-analysis for .memgraph capture, leaks CLI ownership paths, or persistent heap growth; use ios-ettrace-performance for ETTrace capture and JSON.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/evals.json`, `references/instruments-guide.md` and `references/lldb-patterns.md`).

It sits in Development, covering iOS development, Debugging and Performance optimization. It works with iOS. The repository describes itself as: Agent Skills for iOS 26+, Swift 6.3, SwiftUI, and modern Apple frameworks.

When your agent uses it

  • Retain-cycle inspection
  • Network profiling

Example prompts

  • “/debugging-instruments”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Reproduce in a Debug build and stop at the narrowest useful breakpoint.
  2. Inspect locals without executing code, then capture the current stack.
  3. Move to the relevant frame or thread and verify the failing state.
  4. Add a condition or watchpoint only when the bad transition is still unclear.

What it can do on your machine

Read from SKILL.md and the folder at commit 8d90fd1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • xcrun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • sosumi.ai
    • developer.apple.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debugging Instruments loads about 3.6k tokens when it runs, and up to ~9.2k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 1,095 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,095 words (~3,606 tokens).

“Keep interactive graph and Instruments triage here. Route detailed .memgraph command-line ownership/growth analysis and ETTrace work to their focused skills.”

— opening of SKILL.md by dpearson2699, Custom licence
name
debugging-instruments

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files (references) in skills/debugging-instruments of dpearson2699/swift-ios-skills.

  • SKILL.md
  • evals/evals.json
  • references/instruments-guide.md
  • references/lldb-patterns.md

Open the folder on GitHubat commit 8d90fd1

Compare with similar skills

Debugging Instruments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debugging Instruments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debugging Instruments this skilldpearson2699/swift-ios-skills1.2k—~3.6kAutomated safety check: PassCustom licence
Mobile App Debuggingsecondsky/claude-skills227—~513Automated safety check: PassMIT
Native App Performanceharperreed/dotfiles3344 repos~538Automated safety check: PassNone
iOS Crash Log Debuggingconorluddy/xclaude-plugin183—~4.9kAutomated safety check: PassMIT
Performance Profilingconorluddy/xclaude-plugin183—~7.3kAutomated safety check: PassMIT
Apple Crash Log .NET Symbolicationdotnet/skills5.6k1 repos~2.4kAutomated safety check: PassMIT

Similar skills

  • Mobile App Debugging

    secondsky/claude-skills

    Mobile app debugging for iOS, Android, cross-platform frameworks.

    227 GitHub stars~513 tokensUpdated 9 days ago
    MobileAuto-check passed
  • Native App Performance

    harperreed/dotfiles

    Native macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces.

    334 GitHub starsUsed in 4 repos~538 tokens
    DevelopmentAuto-check passed
  • iOS Crash Log Debugging

    conorluddy/xclaude-plugin

    Walks through retrieving, symbolicating and diagnosing iOS crash logs, turning a cryptic stack trace into the function names that actually failed.

    183 GitHub stars~4.9k tokensUpdated 25 days ago
    DevelopmentAuto-check passed
  • Performance Profiling

    conorluddy/xclaude-plugin

    Instruments integration and performance analysis workflows for iOS apps.

    183 GitHub stars~7.3k tokensUpdated 25 days ago
    DevelopmentAuto-check passed
  • Official

    Resolves .NET runtime frames in Apple .ips crash logs to function names, source files and line numbers using dSYM symbols, atos and the Microsoft symbol server.

    5.6k GitHub starsUsed in 1 repo~2.4k tokens
    MobileAuto-check passed
  • C Bounds Safety

    superagents-lab/xcode27-skills

    Guide for the C -fbounds-safety language extension. An agent skill from superagents-lab/xcode27-skills.

    337 GitHub stars~732 tokensUpdated 4 mo ago
    MobileAuto-check passed

More from dpearson2699/swift-ios-skills

All 86 skills in this repo
  • iOS Memgraph Analysis

    dpearson2699/swift-ios-skills

    A skill your agent uses when capturing or analyzing an iOS .memgraph, especially when the task mentions a memory leak, heap growth, persistent memory increase, ownership path, or matched-capture…

    1.2k GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed
  • Natural Language

    dpearson2699/swift-ios-skills

    Tokenize, tag, and analyze natural language text using Apple's NaturalLanguage framework and translate between languages with the Translation framework.

    1.2k GitHub starsUsed in 1 repo~3.5k tokens
    Auto-check passed
  • iOS Ettrace Performance

    dpearson2699/swift-ios-skills

    A skill your agent uses 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…

    1.2k GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Accessorysetupkit

    dpearson2699/swift-ios-skills

    Discover and configure Bluetooth and Wi-Fi accessories using AccessorySetupKit.

    1.2k GitHub stars~3.5k tokensUpdated 2 mo ago
    Auto-check passed
  • Activitykit

    dpearson2699/swift-ios-skills

    Implement, review, or improve Live Activities and Dynamic Island experiences in iOS apps using ActivityKit.

    1.2k GitHub stars~4.6k tokensUpdated 2 mo ago
    Auto-check passed
  • Adattributionkit

    dpearson2699/swift-ios-skills

    Measure ad effectiveness with privacy-preserving attribution using AdAttributionKit.

    1.2k GitHub stars~3.5k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Debugging Instruments

What does Debugging Instruments do?

Debug iOS apps and profile performance using LLDB, the interactive Memory Graph Debugger, and Instruments. Debugging Instruments is an agent skill from dpearson2699/swift-ios-skills. Debug iOS apps and profile performance using LLDB, the interactive Memory Graph Debugger, and Instruments.

When should I use Debugging Instruments?

Debugging Instruments fits situations like: retain-cycle inspection; network profiling.

How do I install Debugging Instruments in Claude Code?

Run `npx skills add dpearson2699/swift-ios-skills --skill debugging-instruments -a claude-code`. Or copy the skill folder (skills/debugging-instruments in dpearson2699/swift-ios-skills) into .claude/skills/debugging-instruments in your project. Claude Code loads it when a task matches its description.

How do I install Debugging Instruments in Codex?

Run `npx skills add dpearson2699/swift-ios-skills --skill debugging-instruments -a codex`. Or copy the skill folder (skills/debugging-instruments in dpearson2699/swift-ios-skills) into .agents/skills/debugging-instruments in your project. Codex loads it when a task matches its description.

Can I use Debugging Instruments in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dpearson2699/swift-ios-skills --skill debugging-instruments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-instruments, .gemini/skills/debugging-instruments, .github/skills/debugging-instruments and .opencode/skills/debugging-instruments in your project.

What does Debugging Instruments need to run?

Going by SKILL.md and its folder, Debugging Instruments needs the command-line tools its instructions call (xcrun).

Does Debugging Instruments access the network?

SKILL.md names 2 domains. As links in the text: sosumi.ai and developer.apple.com. This is read from the text; nothing was executed.

Is Debugging Instruments safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Debugging Instruments use?

Debugging Instruments has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Debugging Instruments use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.6k tokens, read only when the agent opens those files.

What are the alternatives to Debugging Instruments?

Skills that share tags, products or a category with Debugging Instruments: Mobile App Debugging (secondsky/claude-skills, 227 stars), Native App Performance (harperreed/dotfiles, 334 stars), iOS Crash Log Debugging (conorluddy/xclaude-plugin, 183 stars) and Performance Profiling (conorluddy/xclaude-plugin, 183 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debugging Instruments?

dpearson2699 (a GitHub user) maintains it in dpearson2699/swift-ios-skills, which has 1,173 GitHub stars. The repository holds 86 skills in this directory. The repository was last updated on July 31, 2026.

Source: dpearson2699/swift-ios-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.