Individual skill
solidity-pro
Write secure, gas-efficient Solidity smart contracts for EVM chains: tokens, vaults, access control, upgrade patterns, testing and audit checklists. Use when developing or reviewing on-chain contracts.
skills/solidity-pro/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
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 8, 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)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- security Derived category
- testing 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
Read excerpt
# Solidity Pro
A field guide to writing Solidity contracts that are correct first and cheap second: secure defaults, gas-aware patterns, thorough testing, and a pre-deploy audit checklist. Covers ERC-20/721/1155 tokens, vaults, access control, and proxy upgrades.
## Overview
Solidity runs on the EVM where every storage write costs gas, code is immutable once deployed (unless proxied), and bugs can lock or drain real funds. The discipline that matters most is **defensive design**: assume every external call is hostile, every input is adversarial, and every privileged function will be probed.
Two invariants cover most vulnerabilities:
1. **Checks-Effects-Interactions** — validate, update your own state, then call out.
2. **Least privilege** — no function is more powerful than it needs to be.
## When to use
