report

Generates submission-ready smart contract audit reports from validated findings and PoC results.

66|17|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/BitterSecurity/Vigilo --skill report-bittersecurity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report
Source: https://github.com/BitterSecurity/Vigilo/tree/main/packages/claude/skills/report
Command: npx skills add https://github.com/BitterSecurity/Vigilo --skill report-bittersecurity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a smart contract security audit, raw findings and PoC validation logs must be transformed into polished, platform-compliant reports for Code4rena, Cantina, Sherlock, or Immunefi. Manually reformatting each finding, mapping severities, and embedding PoC code is slow and error-prone. ## Core Features & Use Cases - Multi-Platform Templates: Generates reports in Code4rena (default), Cantina, Sherlock, Immunefi, or standard audit formats with correct severity mappings. - Validation-Aware Filtering: Reads findings from .vigilo/findings/ and PoC logs from .vigilo/poc/, including only VALIDATED findings in submissions and separating NEEDS_REVIEW items. - Submission-Ready Output: Produces individual finding files with inline PoC code, execution output, and recommendations, plus an executive summary report. - Use Case: After Vigilo's audit pipeline validates a reentrancy vulnerability, invoke this Skill to produce a Code4rena-formatted submission with the Foundry PoC inline, ready to paste directly into the contest platform. ## Quick Start Generate Code4rena submission reports from the validated findings in .vigilo/findings/ and the PoC logs in .vigilo/poc/.

Frequently Asked Questions about report

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

FAQPage Schema
How do I generate a Code4rena audit report from my findings?▼

Place your findings in .vigilo/findings/ and PoC validation logs in .vigilo/poc/, then invoke the report generation workflow. Code4rena is the default format, producing individual High/Medium submissions plus a bundled QA report for Low findings.

What audit platforms does this report generator support?▼

It supports Code4rena, Cantina, Sherlock, Immunefi, and a general standard format. Each platform has a dedicated template with its required sections, severity mappings, and submission conventions.

How are findings filtered before report generation?▼

Findings are filtered by validation status from PoC results. VALIDATED findings get full submission reports, NEEDS_REVIEW items go into a separate Unconfirmed section, and INVALIDATED findings are excluded as false positives.

Does the report include the proof of concept code?▼

Yes, each submission report embeds the full Foundry PoC code inline rather than referencing external files. It also includes the forge test command and console output demonstrating the exploit's impact.

How are severity levels mapped across audit platforms?▼

A severity classification reference maps Vigilo severities to each platform's standard, such as Code4rena's High/Medium/QA tiers and Immunefi's Critical-to-Low payout ranges. The mapping is applied automatically when a platform template is selected.