burpsuite-project-parser

Overview of burpsuite-project-parser skill

What burpsuite-project-parser does

burpsuite-project-parser is a command-line skill for searching and extracting data from Burp Suite project files (.burp) through Burp Suite Professional plus the burpsuite-project-file-parser extension. It is most useful when you already have a captured project and need to pull out specific evidence fast: audit findings, proxy history, site map entries, or HTTP content matched by regex.

Who should use it

Use the burpsuite-project-parser skill if you work on a Security Audit, incident review, red-team note taking, or Burp project triage and want repeatable extraction instead of manual clicking. It is a strong fit when the question is “show me the matching traffic or finding across this project,” not “help me test a live app from scratch.”

What makes it different

The main value of the burpsuite-project-parser skill is that it wraps a Burp-dependent workflow in a scriptable path. That reduces guesswork around where to start, which flags to use, and how to target a project file. It also makes the skill better for evidence retrieval than a generic prompt because it is anchored to Burp project data and the extension’s supported filters.

How to Use burpsuite-project-parser skill

Install and environment setup

Install with npx skills add trailofbits/skills --skill burpsuite-project-parser. The skill expects Burp Suite Professional and the burpsuite-project-file-parser extension to be installed; it does not parse .burp files directly. If your Burp install lives in a nonstandard path, set BURP_JAVA and BURP_JAR before running the script.

Call it with the right input

For best burpsuite-project-parser usage, start with a concrete target and extraction goal: the .burp file path, the artifact type you want, and any search pattern. Good inputs look like: “Extract response bodies containing csrf from case-2024-07.burp” or “Dump proxyHistory for requests to login.example.com and keep only request headers.” Weak inputs like “analyze this project” force the skill to guess your intent.

Suggested workflow and first files to read

Start with SKILL.md, then inspect scripts/burp-search.sh to see the supported flags and platform defaults. The script help output is the fastest way to understand the burpsuite-project-parser guide in practice: auditItems, proxyHistory, siteMap, responseHeader='regex', and responseBody='regex'. Read the sub-component filter section before running large dumps, because it is the difference between a focused result and a noisy export.

Practical tips that improve output quality

Use the narrowest filter that answers the question first, then expand only if needed. For Security Audit work, ask for one finding class, one host, or one regex family at a time so the result set stays reviewable. If you need reproducibility, include the exact .burp file name, the Burp version, and the desired output slice in the prompt so the skill can map directly to the supported command path.

burpsuite-project-parser skill FAQ

Does burpsuite-project-parser require Burp Suite Professional?

Yes. The burpsuite-project-parser skill depends on Burp Suite Professional plus the burpsuite-project-file-parser extension. If you do not have both, the install will not be useful because the skill delegates parsing to Burp rather than reading .burp files natively.

Is this better than a normal prompt?

For this workflow, yes. A plain prompt can describe what to search, but burpsuite-project-parser adds the practical command structure, supported artifact types, and filter names needed to actually run the extraction consistently. That matters when you want burpsuite-project-parser for Security Audit evidence collection rather than a one-off manual search.

Is it beginner-friendly?

It is beginner-friendly if you already know what a Burp project file is and can identify the evidence you want. It is less friendly if you need help understanding Burp terminology itself. Beginners get the best results by starting with proxyHistory or siteMap before attempting more specific regex searches.

How to Improve burpsuite-project-parser skill

Give it a tighter target

The biggest improvement comes from narrowing scope. Instead of asking for all traffic, specify one host, one time window if known, one finding category, or one regex pattern. The more the burpsuite-project-parser skill can anchor on a concrete artifact, the less likely it is to return an oversized dump you cannot review efficiently.

Match the flag to the job

Choose the output type that matches the task: auditItems for findings, proxyHistory for traffic reconstruction, siteMap for endpoint inventory, and response searches for content hunting. If you are doing burpsuite-project-parser usage for triage, do not start with broad body searches unless you already know the string family you are chasing.

Iterate from summary to evidence

A strong burpsuite-project-parser guide workflow is: get a focused extract, inspect the matching rows, then rerun with a tighter sub-component filter if the output is still noisy. If the first pass is empty, widen the regex slightly, confirm the project file path, and verify Burp plus the extension are available before changing the search strategy.