Evidence-driven authorized penetration and attack-surface validation for local, owned, or explicitly authorized systems, with OWASP, Nuclei, and ZAP method adapters.
Pro scans all 11 files and shows the line behind each finding
Scanned 9/24/2026
npx -y skills add alicewe1/alice_skill --skill eni-pentest-workflow --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Eni Pentest Workflow?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/alicewe1-eni-pentest-workflow)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: eni-pentest-workflow
description: "Evidence-driven authorized penetration and attack-surface validation for local, owned, or explicitly authorized systems, with OWASP, Nuclei, and ZAP method adapters."
x-alice-class: pentest
---
# Pentest Workflow 2.1
Persist the operator scope declaration and target inventory. Start in `eni-solo-direct-v4`: take the fastest high-signal inventory, fingerprint, trust-map, and broad template-driven validation route at the highest intensity recorded in the task ledger, then move immediately into deep manual reproduction of the strongest hypotheses. Combine OWASP WSTG/ASVS coverage, Nuclei-style breadth, and proxy/browser depth. Treat scanner output as a hypothesis until reproduced. Continue through evidence, impact, root cause, remediation, re-test, and delivery; use the smallest connected detail pack for each confirmed class.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!