What problem does it solve? Smart contract audits often produce inconsistent findings across different auditors, making reports hard to compare, validate, and act on. This Skill enforces a single rigorous standard for documenting vulnerabilities so every finding includes code evidence, concrete attack steps, and consistent severity ratings. ## Core Features & Use Cases - Iron Laws Enforcement: Requires every finding to cite exact file paths, function names, line numbers, and annotated code snippets, rejecting vague or speculative claims. - Standardized Finding Template: Provides a Code4rena-style report format with root cause, impact, numbered attack scenario steps, and mitigation code. - Severity Classification & File Organization: Classifies findings as High, Medium, or Low and writes them to a structured .vigilo/findings/ directory with one file per finding. - Use Case: A sub-auditor agent analyzing a Solidity vault contract for reentrancy uses this Skill to write a properly formatted H-01 finding with an annotated code snippet and step-by-step attack scenario, which the main agent later converts into a Foundry PoC test. ## Quick Start Analyze the withdraw function in src/Vault.sol for reentrancy and write a formatted vulnerability finding to the findings directory.
