mirror of
https://github.com/trailofbits/skills
synced 2026-06-21 14:12:00 +00:00
d5fe2e6a78
* feat(codex): add skill UI metadata * Use official Trail of Bits logo * fix: resolve code review findings for PR #175 Codex silently drops the icons as authored: its loader (codex-rs/core-skills resolve_asset_path) requires icon paths containing '..' to resolve under <plugin_root>/assets/, and the repo-root .codex/assets location fails that containment check. Verified empirically via codex app-server plugin/read: every iconSmall/iconLarge came back null; only brand_color applied. P1 fixed: - Vendor trail-of-bits-mark.svg into plugins/<name>/assets/ for all 38 plugins with skills and point every openai.yaml at ../../assets/trail-of-bits-mark.svg (the supported plugin-level shared asset pattern). Icons now resolve for marketplace installs too, since nothing escapes the plugin root. - Drop the .codex/ additions: .codex/skills/gh-cli/agents/ openai.yaml resolved nowhere (.codex/skills is not a Codex discovery root) and PR #173 removes the whole .codex/ tree P2 fixed: - Patch-bump all 38 touched plugins in plugin.json and marketplace.json so installed clients pick up the metadata Verified: - Static check replicating Codex's resolution algorithm: all 73 yaml files resolve under their plugin assets/ and exist - Live codex app-server probe: 71/72 loadable skills report resolved iconSmall/iconLarge and brand_color #D83A34 (claude-in-chrome-troubleshooting fails to load on main due to a pre-existing 64-char qualified-name limit, fixed by #173's rename; zeroize-audit's manifest mcpServers object is likewise a pre-existing Codex incompatibility fixed by #173) - validate_codex_skills.py, validate_plugin_metadata.py, prek all pass Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(codex): use skill-local icon assets --------- Co-authored-by: Dan Guido <dan@trailofbits.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
DWARF Expert
Interact with and analyze DWARF debug files, understand the DWARF debug format/standard, and write code that parses DWARF data.
Author: Evan Hellman
When to Use
Use this skill when you need to:
- Understand or parse DWARF debug information from compiled binaries
- Answer questions about the DWARF standard (v3, v4, v5)
- Write or review code that interacts with DWARF data
- Use
dwarfdumporreadelfto extract debug information - Verify DWARF data integrity using
llvm-dwarfdump --verify - Work with DWARF parsing libraries (libdwarf, pyelftools, gimli, etc.)
What It Does
This skill provides expertise on:
- DWARF standards (v3-v5) via web search and authoritative source references
- Parsing DWARF files using
dwarfdumpandreadelfcommands - Verification workflows using
llvm-dwarfdump --verifyand--statistics - Library recommendations for DWARF parsing in C/C++, Python, Rust, Go, and .NET
- DIE (Debug Information Entry) analysis and searching
- Understanding DWARF sections, attributes, and forms
Authoritative Sources
This skill uses the following authoritative sources for DWARF standard information:
- dwarfstd.org: Official DWARF specification (via web search)
- LLVM source:
llvm/lib/DebugInfo/DWARF/for reference implementations - libdwarf source: github.com/davea42/libdwarf-code for C implementations
Installation
/plugin install trailofbits/skills/plugins/dwarf-expert