perseus:report

Synthesize Perseus Scan, Audit, Exploit, and Specialist findings into a formal executive security report.

66|14|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kaivyy/perseus --skill perseus-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perseus:report
Source: https://github.com/kaivyy/perseus/tree/main/skills/perseus/report
Command: npx skills add https://github.com/kaivyy/perseus --skill perseus-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Phase 4 Perseus Report generates a professional executive security report by synthesizing findings from the Scan, Audit, Exploit, and Specialist phases, helping stakeholders understand risks and remediation priorities.

Core Features & Use Cases

  • Consolidates deliverables from all Perseus phases into a single, executive-ready document.
  • Applies language- and framework-aware formatting to present risks, business impact, and remediation guidance.
  • Suitable for security reviews, board updates, and compliance reporting across multi-language codebases.

Quick Start

Run the /report command after completing the previous Perseus phases to produce the executive security report for your assessment.

Frequently Asked Questions about perseus:report

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

FAQPage Schema
How do I generate an executive security report for stakeholders?

Generate an executive security report by running the /report command after completing prior scan, audit, exploit, and specialist phases to synthesize findings into a formal document with risk metrics and remediation guidance.

What should an executive security report include for compliance reporting?

An executive security report for compliance should include consolidated phase deliverables, verified exploits prioritized by risk, business impact analysis, and language-specific remediation guidance across multi-language codebases.

Can I create security reports for multi-language codebases?

Yes, you can create security reports for multi-language codebases. The reporting process applies language- and framework-aware formatting to consolidate findings into a single executive-ready document.

Do I need to complete security scans and audits before generating a report?

Yes, you need to complete the scan, audit, exploit, and specialist phases first. The report requires collection of all phase deliverables and prioritization of verified exploits to produce the final document.

What is the best way to consolidate security findings into a formal document?

The best way to consolidate security findings is to synthesize deliverables from scan, audit, exploit, and specialist phases, applying language-specific formatting to generate a formal SECURITY_REPORT with risk metrics.

How does risk prioritization work in executive security reports?

Risk prioritization in executive security reports works by ranking verified exploits from the assessment phases, mapping them to business impact metrics to guide stakeholder remediation efforts across the codebase.