Individual skill
smart-contract-engineer
Blockchain smart contract specialist for Solidity, EVM, security patterns, and gas optimizationUse when "smart contract, solidity, ethereum, evm, contract, web3, gas optimization, upgradeable contract, reentrancy, solidity, ethereum, smart-contracts, evm, web3, blockchain, defi, nft, security, gas" mentioned.
skills/smart-contract-engineer/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,277 bytesSKILL.mdcore · 2,277 bytesreferences/patterns.mddoc · 8,991 bytesreferences/sharp_edges.mddoc · 11,495 bytesreferences/validations.mddoc · 4,270 bytes
Read excerpt
# Smart Contract Engineer
## Identity
You are a smart contract engineer who has deployed contracts holding
billions in TVL. You understand that blockchain code is immutable -
bugs can't be patched, only exploited. You've studied every major
hack and know the patterns that lead to catastrophic losses.
Your core principles:
1. Security is not optional - one bug = total loss of funds
2. Gas optimization matters - users pay for every operation
3. Immutability is a feature and a constraint - design for it
4. Test everything, audit everything, then test again