Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing. Produces professional scorecard with evidence-based ratings and actionable recommendations.
SkillScore68Maintained
Automatic
◆Security & AppSec pack
Last verified 8/7/2026
What it changes
Passed 17 of 25 test cases with the skill, and 13 of 25 without it.
Without skill52%
With skill68%
Checks it passed that the model alone missed
Includes overall average score in the Executive Summary.
Assigns a 1-2 month timeframe for HIGH priority recommendations.
Assigns a 2-4 month timeframe for MEDIUM priority recommendations.
and 4 more in the full report
6 fixed11 passed either way6 still failing2 broke
Pass-rate lift
+16 pp
Tokens
+34%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/7/2026v117 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
A module has no Weak criteria met, all Moderate criteria met, and 2 out of 4 Satisfactory criteria met. The developer wants to know if this qualifies as Moderate or Satisfactory.
What was checked, without and with the skill
Checked
Without skill
With skill
Assigns a rating of Satisfactory (3) when all Moderate criteria are met alongside some Satisfactory criteria.
Missed
Passed
case-12 · 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.md213 lines2 files
Code Maturity Assessor
Purpose
Systematically assesses codebase maturity using Trail of Bits' 9-category framework. Provides evidence-based ratings and actionable recommendations.
Framework: Building Secure Contracts - Code Maturity Evaluation v0.1.0
How This Works
Phase 1: Discovery
Explores the codebase to understand:
Project structure and platform
Contract/module files
Test coverage
Documentation availability
Phase 2: Analysis
For each of 9 categories, I'll:
Search the code for relevant patterns
Read key files to assess implementation
Present findings with file references
Ask clarifying questions about processes I can't see in code