Individual skill
evidence-capture
Enforce reproduction bug evidence in either image or video formats to be ready to submit
skills/hunter-utils/evidence-capture/SKILL.md
Source commit 0c1bc93fd5124e7a862d61c1b434f32ba8790e3a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 153
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-security Repository topic
- ai-skills Repository topic
- security-skills Repository topic
- dynamic-workflow Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
Evidence capture skills assists in the image and/or video evidence that go to prove reproducible bugs.
# Must-have rules
- Reproductions usually are made of steps. each step needs to be thought of what we want to present it could be insight or outcome that is tailored to the sentence in the reproduction example
- Captures are only visuals, added text must be minimal if even at all
- OCR-adding markings of the exact point-in-image that the evidence speaks to, for example, if we are showing BurpSuite raw Request/Response pair - a marker signaling the lines exactly on where to look is crucial (other than staring at a wall of info) - the marking should fit the evidence
- Image type captures must go with a 1 line title describing the step (e.g. Attached image demonstrates browser view of when the user interacts with x)
- Capture each thing from the tool that owns it - HTTP from Burp (Repeater or Proxy), never a raw request or response pasted into a browser tab; app behaviour from the browser; code from the editor or a rendered snippet, not a photo of a terminal; a command from the terminal; on-chain state from the explorer or a Foundry trace. The owning tool carries the detail a makeshift capture loses (headers, timing, a diff), and showing it the wrong way reads as amateur. If the right tool is open, use it.
- Correlate surfaces across scenes - To show Burp, the browser, and a code snippet together, chain one capture per scene in order (wire scene, then the browser step, then the code). Each stays a real, hashable capture.
- link to the live source whether its proof in code, in burp, in browser in a specific moment from the user story etc
- Don't fabricate data only use real data and real captures no workarounds find the best way to get proper evidence
- When done, critique the result with actual OCR or visual analysis and wonder if you missed any guidelines in this skill checklist or you did something off (e.g. if you marked a part in the image too much to the right of where the text actually is)
