[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CH8CF74H37Z7DPQ4K8ESMP":3,"skill-same:01M7CH8CF74H37Z7DPQ4K8ESMP":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CH8CF74H37Z7DPQ4K8ESMP","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).","bongkage\u002Ftrailofbits-skills","bongkage","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F101378796?v=4","01M7CH419QTJ16DNJ33P0WCWBE","01M7CH41A9NWK8D2JBRK9F0M2C",1,"CC-BY-SA-4.0","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdwarf-expert\u002Fskills\u002Fdwarf-expert\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":23,"description":7,"allowed-tools":24},"medium","Read Write Edit Bash Grep Glob WebSearch WebFetch","main","321ccfe628eca0d314b0ee4eaffcdd8a05639aaf","plugins\u002Fdwarf-expert\u002Fskills\u002Fdwarf-expert",0,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills","https:\u002F\u002Fgithub.com\u002Fbongkage","2026-11-06 12:15:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add bongkage\u002Ftrailofbits-skills --skill dwarf-expert",{"tool":38,"command":39},"bunx","bunx skills add bongkage\u002Ftrailofbits-skills --skill dwarf-expert",{"tool":41,"command":42},"pnpm","pnpm dlx skills add bongkage\u002Ftrailofbits-skills --skill dwarf-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdwarf-expert\u002Fskills\u002Fdwarf-expert\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",128,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdwarf-expert\u002Fskills\u002Fdwarf-expert\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Ftrail-of-bits-mark.svg","ASSET","资产文件",3084,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdwarf-expert\u002Fskills\u002Fdwarf-expert\u002Fassets\u002Ftrail-of-bits-mark.svg",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7CHJAESZRWKJXFQG55BMNAA","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fzeroize-audit\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7CHJ543G42A9GQC3PJE4F4V","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fyara-authoring\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7CHHYVFS1AKDTH3YDS1Y4K4","writing-lean-proofs","Writes and reviews structured Lean 4 proofs and designs Lean libraries following Mathlib conventions. Use when proving theorems in Lean, formalizing mathematics or specifications in Lean 4, defining new types or definitions in a Lean library, reviewing Lean proofs for readability and maintainability, refactoring long tactic proofs into lemmas, filling in sorry placeholders in a Lean development, setting up CI or linters for a Lean project, diagnosing slow proofs or maxHeartbeats timeouts, or writing custom tactics, macros, or linters.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fwriting-lean-proofs\u002Fskills\u002Fwriting-lean-proofs\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7CHHQXA39M4965MV2RMM5YS","vulnerability-triage-brocards","This skill should be used when the user asks to \"triage a vulnerability report\", \"assess a CVE\", \"evaluate a bug bounty submission\", \"decide if a finding is valid\", \"review a security finding\", \"dismiss a vulnerability\", \"should we fix this CVE\", \"prioritize a vulnerability report\", or needs to determine whether an incoming vulnerability report warrants investigation. Applies 7 brocards (rules of thumb) to systematically accept, dismiss, or request more information on vulnerability reports, or needs to filter raw findings from agentic vulnerability discovery pipelines before human review.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fvulnerability-triage-brocards\u002Fskills\u002Fvulnerability-triage-brocards\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7CHHJVQC2ZG2M310GXT0T42","variant-analysis","Hunts for the other instances of a bug already found — the variants of one root cause across a codebase. Use immediately after a vulnerability, logic bug, or bad pattern turns up in a specific file and the question becomes where else it occurs, including the bare conversational form (\"are there others like this?\", \"is this the same bug?\"). Also for generalizing one known instance into a CodeQL or Semgrep query for its whole pattern family, and for triaging a set of look-alike candidates against a known root cause. Not for initial discovery with no bug in hand.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fvariant-analysis\u002Fskills\u002Fvariant-analysis\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7CHHC1GM5GH585ZWGP7D03P","vector-forge","Mutation-driven test vector generation. Finds implementations of a cryptographic algorithm or protocol, runs mutation testing to identify escaped mutants, then generates new test vectors that deliberately exercise the uncovered code paths. Compares before\u002Fafter mutation kill rates to prove vector effectiveness. Use when generating cryptographic test vectors, measuring Wycheproof coverage gaps, finding escaped mutants via mutation testing, creating cross-implementation test suites, or improving test vector coverage for crypto primitives.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftrailmark\u002Fskills\u002Fvector-forge\u002FSKILL.md",[],[]]