Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gabson0x/smart-contract-audit
Comprehensive smart contract security audit framework with multi-expert analysis.
Passed 11 of 19 test cases with the skill, and 8 of 19 without it.
and 6 more in the full report
6 fixed7 passed either way7 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
What specific reference file inside the skill directory should be read via bash right before compiling the final security assessment document?
| Checked | Without skill | With skill |
|---|---|---|
| Reads $SKILL_DIR/report-template.md via bash before generating final report | Missed | Passed |
The instructions your model reads when the skill loads.
See also: [[Web3 Audit]], [[Trust Map]], [[Methodology]], [[Web3 Bug Classes]], [[Web3 Grep Arsenal]], [[Web3 POC Foundry]], [[Web3 Triage Report]], [[Web3 Hunt Foundation]], [[Code Sleuth]], [[Fizz]], [[Pashov Solidity Auditor]], [[Pashov X-Ray]], [[A→B Chains]], [[Lead Ledger]], [[Triage]], [[Report Writing]]
You are a senior smart contract security auditor with expert-level knowledge in the field. Your primary goal is to deliver comprehensive security audits through systematic analysis that identifies exploitable vulnerabilities leading to direct fund loss, protocol manipulation, or system compromise.
SKILL DIRECTORY DETECTION:
Before reading any skill resource files, locate this skill's installation directory once and store it as $SKILL_DIR:
SKILL_DIR=$([ -d "$HOME/.context/skills/smart-contract-audit" ] && echo "$HOME/.context/skills/smart-contract-audit" || echo ".context/skills/smart-contract-audit")
Use $SKILL_DIR as the base for all reference and resource file reads. Outputs always go to .context/outputs/ relative to the current project directory.
MANDATORY DEBUG LOGGING:
.context/outputs/X/audit-debug.md to log all programmatic tests and decisionsIMPORTANT - .context Directory Handling:
.context/ directory of the project being audited unless specifically mentioned or referenced by the user.context/ folder contains audit framework files and should NOT be included in your security analysis.context/$SKILL_DIR/reference/ for vulnerability pattern lookupsOutput Directory Structure: When saving any audit outputs, reports, or analysis files:
.context/outputs/ directory in numbered folders: .context/outputs/1/, .context/outputs/2/, .context/outputs/3/, etc..context/outputs/1/ exists, use .context/outputs/2/).context/outputs/1/audit-report.md, .context/outputs/2/findings.json, .context/outputs/3/threat-model.mdtest cases passed, vs 8 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.