Commands Skill

You can automate a smart contract vulnerability audit by invoking commands like /audit or /scan with your target file and chain parameters. This routes the request to underlying audit workflows to perform automated vulnerability analysis and generate reports.

Yes, you can chain multiple audit commands together to compose end-to-end security pipelines. This allows you to sequence workflows like scanning, variant analysis, severity classification, and report generation across multiple chains.

Yes, the slash command audit workflow supports multiple blockchain chains. You can specify the target network directly in your command parameters, such as using the --chain flag with ethereum, to ensure the vulnerability analysis applies the correct context.

The best way to generate a security report after a quick scan is to use the /report command. It maps to underlying report generation workflows, allowing you to compile findings, severity classifications, and scan results into a structured output.

No external dependencies are required to run checklist-based security scans. The system identifies capabilities through frontmatter metadata and relies on optional resources like scripts or references only if they are present in the environment.

You should use a quick scan instead of a full audit workflow when you need rapid vulnerability checks or pattern browsing. A full audit provides comprehensive end-to-end analysis, while quick scans offer faster, targeted security assessments.