pentest-evidence-structuring-report-synthesis
Evidence Structuring & Report Synthesis
Activation Triggers (Positive)
write reportconsolidate findingsseverityremediationexecutive summaryevidence tablefinal deliverable
Exclusion Triggers (Negative)
run exploitperform reconfuzz inputslive validation
Output Schema
- Confirmed findings table:
id,title,severity,confidence,impact - Evidence map:
finding idto reproducible proof artifacts - Remediation plan: prioritized fixes with verification guidance
Instructions
- Separate confirmed findings from hypotheses and informational observations.
- Deduplicate by root cause and attacker capability, not by endpoint count alone.
- Assign severity from demonstrated impact and exploitability evidence.
- Keep technical evidence concise, reproducible, and traceable.
- Produce both technical and executive views from the same canonical evidence.
- Mark open questions and explicitly state what remains unverified.
Should Do
- Preserve factual precision and reproducibility in every finding.
- Keep structure stable for machine parsing and downstream tracking.
- Tie remediation to the broken control and observed exploit path.
Should Not Do
- Do not inflate severity without demonstrated impact.
- Do not merge unrelated root causes into a single finding.
- Do not hide uncertainty; mark assumptions explicitly.
More from crtvrffnrt/skills
pentest-xss
Security assessment skill for Cross-Site Scripting (XSS) vulnerabilities. Use when investigating input sanitization, reflected, stored, DOM, or blind XSS. Focuses on discovery, exploitation, and payload optimization. Do not use for generic network recon or non-web injection types.
36pentest-exploit-execution-payload-control
Security assessment skill for deterministic exploit execution from validated primitives. Use when prompts include exploit implementation, payload hardening, chaining confirmed weaknesses, post-exploitation proof, or controlled impact demonstration. Do not use for early-stage reconnaissance, speculative hypothesis generation, or report-only requests.
30pentest-recon-surface-analysis
Security assessment skill for reconnaissance, endpoint/service enumeration, and attack-surface mapping. Use when prompts include recon, enumerate, map endpoints, discover assets, inventory interfaces, fingerprint technologies, or identify control-plane surfaces. Do not use when the request is exploit development, payload execution, or final report writing only.
29pentest-business-logic-abuse
Security assessment skill for business workflow abuse, state-machine manipulation, and control-plane logic flaws. Use when prompts include workflow bypass, race condition, replay, quota abuse, order-of-operations flaws, delegated execution abuse, or unauthorized state transitions. Do not use for pure input injection fuzzing, broad recon, or standalone report formatting tasks.
27pentest-gemini-az
Use when users need an Azure, Microsoft 365, or Entra ID companion that reads, lists, changes, and manages resources using the current Azure CLI session, with `az rest` as the default execution path.
26pentest-outbound-interaction-oob-detection
Security assessment skill for outbound interaction and out-of-band (OOB) validation. Use when prompts include SSRF callback confirmation, blind XSS beacons, webhook abuse, XXE/OOB behavior, DNS/HTTP callback correlation, or asynchronous server-side interaction proof. Do not use when vulnerabilities are fully in-band and require no external callback correlation.
25