Menu

Individual skill

reporting-evidence-review

0upvotes

Pre-handoff audit of an engagement package — scope confirmed, every finding traceable to reproducible evidence, activity-log leads closed with rationale, artifact hashes intact. Load before writing the final report or handing a case to a teammate/client, on "is this ready to report", "review my engagement notes", QA of findings/ + notes.md. Signals: findings folder full, handoff, report QA, evidence chain, chain of custody.

skills/reporting/reporting-evidence-review/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 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)
27
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Pre-handoff evidence review

## When it applies
The active work is done — findings drafted in `findings/`, `notes.md` complete, activity log
populated — and you're about to write the report (`reporting-pentest-report`,
`reporting-bug-bounty-writeup`) or hand the case to a teammate, client, or incident
stakeholder. This is a **read-only** audit of `engagements/<target>/`: it never touches the
target and never adds new testing. If a check fails, go back to the owning skill — don't patch
the report to hide the gap.

## Why it works
Reports get killed in review for the same few reasons: a finding with no reproducible proof, a
lead silently dropped, scope ambiguity, or an artifact that no longer matches its hash. A
structured pass over the package catches these while they're still cheap to fix and produces a
Back to top