fethallaheth/audit-reports-skill

Overview

This skill generates formatted security audit findings tailored to major Web3 contest platforms (Sherlock, Code4rena, Cantina). It produces platform-specific markdown or submission content ready for upload, following each platform's severity, PoC, and judging rules. Use it to convert raw vulnerability details into contest-ready reports.

How this skill works

I ask which platform you need (default: Code4rena) and collect the vulnerability title, severity, impact, root cause, affected code references, proof-of-concept, and remediation. Then I produce a fully formatted report using the target platform's template, severity conventions, and submission rules. The output is ready to paste into GitHub Issues, submission forms, or LightChaser templates.

When to use it

• You discovered a smart-contract bug and need a contest-ready writeup.
• You want to convert notes and test cases into a complete PoC and remediation.
• Preparing findings for Sherlock GitHub Issues with HIGH/MEDIUM classifications.
• Submitting to Code4rena with Risk Rating 3/2/1 and executable PoC requirements.
• Creating Cantina LightChaser reports with detailed impact/likelihood context.

Best practices

• Write a concise title and lead with the impact summary so judges see risk immediately.
• Include file:line code references and minimal reproducible PoC code or tests.
• Map severity explicitly to the selected platform's criteria before submission.
• Provide a clear root-cause explanation, not just symptoms, and a code-level fix.
• Avoid reporting issues classified as universally invalid (gas tweaks, trivial view issues).

Example use cases

• Convert local fuzzing failure and test script into a Code4rena submission with Risk 3 and an executable truffle/hardhat test.
• Format a critical reentrancy finding into a Sherlock GitHub Issue using HIGH severity and the Sherlock template.
• Draft a Cantina LightChaser report for a medium-impact DOS vector including impact, likelihood, and remediation steps.
• Turn audit notes into multiple platform-specific reports when contesting across venues.
• Validate severity choice and PoC completeness against platform judging criteria before finalizing submission.