Agent skill

iOS Memgraph Leaks

by omarshahine in omarshahine/HomeClaw

Capture, inspect, compare, and root-cause iOS memory graph leaks using Apple's leaks and memgraph tools.

MITAuto-check passedDevelopment

Install iOS Memgraph Leaks

skills CLI
$ npx skills add omarshahine/HomeClaw --skill ios-memgraph-leaks -a claude-code

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

GitHub CLI
$ gh skill install omarshahine/HomeClaw ios-memgraph-leaks --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/omarshahine/HomeClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ios-memgraph-leaks .claude/skills/ios-memgraph-leaks && 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
ios-memgraph-leaks
GitHub stars
175
Used in
1 other repo
Token cost
~1k tokens
SKILL.md length
475 words
Files
4 (incl. scripts)
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Capture, inspect, compare, and root-cause iOS memory graph leaks using Apple's leaks and memgraph tools.

  • Works in 6 steps: Build, launch, and drive the exact flow… → Capture a memgraph from the running… → Summarize leaks with… → …
  • Debugging leaked iOS objects
  • SKILL.md covers Core Workflow, Capture, Summarize and Root Cause Rules, plus 1 more section
  • Runs Shell and Python scripts from its folder; calls xcrun

What it does

iOS Memgraph Leaks is an agent skill from omarshahine/HomeClaw. Capture, inspect, compare, and root-cause iOS memory graph leaks using Apple's leaks and memgraph tools. Use when debugging leaked iOS objects, simulator memgraphs, retain-cycle suspicions, memory growth after navigation/logout/account changes, or when asked to prove an iOS leak fix with before/after memgraph evidence.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `agents/openai.yaml`, `scripts/capture_sim_memgraph.sh` and `scripts/summarize_memgraph_leaks.py`).

It sits in Development, covering Root cause analysis. It works with iOS. The repository describes itself as: HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw. The licence is MIT.

When your agent uses it

  • Debugging leaked iOS objects
  • Simulator memgraphs
  • Retain-cycle suspicions
  • Memory growth after navigation/logout/account changes

Example prompts

  • “/ios-memgraph-leaks”

Requirements

  • Python 3
  • A Bash shell

Workflow steps

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

  1. Build, launch, and drive the exact flow that should release objects.
  2. Capture a memgraph from the running simulator process with scripts/capture_sim_memgraph.sh.
  3. Summarize leaks with scripts/summarize_memgraph_leaks.py.
  4. For each app-owned leaked type, inspect ownership with leaks --traceTree= and grouped leak evidence.
  5. Make the smallest root-cause patch, then recapture the same flow on the same simulator when possible.
  6. Report proof: before/after leak counts, disappeared root types, remaining leaks, memgraph paths, and test/build results.

What it can do on your machine

Read from SKILL.md and the folder at commit da69700. 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

    Ships 2 files in scripts/ (Shell and Python), which the agent can run.

    Shell commands in SKILL.md call:

    • xcrun

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

  • Network

    No URLs in SKILL.md.

    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

iOS Memgraph Leaks loads about 1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 475 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from omarshahine/HomeClaw at commit da69700, republished under its MIT licence (© omarshahine). 475 words, ~1,034 tokens.

Download SKILL.mdSave it as .claude/skills/ios-memgraph-leaks/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
ios-memgraph-leaks
description
Capture, inspect, compare, and root-cause iOS memory graph leaks using Apple's leaks and memgraph tools. Use when debugging leaked iOS objects, simulator memgraphs, retain-cycle suspicions, memory growth after navigation/logout/account changes, or when asked to prove an iOS leak fix with before/after memgraph evidence.

iOS Memgraph Leaks

Use this skill to prove iOS leaks from a live simulator process or an existing .memgraph. Pair it with ../ios-debugger-agent/SKILL.md when the task also needs simulator build, install, launch, UI driving, logs, or screenshots.

Core Workflow

  1. Build, launch, and drive the exact flow that should release objects.
  2. Capture a memgraph from the running simulator process with scripts/capture_sim_memgraph.sh.
  3. Summarize leaks with scripts/summarize_memgraph_leaks.py.
  4. For each app-owned leaked type, inspect ownership with leaks --traceTree=<address> <file.memgraph> and grouped leak evidence.
  5. Make the smallest root-cause patch, then recapture the same flow on the same simulator when possible.
  6. Report proof: before/after leak counts, disappeared root types, remaining leaks, memgraph paths, and test/build results.

Do not claim a leak fix from a smaller memgraph alone. A credible fix explains the ownership path that kept the object alive and shows that the same path or type disappears after the patch.

Capture

Prefer capturing from the simulator already used for the reproduction. Resolve the simulator UDID and app bundle identifier, then capture the running app:

bash
SKILL_DIR="<absolute path to this loaded skill folder>"
SIM="<simulator-udid>"
BUNDLE_ID="<app.bundle.identifier>"
MEMGRAPH_DIR="$(mktemp -d "${TMPDIR:-/tmp}/codex-ios-memgraph.XXXXXX")"

"$SKILL_DIR/scripts/capture_sim_memgraph.sh" \
  --udid "$SIM" \
  --bundle-id "$BUNDLE_ID" \
  --out-dir "$MEMGRAPH_DIR"

Do not derive SKILL_DIR from the target app repo's pwd; installed plugins usually live outside the app being debugged. Store captures in a run-specific temp or user-chosen folder, not under SKILL_DIR.

If the process cannot be found, confirm the bundle identifier and use xcrun simctl spawn "$SIM" launchctl list to inspect running labels.

Summarize

Summarize an existing memgraph:

bash
"$SKILL_DIR/scripts/summarize_memgraph_leaks.py" \
  /path/to/app.memgraph \
  --trace-limit 5 \
  --out /path/to/leak-summary.md

Use --trace-limit sparingly. Trace trees are useful root-cause evidence, but large memgraphs can produce noisy output. If a trace tree says Found 0 roots referencing, treat it as an unreachable/self-retained leak candidate and use the summary's grouped leak tree or leaks --groupByType <file.memgraph> to identify the retained fields and payload chain.

Show full SKILL.md (191 more words)Show less

Root Cause Rules

  • Identify the first app-owned leaked type in the leak output or trace.
  • Determine the intended lifetime: process, session, account, view, request, or task.
  • Treat lazy or deferred allocation as a scope reduction, not a leak fix, unless the original eager allocation itself violated the intended lifetime.
  • Prove retain-cycle claims with either a traceTree ownership path or an isolated reproduction.
  • For unreachable/self-cycle leaks, traceTree may have no root path; use leaks --groupByType plus source verification to find the self-retaining edge.
  • Do not claim success just because total leak count went down; prove the specific type or path disappeared.
  • Separate real root-cause branches from candidate/noise branches.
  • Prefer deleting the retaining edge over adding broad cleanup code.

Report

A useful leak report includes:

  • the exact flow and simulator/app build
  • the memgraph and summary paths
  • app-owned leaked types and counts
  • at least one ownership path, or grouped leak tree evidence when the object is unreachable from roots
  • the smallest proposed or applied retaining-edge fix
  • before/after evidence when a fix was made

If the memgraph shows only framework/runtime noise, say that and recommend the next narrower capture rather than inventing an app leak.

© omarshahine, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in .claude/skills/ios-memgraph-leaks of omarshahine/HomeClaw.

  • SKILL.md
  • agents/openai.yaml
  • scripts/capture_sim_memgraph.sh
  • scripts/summarize_memgraph_leaks.py

Open the folder on GitHubat commit da69700

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in omarshahine/HomeClaw, which our catalogue first saw on October 7, 2026.

Compare with similar skills

iOS Memgraph Leaks 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.

iOS Memgraph Leaks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
iOS Memgraph Leaks this skillomarshahine/HomeClaw1751 repos~1kAutomated safety check: PassMIT
AppsFlyer Unity Bridge DebuggingAppsFlyerSDK/appsflyer-unity-plugin178—~492Automated safety check: PassMIT
iOS FixMacMagazine/app-iOS170—~957Automated safety check: PassNone
Fix GitHub IssueShopify/flash-list7.2k—~1.6kAutomated safety check: PassMIT
QA Find Bugs Mobilebex-co/beancount-io296—~2.2kAutomated safety check: NotesMIT
Reverse Flowlingbol088-spec/reverse-flow-skill940—~2.4kAutomated safety check: PassMIT

Similar skills

  • AppsFlyer Unity Bridge Debugging

    AppsFlyerSDK/appsflyer-unity-plugin

    Traces a failing call or callback between C# and the native Android or iOS wrappers of the AppsFlyer Unity plugin to find the first broken link.

    178 GitHub stars~492 tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • iOS Fix

    MacMagazine/app-iOS

    Bug-fix and refactoring workflow for MacMagazine — root cause analysis, pattern-matching fix, regression verification.

    170 GitHub stars~957 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Fix GitHub Issue

    Shopify/flash-list

    Official

    Full workflow for fixing a GitHub issue - understand the problem, reproduce, diagnose root cause, fix, test on iOS/Android simulators, review, and raise a PR

    7.2k GitHub stars~1.6k tokensUpdated 9 days ago
    DevelopmentAuto-check passed
  • QA Find Bugs Mobile

    bex-co/beancount-io

    Hunt bugs in the running Beancount mobile app using local Expo MCP on the iPhone 17e simulator, sign in with QAEMAIL and QAPASSWORD, reproduce failures, trace root causes, and deduplicate findings.

    296 GitHub stars~2.2k tokensUpdated today
    MobileAuto-check: notes
  • Reverse Flow

    lingbol088-spec/reverse-flow-skill

    Guided reverse engineering workflow for binaries, firmware, mobile apps, scripts, document samples, protocol captures, and unknown artifacts.

    940 GitHub stars~2.4k tokensUpdated 2 mo ago
    SecurityAuto-check passed
  • Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.

    6.4k GitHub stars~5k tokensUpdated today
    DevelopmentAuto-check passed

More from omarshahine/HomeClaw

All 14 skills in this repo
  • Swiftui Expert Skill

    omarshahine/HomeClaw

    A skill your agent uses when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management, view composition, performance, Liquid Glass adoption, or Instruments .trace…

    175 GitHub starsUsed in 4 repos~2.8k tokens
    Auto-check passed
  • Spm Build Analysis

    omarshahine/HomeClaw

    Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds.

    175 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Xcode Build Benchmark

    omarshahine/HomeClaw

    Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts.

    175 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Xcode Build Fixer

    omarshahine/HomeClaw

    Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement.

    175 GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed
  • Xcode Build Orchestrator

    omarshahine/HomeClaw

    Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to…

    175 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed
  • Xcode Compilation Analyzer

    omarshahine/HomeClaw

    Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan.

    175 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Works with

Questions about iOS Memgraph Leaks

What does iOS Memgraph Leaks do?

Capture, inspect, compare, and root-cause iOS memory graph leaks using Apple's leaks and memgraph tools. iOS Memgraph Leaks is an agent skill from omarshahine/HomeClaw. Capture, inspect, compare, and root-cause iOS memory graph leaks using Apple's leaks and memgraph tools.

When should I use iOS Memgraph Leaks?

iOS Memgraph Leaks fits situations like: debugging leaked iOS objects; simulator memgraphs; retain-cycle suspicions; memory growth after navigation/logout/account changes.

How do I install iOS Memgraph Leaks in Claude Code?

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

How do I install iOS Memgraph Leaks in Codex?

Run `npx skills add omarshahine/HomeClaw --skill ios-memgraph-leaks -a codex`. Or copy the skill folder (.claude/skills/ios-memgraph-leaks in omarshahine/HomeClaw) into .agents/skills/ios-memgraph-leaks in your project. Codex loads it when a task matches its description.

Can I use iOS Memgraph Leaks 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 omarshahine/HomeClaw --skill ios-memgraph-leaks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ios-memgraph-leaks, .gemini/skills/ios-memgraph-leaks, .github/skills/ios-memgraph-leaks and .opencode/skills/ios-memgraph-leaks in your project.

What does iOS Memgraph Leaks need to run?

Going by SKILL.md and its folder, iOS Memgraph Leaks needs a shell and Python for the scripts in its folder and the command-line tools its instructions call (xcrun). Our summary lists: Python 3; A Bash shell.

Does iOS Memgraph Leaks access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is iOS Memgraph Leaks 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does iOS Memgraph Leaks use?

iOS Memgraph Leaks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does iOS Memgraph Leaks use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to iOS Memgraph Leaks?

Skills that share tags, products or a category with iOS Memgraph Leaks: AppsFlyer Unity Bridge Debugging (AppsFlyerSDK/appsflyer-unity-plugin, 178 stars), iOS Fix (MacMagazine/app-iOS, 170 stars), Fix GitHub Issue (Shopify/flash-list, 7.2k stars) and QA Find Bugs Mobile (bex-co/beancount-io, 296 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains iOS Memgraph Leaks?

omarshahine (a GitHub user) maintains it in omarshahine/HomeClaw, which has 175 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.

Source: omarshahine/HomeClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.