Pentest Evidence Structuring Report Synthesis
- 41 installs
- 2 repo stars
- Updated July 8, 2026
- crtvrffnrt/skills
Structure evidence, deduplicate findings, rank severity, and produce decision-ready security reports with executive summaries and technical appendices.
About
A security-assessment skill that structures evidence, deduplicates findings, ranks severity, and synthesizes decision-ready reports with executive summaries and technical appendices. A developer or pentester uses it to consolidate findings into a final deliverable rather than running exploits or recon.
- Deduplicates findings and ranks severity with remediation guidance
- Produces executive summary plus technical appendix
Pentest Evidence Structuring Report Synthesis by the numbers
- 41 all-time installs (skills.sh)
- Ranked #1,405 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/crtvrffnrt/skills --skill pentest-evidence-structuring-report-synthesisAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 41 |
|---|---|
| repo stars | ★ 2 |
| Last updated | July 8, 2026 |
| Repository | crtvrffnrt/skills ↗ |
What it does
Structure evidence, deduplicate findings, rank severity, and produce decision-ready security reports with executive summaries and technical appendices.
Files
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
1. Separate confirmed findings from hypotheses and informational observations. 2. Deduplicate by root cause and attacker capability, not by endpoint count alone. 3. Assign severity from demonstrated impact and exploitability evidence. 4. Keep technical evidence concise, reproducible, and traceable. 5. Produce both technical and executive views from the same canonical evidence. 6. 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.
Related skills
Entra App RegistrationCorrectly register an application in Microsoft Entra ID, configure OAuth 2.0 flows, request the right API permissions, and generate working MSAL authentication snippets484k1.3kAzure ComplianceRun automated Azure compliance scans, security posture checks, and Key Vault expiration audits before deploying.484k1.3k
Openclaw Secure Linux CloudDeploy and harden an OpenClaw agent instance on a Linux cloud server following battle-tested security defaults.270k72
Better Auth Best PracticesCorrectly configure Better Auth for secure authentication with database adapters, sessions, OAuth, email/password, and plugins in TypeScript projects.80.9k206
Firebase Security Rules AuditorAutomatically audit Firebase Firestore security rules for bypass vulnerabilities and logic gaps before deploying.80.4k397
Audit WebsiteRun comprehensive audits that surface SEO, performance, security, technical, and content issues with LLM-optimized reports and health scores.65.6k85