About Security Auditing
A security audit moves from understanding the code to finding bugs, then to proving or discarding each suspect. The skills in this category cover those stages. Context-building skills map what each function assumes before any bug hunt, scanners check for known vulnerability patterns, and verification skills return a true or false positive verdict with evidence.
Smart contract work has its own group: scanners for Solana, Cairo, Cosmos, Substrate, TON and Algorand each check platform-specific flaws, and companions list entry points, rate code maturity and guide a secure development workflow. For native code there are review skills for C, C++ and Rust, plus guidance on modern C++ hardening.
When choosing, match the skill to the language and stage of the project. Prefer skills that report a verdict for every pattern they check, so a clean result is evidence and silence is never ambiguous. Look at the output format too: a SARIF file or a severity-ranked report drops straight into a review process.
Run a diff review on each change, a deeper scan before a release, and a patch validation pass after fixes land.