[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EC78JBGS5ADJ1TENY25419":3,"skill-same:01M7EC78JBGS5ADJ1TENY25419":54},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7EC78JBGS5ADJ1TENY25419","dwarf-expert",null,"Analyzes DWARF debug information in compiled binaries. Use when inspecting .debug_* sections, DIE trees, or DW_TAG_\u002FDW_AT_ entries with dwarfdump\u002Fllvm-dwarfdump or readelf, verifying debug info with llvm-dwarfdump --verify, answering DWARF standard questions, or writing code that parses DWARF (libdwarf, pyelftools, gimli).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fdwarf-expert-trailofbits__skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dwarf-expert\ndescription: Analyzes DWARF debug information in compiled binaries. Use when inspecting .debug_* sections, DIE trees, or DW_TAG_\u002FDW_AT_ entries with dwarfdump\u002Fllvm-dwarfdump or readelf, verifying debug info with llvm-dwarfdump --verify, answering DWARF standard questions, or writing code that parses DWARF (libdwarf, pyelftools, gimli).\neffort: medium\nallowed-tools: Read Write Edit Bash Grep Glob WebSearch WebFetch\n---\n# DWARF Expert\n\nExpertise for DWARF debug info: parsing and searching it, verifying its\nintegrity, answering questions about the standard, and writing code that\nconsumes it. Out of scope: runtime debugging (use gdb\u002Flldb), reverse\nengineering beyond the DWARF sections (use Ghidra\u002FIDA), and compiler-specific\nDWARF generation bugs.\n\n# Authoritative Sources\n\nWhen precision matters, look standard details up instead of answering from memory:\n\n1. **dwarfstd.org** — the official specification. Web-search specific sections,\n   e.g. \"DWARF5 DW_TAG_subprogram attributes site:dwarfstd.org\".\n2. **LLVM** — `llvm\u002Flib\u002FDebugInfo\u002FDWARF\u002F` is a reliable reference implementation:\n   `DWARFDie.cpp` (DIE and attribute access), `DWARFUnit.cpp` (compilation units),\n   `DWARFDebugLine.cpp` (line tables), `DWARFVerifier.cpp` (validation).\n3. **libdwarf** — the reference C implementation at github.com\u002Fdavea42\u002Flibdwarf-code.\n\n# Parsing and Searching with dwarfdump\n\nPrefer `dwarfdump` over `readelf` for DWARF-specific work. Two implementations\nexist — libdwarf's `dwarfdump` and LLVM's `llvm-dwarfdump` — with different\noptions, and a bare `dwarfdump` command may be either: check `dwarfdump --version`\nfirst. The options below are LLVM's.\n\nOn macOS, linked Mach-O executables do not carry DWARF: it stays in the `.o`\nfiles until `dsymutil` collects it into a `.dSYM` bundle. Point `dwarfdump` at\nthe dSYM (or the object files), not the executable. `pyelftools` is ELF-only —\nfor Mach-O scripted work, stay with the LLVM tools.\n\n- `--all`: dump every DWARF section; `--debug-info`, `--debug-line`, etc. dump one\n- `--show-children [--recurse-depth=\u003Cn>]`: include child DIEs when printing\n  selected entries — parameters, locals, and struct members are children of\n  function and type DIEs\n- `--show-parents [--parent-recurse-depth=\u003Cn>]`: include parent DIEs\n- `--show-form`: print attribute form types, for when encoding details matter\n- `--find=\u003Cname>`: exact-name lookup via the accelerator tables — fast but not\n  exhaustive; fall back to `--name` when it misses\n- `--name=\u003Cpattern> [--ignore-case] [--regex]`: exhaustive DIE-name search\n- `--lookup=\u003Caddress>`: find the DIE covering an address\n- `--verbose`: print low-level encoding detail\n\n## Searching DIEs\n\nEscalate through these strategies as the query grows more complex:\n\n1. **Name or address match**: `--find`, then `--name`; `--lookup` for addresses.\n2. **Attribute or type queries** (e.g. all parameters of type `float *`): dump and\n   filter. `grep -B` pulls in the header line carrying each DIE's offset:\n   `llvm-dwarfdump file | grep -B 5 \"float \\*\" | grep DW_TAG_formal_parameter`,\n   then print each DIE at its offset with `--debug-info=\u003Coffset> --show-children`\n   (`--lookup` takes a program address, not a DIE offset).\n3. **Multi-attribute or structural queries**: when grep pipelines turn brittle,\n   write a Python script using `pyelftools` instead.\n\n# Verifying DWARF Integrity\n\n- `llvm-dwarfdump --verify \u003Cbinary>`: structural checks (unit chains, DIE\n  relationships, address ranges). `--error-display=\u003Cquiet|summary|details|full>`\n  controls detail; `--verify-json=\u003Cpath>` writes a machine-readable error\n  summary; `--quiet` for exit-code-only checks.\n- `llvm-dwarfdump --statistics \u003Cbinary>`: debug-info quality metrics as JSON —\n  compare across compiler versions or optimization levels to catch regressions.\n\nVerify after producing DWARF (compilers, binary rewriters), when a debugger\nmisbehaves on a binary, and when developing DWARF tooling against known-good\nfiles.\n\nWhen a current-generation compiler emitted an old DWARF version, the build\nexplicitly passed `-gdwarf-N` — modern gcc and clang default to v4\u002Fv5, so check\nthe build system rather than assuming a toolchain default. GCC embeds its flags\nin `DW_AT_producer`, so the pin is often readable right there; clang's producer\nstring carries no flags. Old versions remain common in the wild and read the\nsame way apart from surface forms: in v2 output, member offsets appear as\nlocation expressions (`DW_OP_plus_uconst`) and linkage names as\n`DW_AT_MIPS_linkage_name`.\n\n# readelf\n\nFor general ELF structure, or when `dwarfdump` is unavailable:\n\n- `--debug-dump=\u003Csection>`: dump a DWARF section (`info`, `line`, ...)\n- `--dwarf-depth=\u003Cn>` \u002F `--dwarf-start=\u003Cn>`: limit DIE depth \u002F start offset\n\n# Writing Code That Parses DWARF\n\nPrefer an existing library over parsing by hand:\n\n| Library | Language | Notes |\n|---------|----------|-------|\n| `libdwarf` | C\u002FC++ | github.com\u002Fdavea42\u002Flibdwarf-code — low-level; used to implement `dwarfdump` |\n| `pyelftools` | Python | github.com\u002Feliben\u002Fpyelftools — also parses ELF in general |\n| `gimli` | Rust | github.com\u002Fgimli-rs\u002Fgimli — pair with `object` to load container files |\n| `debug\u002Fdwarf` | Go | standard library |\n| `LibObjectFile` | .NET | github.com\u002Fxoofx\u002FLibObjectFile — also handles ELF\u002FPE object files |\n\nDefault to Python with `pyelftools` for one-off scripts unless the task dictates\notherwise.\n\nDWARF-specific pitfalls to handle — and to check for when reviewing DWARF code:\n\n- Attributes are optional: a DIE may omit `DW_AT_name`, `DW_AT_type`, ranges, etc.\n- Attribute indirection: a DIE's attributes may live on the DIE referenced by its\n  `DW_AT_abstract_origin` (inlined instances) or `DW_AT_specification`\n  (out-of-line definitions) — resolve the chain before concluding data is absent.\n- Type chains: qualifiers and modifiers (`DW_TAG_const_type`,\n  `DW_TAG_pointer_type`, ...) wrap the underlying type; walk `DW_AT_type` links to\n  reach the base type.\n","# DWARF Expert\n\nExpertise for DWARF debug info: parsing and searching it, verifying its\nintegrity, answering questions about the standard, and writing code that\nconsumes it. Out of scope: runtime debugging (use gdb\u002Flldb), reverse\nengineering beyond the DWARF sections (use Ghidra\u002FIDA), and compiler-specific\nDWARF generation bugs.\n\n# Authoritative Sources\n\nWhen precision matters, look standard details up instead of answering from memory:\n\n1. **dwarfstd.org** — the official specification. Web-search specific sections,\n   e.g. \"DWARF5 DW_TAG_subprogram attributes site:dwarfstd.org\".\n2. **LLVM** — `llvm\u002Flib\u002FDebugInfo\u002FDWARF\u002F` is a reliable reference implementation:\n   `DWARFDie.cpp` (DIE and attribute access), `DWARFUnit.cpp` (compilation units),\n   `DWARFDebugLine.cpp` (line tables), `DWARFVerifier.cpp` (validation).\n3. **libdwarf** — the reference C implementation at github.com\u002Fdavea42\u002Flibdwarf-code.\n\n# Parsing and Searching with dwarfdump\n\nPrefer `dwarfdump` over `readelf` for DWARF-specific work. Two implementations\nexist — libdwarf's `dwarfdump` and LLVM's `llvm-dwarfdump` — with different\noptions, and a bare `dwarfdump` command may be either: check `dwarfdump --version`\nfirst. The options below are LLVM's.\n\nOn macOS, linked Mach-O executables do not carry DWARF: it stays in the `.o`\nfiles until `dsymutil` collects it into a `.dSYM` bundle. Point `dwarfdump` at\nthe dSYM (or the object files), not the executable. `pyelftools` is ELF-only —\nfor Mach-O scripted work, stay with the LLVM tools.\n\n- `--all`: dump every DWARF section; `--debug-info`, `--debug-line`, etc. dump one\n- `--show-children [--recurse-depth=\u003Cn>]`: include child DIEs when printing\n  selected entries — parameters, locals, and struct members are children of\n  function and type DIEs\n- `--show-parents [--parent-recurse-depth=\u003Cn>]`: include parent DIEs\n- `--show-form`: print attribute form types, for when encoding details matter\n- `--find=\u003Cname>`: exact-name lookup via the accelerator tables — fast but not\n  exhaustive; fall back to `--name` when it misses\n- `--name=\u003Cpattern> [--ignore-case] [--regex]`: exhaustive DIE-name search\n- `--lookup=\u003Caddress>`: find the DIE covering an address\n- `--verbose`: print low-level encoding detail\n\n## Searching DIEs\n\nEscalate through these strategies as the query grows more complex:\n\n1. **Name or address match**: `--find`, then `--name`; `--lookup` for addresses.\n2. **Attribute or type queries** (e.g. all parameters of type `float *`): dump and\n   filter. `grep -B` pulls in the header line carrying each DIE's offset:\n   `llvm-dwarfdump file | grep -B 5 \"float \\*\" | grep DW_TAG_formal_parameter`,\n   then print each DIE at its offset with `--debug-info=\u003Coffset> --show-children`\n   (`--lookup` takes a program address, not a DIE offset).\n3. **Multi-attribute or structural queries**: when grep pipelines turn brittle,\n   write a Python script using `pyelftools` instead.\n\n# Verifying DWARF Integrity\n\n- `llvm-dwarfdump --verify \u003Cbinary>`: structural checks (unit chains, DIE\n  relationships, address ranges). `--error-display=\u003Cquiet|summary|details|full>`\n  controls detail; `--verify-json=\u003Cpath>` writes a machine-readable error\n  summary; `--quiet` for exit-code-only checks.\n- `llvm-dwarfdump --statistics \u003Cbinary>`: debug-info quality metrics as JSON —\n  compare across compiler versions or optimization levels to catch regressions.\n\nVerify after producing DWARF (compilers, binary rewriters), when a debugger\nmisbehaves on a binary, and when developing DWARF tooling against known-good\nfiles.\n\nWhen a current-generation compiler emitted an old DWARF version, the build\nexplicitly passed `-gdwarf-N` — modern gcc and clang default to v4\u002Fv5, so check\nthe build system rather than assuming a toolchain default. GCC embeds its flags\nin `DW_AT_producer`, so the pin is often readable right there; clang's producer\nstring carries no flags. Old versions remain common in the wild and read the\nsame way apart from surface forms: in v2 output, member offsets appear as\nlocation expressions (`DW_OP_plus_uconst`) and linkage names as\n`DW_AT_MIPS_linkage_name`.\n\n# readelf\n\nFor general ELF structure, or when `dwarfdump` is unavailable:\n\n- `--debug-dump=\u003Csection>`: dump a DWARF section (`info`, `line`, ...)\n- `--dwarf-depth=\u003Cn>` \u002F `--dwarf-start=\u003Cn>`: limit DIE depth \u002F start offset\n\n# Writing Code That Parses DWARF\n\nPrefer an existing library over parsing by hand:\n\n| Library | Language | Notes |\n|---------|----------|-------|\n| `libdwarf` | C\u002FC++ | github.com\u002Fdavea42\u002Flibdwarf-code — low-level; used to implement `dwarfdump` |\n| `pyelftools` | Python | github.com\u002Feliben\u002Fpyelftools — also parses ELF in general |\n| `gimli` | Rust | github.com\u002Fgimli-rs\u002Fgimli — pair with `object` to load container files |\n| `debug\u002Fdwarf` | Go | standard library |\n| `LibObjectFile` | .NET | github.com\u002Fxoofx\u002FLibObjectFile — also handles ELF\u002FPE object files |\n\nDefault to Python with `pyelftools` for one-off scripts unless the task dictates\notherwise.\n\nDWARF-specific pitfalls to handle — and to check for when reviewing DWARF code:\n\n- Attributes are optional: a DIE may omit `DW_AT_name`, `DW_AT_type`, ranges, etc.\n- Attribute indirection: a DIE's attributes may live on the DIE referenced by its\n  `DW_AT_abstract_origin` (inlined instances) or `DW_AT_specification`\n  (out-of-line definitions) — resolve the chain before concluding data is absent.\n- Type chains: qualifiers and modifiers (`DW_TAG_const_type`,\n  `DW_TAG_pointer_type`, ...) wrap the underlying type; walk `DW_AT_type` links to\n  reach the base type.\n",{"name":5,"effort":24,"description":7,"allowed-tools":25},"medium","Read Write Edit Bash Grep Glob WebSearch WebFetch","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","03-逆向工程\u002Fdwarf-expert-trailofbits__skills",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill dwarf-expert",{"tool":40,"command":41},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill dwarf-expert",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill dwarf-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fdwarf-expert-trailofbits__skills\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",232,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fdwarf-expert-trailofbits__skills\u002Fagents\u002Fopenai.yaml",[55,63,68,75,82,89],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":64,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":62},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":62},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":62},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":62},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":62},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]