Skip to content
TrustedSkillsbeta
Back to all skills

Dwarf Debug Format

Checked
mohitmishra786·vlatest·testing·MIT

Helps with debugging, formatting as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mohitmishra786/low-level-dev-skills --skill dwarf-debug-format -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

mohitmishra786

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mohitmishra786/low-level-dev-skills at bdc58472fa.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
bdc58472fa
Manifest
skills/debuggers/dwarf-debug-format/SKILL.md
Scanned
1 file, 199 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The dwarf-debug-format skill allows AI agents to parse and interpret DWARF debug information. This enables the agent to extract detailed debugging data from compiled binaries, including variable values, source code locations, and function arguments. It facilitates deeper analysis of program behavior during runtime or post-mortem debugging scenarios.

When to use it

  • Reverse Engineering: Analyze binary executables to understand their functionality without access to source code.
  • Bug Hunting: Extract precise information about the state of a program at the point of failure, aiding in root cause analysis.
  • Performance Profiling: Identify performance bottlenecks by examining function call stacks and variable usage patterns.
  • Security Auditing: Investigate potential vulnerabilities within compiled code by inspecting debug symbols.

Key capabilities

  • Parsing DWARF information from ELF binaries.
  • Extracting source location (file and line number) for variables and functions.
  • Retrieving variable values at specific program addresses.
  • Decoding function arguments from the debugging data.

Example prompts

  • "Analyze this binary and tell me the value of 'user_input' at address 0x401234."
  • "Show me the source code location where variable 'count' is defined in this executable."
  • "What were the arguments passed to function 'process_data' when it was called?"

Tips & gotchas

  • The binary must contain DWARF debug information for this skill to be effective. Not all binaries are compiled with debugging symbols enabled.
  • Understanding of ELF file format and DWARF structure will improve interpretation of the results.