How do I install the Valgrind Summarizer skill?

Run npx skillmds@latest add majiayu000/valgrind-summarizer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Valgrind Summarizer safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Valgrind Summarizer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Valgrind Summarizer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Valgrind Summarizer?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Valgrind Summarizer by majiayu000 — Agent Skill

Name: Valgrind Summarizer
Rating: 4.2 (5 reviews)
Author: majiayu000

Valgrind Summarizer

Summarize Valgrind Memcheck reports into concise Markdown. Use when the user uploads or references a Valgrind log file (.txt, .log, .valgrind) and wants a summary, analysis, or overview of memory leaks and errors. Triggers on mentions of "valgrind", "memcheck", "leak check", "memory leak report", or when the uploaded file contains Valgrind Memcheck output (identifiable by "==PID==" prefixed lines, "HEAP SUMMARY", "LEAK SUMMARY").

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Valgrind Report Summarizer

Produce a minimal-token Markdown summary of Valgrind Memcheck reports by running the bundled parser script.

Workflow

Identify the valgrind log file (uploaded or at a given path).

If no log file exists yet and the user wants to run Valgrind, build with debug symbols first:

cd python && MSCOMPRESS_DEBUG=1 uv sync --all-extras --reinstall

Then run Valgrind:

cd python && valgrind --tool=memcheck --leak-check=full --log-file=leak-check.txt $(uv run which python) -m pytest

Run the parser:

python3 /path/to/this/skill/scripts/parse_valgrind.py <input_file> <output.md>

Deliver the resulting .md file to the user.

What the Script Produces

Heap Overview — exit usage, total allocated, alloc/free delta
Leak Summary — table with definitely/indirectly/possibly lost, still reachable, suppressed (with severity icons)
Top 15 Leak Sources — grouped & deduplicated by call stack, sorted by bytes, showing only user-code frames (runtime/valgrind internals stripped)

Notes

The parser strips ==PID== / --PID-- prefixes automatically.
Stack frames from valgrind preload, libpython, CPython eval loop, pthread, and clone are filtered out to surface only the user's own code.
Duplicate stacks (same top-4 frames) are merged with a ×N count.
Byte values are human-readable (KB/MB/GB).
If the user wants deeper analysis or remediation advice beyond the summary, read the generated markdown and provide commentary.

---name: valgrind-summarizerdescription: Summarize Valgrind Memcheck reports into concise Markdown. Use when the user uploads or references a Valgrind log file (.txt, .log, .valgrind) and wants a summary, analysis, or overview of memory leaks and errors. Triggers on mentions of "valgrind", "memcheck", "leak check", "memory leak report", or when the uploaded file contains Valgrind Memcheck output (identifiable by "==PID==" prefixed lines, "HEAP SUMMARY", "LEAK SUMMARY").--- # Valgrind Report Summarizer Produce a minimal-token Markdown summary of Valgrind Memcheck reports by running the bundled parser script. ## Workflow 1. Identify the valgrind log file (uploaded or at a given path). - If no log file exists yet and the user wants to run Valgrind, build with debug symbols first: ```bash cd python && MSCOMPRESS_DEBUG=1 uv sync --all-extras --reinstall ``` Then run Valgrind: ```bash cd python && valgrind --tool=memcheck --leak-check=full --log-file=leak-check.txt $(uv run which python) -m pytest ``` 2. Run the parser: ```bash python3 /path/to/this/skill/scripts/parse_valgrind.py <input_file> <output.md> ``` 3. Deliver the resulting `.md` file to the user. ## What the Script Produces - **Heap Overview** — exit usage, total allocated, alloc/free delta - **Leak Summary** — table with definitely/indirectly/possibly lost, still reachable, suppressed (with severity icons) - **Top 15 Leak Sources** — grouped & deduplicated by call stack, sorted by bytes, showing only user-code frames (runtime/valgrind internals stripped) ## Notes - The parser strips `==PID==` / `--PID--` prefixes automatically. - Stack frames from valgrind preload, libpython, CPython eval loop, pthread, and clone are filtered out to surface only the user's own code. - Duplicate stacks (same top-4 frames) are merged with a `×N` count. - Byte values are human-readable (KB/MB/GB). - If the user wants deeper analysis or remediation advice beyond the summary, read the generated markdown and provide commentary.

Frequently asked questions