[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6GEK95MBCSN2MZYKB85R5":3,"skill-same:01M7E6GEK95MBCSN2MZYKB85R5":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7E6GEK95MBCSN2MZYKB85R5","ios-memgraph-leaks",null,"Capture and inspect iOS leaks and memgraphs. Use when debugging leaked objects, retain cycles, memory growth, or before\u002Fafter leak evidence.","wxdwu\u002Fnew-api","wxdwu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80968397?v=4","01M7E6AEMB59N90BKXD77EC83D","Xudong Wu","01M7E6AEMY2BXCDVZ9MJJHFQ4C",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-ios-apps\u002Fskills\u002Fios-memgraph-leaks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ios-memgraph-leaks\ndescription: Capture and inspect iOS leaks and memgraphs. Use when debugging leaked objects, retain cycles, memory growth, or before\u002Fafter leak evidence.\n---\n\n# iOS Memgraph Leaks\n\nUse this skill to prove iOS leaks from a live simulator process or an existing `.memgraph`. Pair it with `..\u002Fios-debugger-agent\u002FSKILL.md` when the task also needs simulator build, install, launch, UI driving, logs, or screenshots.\n\n## Core Workflow\n\n1. Build, launch, and drive the exact flow that should release objects.\n2. Capture a memgraph from the running simulator process with `scripts\u002Fcapture_sim_memgraph.sh`.\n3. Summarize leaks with `scripts\u002Fsummarize_memgraph_leaks.py`.\n4. For each app-owned leaked type, inspect ownership with `leaks --traceTree=\u003Caddress> \u003Cfile.memgraph>` and grouped leak evidence.\n5. Make the smallest root-cause patch, then recapture the same flow on the same simulator when possible.\n6. Report proof: before\u002Fafter leak counts, disappeared root types, remaining leaks, memgraph paths, and test\u002Fbuild results.\n\nDo 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.\n\n## Capture\n\nPrefer capturing from the simulator already used for the reproduction. Resolve the simulator UDID and app bundle identifier, then capture the running app:\n\n```bash\nSKILL_DIR=\"\u003Cabsolute path to this loaded skill folder>\"\nSIM=\"\u003Csimulator-udid>\"\nBUNDLE_ID=\"\u003Capp.bundle.identifier>\"\nMEMGRAPH_DIR=\"$(mktemp -d \"${TMPDIR:-\u002Ftmp}\u002Fcodex-ios-memgraph.XXXXXX\")\"\n\n\"$SKILL_DIR\u002Fscripts\u002Fcapture_sim_memgraph.sh\" \\\n  --udid \"$SIM\" \\\n  --bundle-id \"$BUNDLE_ID\" \\\n  --out-dir \"$MEMGRAPH_DIR\"\n```\n\nDo 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`.\n\nIf the process cannot be found, confirm the bundle identifier and use `xcrun simctl spawn \"$SIM\" launchctl list` to inspect running labels.\n\n## Summarize\n\nSummarize an existing memgraph:\n\n```bash\n\"$SKILL_DIR\u002Fscripts\u002Fsummarize_memgraph_leaks.py\" \\\n  \u002Fpath\u002Fto\u002Fapp.memgraph \\\n  --trace-limit 5 \\\n  --out \u002Fpath\u002Fto\u002Fleak-summary.md\n```\n\nUse `--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\u002Fself-retained leak candidate and use the summary's grouped leak tree or `leaks --groupByType \u003Cfile.memgraph>` to identify the retained fields and payload chain.\n\n## Root Cause Rules\n\n- Identify the first app-owned leaked type in the leak output or trace.\n- Determine the intended lifetime: process, session, account, view, request, or task.\n- Treat lazy or deferred allocation as a scope reduction, not a leak fix, unless the original eager allocation itself violated the intended lifetime.\n- Prove retain-cycle claims with either a `traceTree` ownership path or an isolated reproduction.\n- For unreachable\u002Fself-cycle leaks, `traceTree` may have no root path; use `leaks --groupByType` plus source verification to find the self-retaining edge.\n- Do not claim success just because total leak count went down; prove the specific type or path disappeared.\n- Separate real root-cause branches from candidate\u002Fnoise branches.\n- Prefer deleting the retaining edge over adding broad cleanup code.\n\n## Report\n\nA useful leak report includes:\n\n- the exact flow and simulator\u002Fapp build\n- the memgraph and summary paths\n- app-owned leaked types and counts\n- at least one ownership path, or grouped leak tree evidence when the object is unreachable from roots\n- the smallest proposed or applied retaining-edge fix\n- before\u002Fafter evidence when a fix was made\n\nIf the memgraph shows only framework\u002Fruntime noise, say that and recommend the next narrower capture rather than inventing an app leak.\n","# iOS Memgraph Leaks\n\nUse this skill to prove iOS leaks from a live simulator process or an existing `.memgraph`. Pair it with `..\u002Fios-debugger-agent\u002FSKILL.md` when the task also needs simulator build, install, launch, UI driving, logs, or screenshots.\n\n## Core Workflow\n\n1. Build, launch, and drive the exact flow that should release objects.\n2. Capture a memgraph from the running simulator process with `scripts\u002Fcapture_sim_memgraph.sh`.\n3. Summarize leaks with `scripts\u002Fsummarize_memgraph_leaks.py`.\n4. For each app-owned leaked type, inspect ownership with `leaks --traceTree=\u003Caddress> \u003Cfile.memgraph>` and grouped leak evidence.\n5. Make the smallest root-cause patch, then recapture the same flow on the same simulator when possible.\n6. Report proof: before\u002Fafter leak counts, disappeared root types, remaining leaks, memgraph paths, and test\u002Fbuild results.\n\nDo 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.\n\n## Capture\n\nPrefer capturing from the simulator already used for the reproduction. Resolve the simulator UDID and app bundle identifier, then capture the running app:\n\n```bash\nSKILL_DIR=\"\u003Cabsolute path to this loaded skill folder>\"\nSIM=\"\u003Csimulator-udid>\"\nBUNDLE_ID=\"\u003Capp.bundle.identifier>\"\nMEMGRAPH_DIR=\"$(mktemp -d \"${TMPDIR:-\u002Ftmp}\u002Fcodex-ios-memgraph.XXXXXX\")\"\n\n\"$SKILL_DIR\u002Fscripts\u002Fcapture_sim_memgraph.sh\" \\\n  --udid \"$SIM\" \\\n  --bundle-id \"$BUNDLE_ID\" \\\n  --out-dir \"$MEMGRAPH_DIR\"\n```\n\nDo 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`.\n\nIf the process cannot be found, confirm the bundle identifier and use `xcrun simctl spawn \"$SIM\" launchctl list` to inspect running labels.\n\n## Summarize\n\nSummarize an existing memgraph:\n\n```bash\n\"$SKILL_DIR\u002Fscripts\u002Fsummarize_memgraph_leaks.py\" \\\n  \u002Fpath\u002Fto\u002Fapp.memgraph \\\n  --trace-limit 5 \\\n  --out \u002Fpath\u002Fto\u002Fleak-summary.md\n```\n\nUse `--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\u002Fself-retained leak candidate and use the summary's grouped leak tree or `leaks --groupByType \u003Cfile.memgraph>` to identify the retained fields and payload chain.\n\n## Root Cause Rules\n\n- Identify the first app-owned leaked type in the leak output or trace.\n- Determine the intended lifetime: process, session, account, view, request, or task.\n- Treat lazy or deferred allocation as a scope reduction, not a leak fix, unless the original eager allocation itself violated the intended lifetime.\n- Prove retain-cycle claims with either a `traceTree` ownership path or an isolated reproduction.\n- For unreachable\u002Fself-cycle leaks, `traceTree` may have no root path; use `leaks --groupByType` plus source verification to find the self-retaining edge.\n- Do not claim success just because total leak count went down; prove the specific type or path disappeared.\n- Separate real root-cause branches from candidate\u002Fnoise branches.\n- Prefer deleting the retaining edge over adding broad cleanup code.\n\n## Report\n\nA useful leak report includes:\n\n- the exact flow and simulator\u002Fapp build\n- the memgraph and summary paths\n- app-owned leaked types and counts\n- at least one ownership path, or grouped leak tree evidence when the object is unreachable from roots\n- the smallest proposed or applied retaining-edge fix\n- before\u002Fafter evidence when a fix was made\n\nIf the memgraph shows only framework\u002Fruntime noise, say that and recommend the next narrower capture rather than inventing an app leak.\n",{"name":5,"description":7},"main","dde9a06ab10bce3fe52058c783826590231f7df3","plugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-ios-apps\u002Fskills\u002Fios-memgraph-leaks","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api","https:\u002F\u002Fgithub.com\u002Fwxdwu","24120128@bjtu.edu.cn","I am Xudong Wu，a student in beijing jiaotong University, \"I am eager to learn on GitHub and contribute my part to this community.","2026-10-05 17:26:50",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add wxdwu\u002Fnew-api --skill ios-memgraph-leaks",{"tool":38,"command":39},"bunx","bunx skills add wxdwu\u002Fnew-api --skill ios-memgraph-leaks",{"tool":41,"command":42},"pnpm","pnpm dlx skills add wxdwu\u002Fnew-api --skill ios-memgraph-leaks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-ios-apps\u002Fskills\u002Fios-memgraph-leaks\u002FSKILL.md",true,[46,52,58],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",247,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-ios-apps\u002Fskills\u002Fios-memgraph-leaks\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fcapture_sim_memgraph.sh","SCRIPT","脚本",3118,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-ios-apps\u002Fskills\u002Fios-memgraph-leaks\u002Fscripts\u002Fcapture_sim_memgraph.sh",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fsummarize_memgraph_leaks.py",5769,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-ios-apps\u002Fskills\u002Fios-memgraph-leaks\u002Fscripts\u002Fsummarize_memgraph_leaks.py",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7E8SVA2N0JA09RW1XJYXCWX","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzotero\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7E8ST1FJAD5PWTW2FN1NSK0","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7E8SRW074NNNCZRCZA5T3Z1","setup-zoom-websockets","Use when building Zoom WebSockets.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7E8SPCFMD3YVPRX2MW8X3RA","setup-zoom-webhooks","Use when building Zoom webhooks.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebhooks\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7E8SMCH4RPCX8YSBNGWQCMP","zoom-virtual-agent-web","Zoom Virtual Agent SDK for web embeds. Use for campaign or entry ID chat launch, event-driven controls, user context updates, and CSP-safe deployment.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fweb\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7E8SJCAY323E36Z8SAP8H4M","zoom-virtual-agent-ios","Zoom Virtual Agent iOS integration via WKWebView. Use for Swift\u002FObjective-C script injection, message handlers, support_handoff relay, and URL routing policies.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fios\u002FSKILL.md",[],[]]