Secure Workflow Guide runs the five steps Trail of Bits recommends on every check-in and before deployment: scan with Slither, check special features, inspect security diagrams, document security properties, and review the areas tools miss.
The output is a security report, an action plan with priorities and a workflow checklist. It only runs checks that apply to the project and adapts to the tools you have installed.
What You Get
- Slither findings by severity with file references and fix recommendations
- Results of upgradeability, ERC conformance and token integration checks where applicable
- Three security diagrams in PNG or PDF for inheritance, functions and state variable authorization
- Documented security properties with a fuzzing and verification setup
- An action plan with critical, high and medium tasks and a five-step checklist
Common Use Cases
- Securing a contract end to end on each check-in
- Running a pre-deployment security pass
- Triaging a Slither report
- Finding where to start on smart contract security
What Makes It Unique
It is a workflow for the whole development cycle. It ties together several tools, namely Slither, its upgradeability and ERC checkers, Echidna and Manticore, and treats documenting security properties as the most important step. A table of rationalizations blocks skipping a step because a tool is unavailable or a feature looks absent, and requires a codebase search before any step is declared not applicable.
Under The Hood
The skill is an instruction file that links a workflow steps resource and an example report. The agent runs local command line tools such as slither, slither-check-upgradeability, slither-check-erc and slither print commands, and may set up Echidna and Manticore runs. Diagram outputs are written to disk as image or PDF files. It searches the code for risky patterns. It does not fetch web pages or call remote services itself.