reporting-evidence-review
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 enga
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reporting-evidence-reviewWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package2b0aab4d…63a60100
2b0aab4d147a…a00f63a601001 file · 2.3 KBScanMedium3 findings
- injection.no_confirmationSKILL.md:31
- injection.no_confirmationSKILL.md:56
- Links to outside domains
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reporting/reporting-evidence-review@ee0e0c5
On this page
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 handoff another human can defend without you in the room.
Method
Work the package top to bottom; every failure is a blocker until fixed or explicitly waived with a written reason.
1. Scope & readiness
-
scope.txtexists and every tested asset traces back to it (or toroe.mdfor bounty). - Anything out of scope that was touched is disclosed, not buried.
- The objective from
plan.mdis answered, or the gap is stated.
2. Evidence → finding traceability
- Every
findings/*.mdhas copy-pasteable repro steps and minimal proof of impact. - Every finding cites its exact evidence (request, command + output, screenshot, artifact path) — and that evidence exists in the package.
- No orphaned evidence: each capture/log/screenshot is referenced by a finding or
notes.md. - Severity is defensible (
reporting-cvss-scoring) and the finding survived false-positive checks (reporting-triage-validation).
3. Lead & timeline coverage
- Every lead in
.secskills/activity.jsonl/plan.mdhas a terminal status —confirmed,failed(with variation-matrix rationale),blocked, orskipped(with why). No lead silently evaporates. -
notes.mdtimestamps let a reviewer reconstruct the order of operations; clock and timezone noted. - Not-attempted surface is listed — what you didn't test and why (time, RoE, risk).
4. Fixity (where artifacts matter — forensics, malware, captured data)
- SHA-256 recorded for each acquired artifact at intake; re-hash now and compare. A mismatch is a hard failure — quarantine the copy, re-acquire or declare it.
- Chain of custody: who acquired what, when, with which command.
5. Handoff
- Save the review result (passes, failures, waivers) into the package — e.g.
findings/00-review.md— so it ships with the report. - Then run the report skill. A review result is not legal advice and doesn't replace your organization's evidence-handling procedures.
Gotchas
- "It worked yesterday" is not evidence — capture it in the package or it doesn't exist.
- One-time observations (a state you could only see once) are allowed only with an explicit note of the limitation; don't dress them up as reproducible.
- Sanitize before handoff: third-party data, credentials, and internal paths in evidence need redaction with the reason noted.
- Don't fix gaps by editing findings to say less — go back and test, or mark the lead
blockedhonestly. - Skipped hash verification needs a written reason ("no acquired artifacts — web-only engagement"), not silence.
Verify success
A reviewer who was never on the engagement can start from scope.txt, follow any finding to
its evidence and reproduce it, see every lead's disposition, and confirm artifact integrity —
with the review record saved alongside the report.
References
NIST SP 800-86 (forensic techniques in incident response); SWGDE best practices for forensic
acquisition and evidence archiving; reporting-triage-validation.
Portions adapted from reverse-skill by zhaoxuya520, MIT License.
Files in this version
- SKILL.md4.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumPrompt injection · injection.no_confirmationSKILL.md:31
- MediumPrompt injection · injection.no_confirmationSKILL.md:56
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 2b0aab4d | Signed | – |
More from NoorQureshi
All from this publisherMore in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login