Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/solidity-security
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns.
Passed 21 of 22 test cases with the skill, and 20 of 22 without it.
1 fixed20 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
On an automated market maker or DEX contract, users submit trade orders that get front-run in the public mempool. What classic two-step architectural pattern using cryptographic hashes prevents searchers from seeing and copying raw trade details before execution?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies commit-reveal as the architecture to mitigate mempool front-running. | Passed | Passed |
| Recommends keccak256 hashing for trade commitments in the initial step. | Missed | Passed |
The instructions your model reads when the skill loads.
Master smart contract security best practices, vulnerability prevention, and secure Solidity development patterns.
Attacker calls back into your contract before state is updated.
Vulnerable Code:
// VULNERABLE TO REENTRANCY
contract VulnerableBank {
mapping(address => uint256) public balances;
function withdraw() public {
uint256 amount = balances[msg.sender];
// DANGER: External call before state update
(bool success, ) = msg.sender.call{value: amount}("");
require(success);
balances[msg.sender] = 0; // Too late!
}
}
Secure Pattern (Checks-Effects-Interactions):
contract SecureBank {
test cases passed, vs 20 / 22 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.