Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).
SkillScore84Maintained
Automatic
◆Security & AppSec pack
Last verified 8/7/2026
What it changes
Passed 19 of 23 test cases with the skill, and 15 of 23 without it.
Without skill64%
With skill84%
Checks it passed that the model alone missed
Recommends running dylint --all.
Recommends running slither-flat.
Specifies running golangci-lint run for Go static analysis.
and 2 more in the full report
5 fixed16 passed either way4 still failing0 broke
Pass-rate lift
+20 pp
Tokens
+135%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/7/2026v121 of 25 cases passed with skill · 23 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Our reviewers requested a single flattened source file for a contract that imports multiple OpenZeppelin libraries. Developers suggest manually copying file contents together. What Slither utility flattens smart contracts automatically?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends running slither-flat.
Missed
Passed
case-24 · gemini-3.6-flash · 8/7/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md404 lines2 files
Audit Prep Assistant
Purpose
Helps prepare for a security review using Trail of Bits' checklist. A well-prepared codebase makes the review process smoother and more effective.
Use this: 1-2 weeks before your security audit
The Preparation Process
Step 1: Set Review Goals
Helps define what you want from the review:
Key Questions:
What's the overall security level you're aiming for?
What areas concern you most?
Previous audit issues?
Complex components?
Fragile parts?
What's the worst-case scenario for your project?
Documents goals to share with the assessment team.
Step 2: Resolve Easy Issues
Runs static analysis and helps fix low-hanging fruit: