security-documentation

Generate LaTeX security assessment reports and compile them to PDF.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill security-documentation-yogiex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-documentation
Source: https://github.com/yogiex/opencode-cyber-security-skills/tree/main/skills/security-documentation
Command: npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill security-documentation-yogiex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing formal penetration testing reports is time-consuming and inconsistent. This Skill turns raw security findings into a structured LaTeX report following OWASP WSTG and PTES conventions, compiled to PDF for stakeholders. ## Core Features & Use Cases - Standardized Report Structure: Produces the full report flow — executive summary, findings by severity (CRITICAL/HIGH/MEDIUM/LOW/INFO), technical summary, detailed findings, conclusion, and appendices. - Reproducible PoCs: Every finding includes copy-paste-ready curl commands with JSON response evidence, plus CVSS v3.1 scores and CWE mappings. - LaTeX Conventions Built In: Severity badges via colorbox, longtable layouts for lower-severity findings, and 3-pass pdflatex compilation for the table of contents. - Use Case: After a read-only web application assessment, feed your findings to the Skill and receive a stakeholder-ready PDF report with a non-technical narrative summary for management and technical detail for engineers. ## Quick Start Ask the agent to generate a security testing report in LaTeX from your collected findings and compile it to PDF following the laporan template.

Frequently Asked Questions about security-documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a penetration testing report in LaTeX?▼

Structure the report as executive summary, findings table by severity, technical summary, detailed findings with PoCs, conclusion, and appendices. Use packages like longtable, booktabs, and xcolor, then compile with three pdflatex passes for the table of contents.

How to document proof of concept for security findings?▼

Write PoCs as copy-paste-ready curl commands rather than raw HTTP requests, and include the JSON response as evidence. If a finding cannot be reproduced in read-only mode, state that explicitly in the report.

What CVSS and CWE information should a security report include?▼

HIGH and MEDIUM findings should include a CVSS v3.1 base score plus a CWE identifier such as CWE-862 or CWE-639. LOW and INFO findings only need a severity label without full scoring.

Can this skill generate reports in DOCX or HTML format?▼

No, the skill only produces LaTeX source compiled to PDF via pdflatex. It is also not suited for active exploitation phases involving POST, PUT, or DELETE requests, as it targets read-only assessment documentation.

Why does my LaTeX report table of contents not appear?▼

The table of contents requires multiple compilation passes to resolve references. Run pdflatex three times on the document so section numbering and ToC entries are fully populated.