Score breakdown0 Version history1 Source
Category Weight Category score Contribution
Security prompt, exec, net, exfil, eval
35%
100
35.0 pts
Supply chain hash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenance staleness, pinning, CI
15%
100
15.0 pts
Transparency SKILL.md, perms, README
15%
100
15.0 pts
Community installs, verify, response
15%
100
15.0 pts
Findings & checks · 0 flagged
Security score 100 · 0 findings
✓ — All security checks passedNo findings in this category for the latest scan. pass
Supply chain score 100 · 0 findings
✓ — All supply chain checks passedNo findings in this category for the latest scan. pass
Maintenance score 100 · 0 findings
✓ — All maintenance checks passedNo findings in this category for the latest scan. pass
Transparency score 100 · 0 findings
✓ — All transparency checks passedNo findings in this category for the latest scan. pass
Community score 100 · 0 findings
✓ — All community checks passedNo findings in this category for the latest scan. pass
Every scanned point with the score it earned and what moved between them.
1 scans · 90 days d79592e latest
Jun 24, 2026 100 d79592e
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
skills/web3/smart-contracts/SKILL.md · 1 file skills/web3/smart-contracts/SKILL.md 1.8 KB · Markdown Rendered Raw ⧉ Copy
Web3 & Smart Contracts PUDO Checklist 1. PLAN (Architecture & Strategy) [ ] Protocol Design: Define contract architecture (e.g., Monolithic vs. Proxy/Upgradable vs. Diamond pattern). [ ] Tokenomics: Map out value flow, minting, burning, and pausing capabilities (ERC20/ERC721/ERC1155). [ ] Access Control: Plan roles (Owner, Admin, Minter) and multisig requirements. [ ] Gas Economics: Architect data structures to minimize storage operations (packing variables). 2. UNDERSTAND (Context & Auditing) [ ] Dependencies: Validate versions of inherited libraries (e.g., OpenZeppelin Contracts). [ ] External Interactions: Map all calls to external, untrusted contracts (risk of reentrancy). [ ] State Changes: Understand the lifecycle of state variables over the contract's active period. 3. DEVELOP (Implementation) [ ] CEI Pattern: STRICTLY adhere to Checks-Effects-Interactions pattern for all state-mutating functions. [ ] Modifiers: Use modifiers for access control and validation logically without bloating gas. [ ] Events: Emit events for all significant state changes for off-chain indexing. [ ] Testing: Achieve 100% branch test coverage using Foundry or Hardhat. Include fuzz testing and invariant testing. [ ] Security Auditing: Run static analyzers (Slither, Aderyn) to catch common vulnerabilities (reentrancy, arithmetic overflows). [ ] Gas Optimization: Use calldata instead of memory for read-only external inputs. Pack structs to fit in 256-bit slots. [ ] Upgradability: If using proxies, ensure storage slots do not clash on upgrades (append-only storage). [ ] Documentation: Add NatSpec comments (@title, @notice, @param) to all public/external functions.