Menú
Generate PDF security report from findings.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Complete reference for pentest-cli. Load this skill when you need to call the CLI with correct syntax, flags, and output shapes.
Business logic and authorization testing. IDOR, privilege escalation, workflow bypass, payment manipulation.
Show all available pentest-cli commands and how to use them.
Advanced attack testing. Request smuggling, race conditions, cache poisoning, subdomain takeover.
Authentication and session security testing. JWT, OAuth, sessions, brute force.
Cloud and infrastructure testing. Storage misconfig, WAF detection, email security.
| name | pentest-report |
| description | Generate PDF security report from findings. |
| user-invocable | true |
| allowed-tools | ["Bash","Agent","Read"] |
Generate a professional PDF security report from previously collected pentest findings.
An optional findings directory path can be provided via $ARGUMENTS. Defaults to ./findings/ if not specified.
Determine findings directory:
$ARGUMENTS contains a path, use that../findings/.Verify findings exist:
Check that the findings directory contains result files. If empty, inform the user they need to run scans first (suggest /pentest-full or individual scan skills).
Delegate to report-agent using the Agent tool. The agent must run:
pentest report ./findings/
Read the command output to determine the report file location.
Present the report location to the user:
./findings/ directory.