Smart contract development advisor based on Trail of Bits' best practices. Analyzes codebase to generate documentation/specifications, review architecture, check upgradeability patterns, assess implementation quality, identify pitfalls, review dependencies, and evaluate testing. Provides actionable recommendations.
SkillScore87Maintained
Automatic
◆Security & AppSec pack
Last verified 8/7/2026
What it changes
Passed 20 of 23 test cases with the skill, and 18 of 23 without it.
Without skill78%
With skill87%
Checks it passed that the model alone missed
The response identifies storage layout collision between the proxy and implementation state variables.
The response states that sections cannot be declared N/A without explicit codebase search and verification.
2 fixed18 passed either way3 still failing0 broke
Pass-rate lift
+9 pp
Tokens
+36%
Agent turns
0%
Response time
-34%
Model gemini-3.6-flashMeasured 8/7/2026v120 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
We deployed an ERC1967 proxy contract wrapping an implementation contract that stores state variables starting at slot 0. The implementation contract inherits from a base contract that also declares uint256 private _status at slot 0. What specific vulnerability check must be conducted during architectural analysis?
What was checked, without and with the skill
Checked
Without skill
With skill
The response identifies storage layout collision between the proxy and implementation state variables.
Missed
Passed
case-07 · 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.md247 lines2 files
Guidelines Advisor
Purpose
Systematically analyzes the codebase and provides guidance based on Trail of Bits' development guidelines:
Generate documentation and specifications (plain English descriptions, architectural diagrams, code documentation)
Optimize on-chain/off-chain architecture (only if applicable)
Review upgradeability patterns (if your project has upgrades)