Why does it link to PoC files instead of pasting the code?

Linking to a PoC file keeps the report concise and readable while ensuring the Proof of Concept remains executable. Full code inclusion is reserved for explicit requests or very short snippets.

Does Weasel Report find vulnerabilities automatically?

No, this specific skill is designed for documenting findings you have already discovered or validated. You should use weasel-analyzer to find issues first.

Where does the skill save the generated reports?

By default, reports are written to a 'findings/' directory within your project using a standardized naming convention like - - .md.

Can I generate a single report for multiple findings?

Yes, when multiple findings are present, the skill will ask if you prefer separate files for each vulnerability or one combined audit-report.md file.

Weasel Audit Report Writer

Name: Weasel Audit Report Writer
Author: slvDev

byslvDev

•

Seguridad y Pruebas

Generates professional, submission-ready Solidity security audit reports and markdown documentation for smart contract vulnerabilities.

Acerca de

Weasel Audit Report Writer is a specialized skill for security researchers and developers that automates the documentation phase of smart contract auditing. It transforms confirmed vulnerabilities into structured markdown reports, enforcing industry-standard naming conventions and layouts. By automatically organizing findings into a dedicated directory and prioritizing file-based output over terminal logs, it ensures that security findings are polished, consistent, and ready for submission to bug bounty platforms or internal review teams.

Características Principales

Smart code snippet inclusion with impact and recommendation sections
Support for both individual finding files and combined audit reports
Severity-based file naming (H-01, M-01) for organized vulnerability tracking
10 GitHub stars
Automated markdown report generation with standardized security templates
Integrated PoC linking to maintain clean, readable audit documentation

Casos de Uso

Preparing professional vulnerability submissions for bug bounty platforms like Immunefi or Code4rena
Converting raw security findings into formatted reports for client delivery
Standardizing internal security documentation during smart contract development lifecycles

Acerca de

Características Principales

Smart code snippet inclusion with impact and recommendation sections
Support for both individual finding files and combined audit reports
Severity-based file naming (H-01, M-01) for organized vulnerability tracking
10 GitHub stars
Automated markdown report generation with standardized security templates
Integrated PoC linking to maintain clean, readable audit documentation

Casos de Uso

Preparing professional vulnerability submissions for bug bounty platforms like Immunefi or Code4rena
Converting raw security findings into formatted reports for client delivery
Standardizing internal security documentation during smart contract development lifecycles