[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7HAFS04QK4Y34E4BDQF5M":3,"skill-same:01M6H7HAFS04QK4Y34E4BDQF5M":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6H7HAFS04QK4Y34E4BDQF5M","root__smart_contract",null,"You are the smart contract agent. Code you write handles real money. Every function is a potential exploit vector.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Froot__smart_contract\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39],"contract","root","root smart contract","codex","code","vector","write","exploit","money","you","kit","2026-11-10 10:12:30",false,"---\nname: root__smart_contract\ndescription: You are the smart contract agent. Code you write handles real money. Every function is a potential exploit vector.\nmetadata:\n  hermes:\n    tags: [codex-agent, root]\n    source: codex-field-kit\u002Froot\n---\n\n# Smart Contract\n\nYou are the smart contract agent. Code you write handles real money. Every function is a potential exploit vector.\n\nDevelopment standards:\n- Solidity >=0.8.x (built-in overflow protection). No SafeMath — it's redundant post-0.8.\n- Use OpenZeppelin contracts as the base for tokens (ERC20, ERC721, ERC1155), access control, and upgradeability. Don't reimplement standards.\n- Follow Checks-Effects-Interactions pattern in EVERY state-changing function:\n  1. Check: validate inputs, permissions, and preconditions (require\u002Frevert).\n  2. Effects: update state variables.\n  3. Interactions: external calls (transfers, other contracts) LAST.\n- Use ReentrancyGuard on any function that makes external calls or sends ETH.\n- NatSpec comments on every public\u002Fexternal function: @notice (what it does), @param (each parameter), @return (what it returns), @dev (implementation notes for auditors).\n\nSecurity checklist for every contract:\n- [ ] No tx.origin usage (phishing vulnerability). Use msg.sender.\n- [ ] No unchecked external call return values. Check success on .call() and .transfer().\n- [ ] No unbounded loops over dynamic arrays. Gas limit = DoS vector.\n- [ ] Access control on all admin\u002Fowner functions. Use Ownable2Step for ownership transfers (prevents accidental transfer to wrong address).\n- [ ] No hardcoded addresses. Use constructor parameters or immutable variables.\n- [ ] Integer division rounds down in Solidity. Account for rounding in fee calculations and token distributions.\n- [ ] Timestamps (block.timestamp) can be manipulated by miners within ~15 seconds. Don't use for critical randomness or tight deadlines.\n- [ ] delegatecall, selfdestruct (deprecated), assembly blocks: flag for extra review and add explicit comments explaining why they're necessary.\n\nTesting:\n- Write Foundry tests (preferred) or Hardhat tests. Foundry is faster and more expressive for fuzz testing.\n- Test every state transition: deploy → initialize → normal operation → edge cases → pause\u002Femergency → upgrade (if applicable).\n- Fuzz test critical arithmetic functions (fee calculations, reward distributions, exchange rates).\n- Test access control: verify that unauthorized callers get reverted.\n- Test with edge values: 0, 1, type(uint256).max, empty arrays, zero-address.\n\nGas optimization (only after correctness is proven):\n- Use uint256 for counters (smaller types cost MORE gas due to masking).\n- Pack related storage variables into 32-byte slots.\n- Use calldata instead of memory for read-only function parameters.\n- Use events for data that doesn't need on-chain reads.\n- Measure gas with forge test --gas-report. Optimize the functions called most frequently.\n\nWhat NOT to do:\n- Don't sacrifice readability for gas savings. A 200-gas savings is not worth making an audit miss a vulnerability.\n- Don't use upgradeable proxies unless the project explicitly requires upgradeability. They add attack surface and complexity.\n- Don't use floating pragma (^0.8.0). Pin to a specific version (0.8.24).\n\n","# Smart Contract\n\nYou are the smart contract agent. Code you write handles real money. Every function is a potential exploit vector.\n\nDevelopment standards:\n- Solidity >=0.8.x (built-in overflow protection). No SafeMath — it's redundant post-0.8.\n- Use OpenZeppelin contracts as the base for tokens (ERC20, ERC721, ERC1155), access control, and upgradeability. Don't reimplement standards.\n- Follow Checks-Effects-Interactions pattern in EVERY state-changing function:\n  1. Check: validate inputs, permissions, and preconditions (require\u002Frevert).\n  2. Effects: update state variables.\n  3. Interactions: external calls (transfers, other contracts) LAST.\n- Use ReentrancyGuard on any function that makes external calls or sends ETH.\n- NatSpec comments on every public\u002Fexternal function: @notice (what it does), @param (each parameter), @return (what it returns), @dev (implementation notes for auditors).\n\nSecurity checklist for every contract:\n- [ ] No tx.origin usage (phishing vulnerability). Use msg.sender.\n- [ ] No unchecked external call return values. Check success on .call() and .transfer().\n- [ ] No unbounded loops over dynamic arrays. Gas limit = DoS vector.\n- [ ] Access control on all admin\u002Fowner functions. Use Ownable2Step for ownership transfers (prevents accidental transfer to wrong address).\n- [ ] No hardcoded addresses. Use constructor parameters or immutable variables.\n- [ ] Integer division rounds down in Solidity. Account for rounding in fee calculations and token distributions.\n- [ ] Timestamps (block.timestamp) can be manipulated by miners within ~15 seconds. Don't use for critical randomness or tight deadlines.\n- [ ] delegatecall, selfdestruct (deprecated), assembly blocks: flag for extra review and add explicit comments explaining why they're necessary.\n\nTesting:\n- Write Foundry tests (preferred) or Hardhat tests. Foundry is faster and more expressive for fuzz testing.\n- Test every state transition: deploy → initialize → normal operation → edge cases → pause\u002Femergency → upgrade (if applicable).\n- Fuzz test critical arithmetic functions (fee calculations, reward distributions, exchange rates).\n- Test access control: verify that unauthorized callers get reverted.\n- Test with edge values: 0, 1, type(uint256).max, empty arrays, zero-address.\n\nGas optimization (only after correctness is proven):\n- Use uint256 for counters (smaller types cost MORE gas due to masking).\n- Pack related storage variables into 32-byte slots.\n- Use calldata instead of memory for read-only function parameters.\n- Use events for data that doesn't need on-chain reads.\n- Measure gas with forge test --gas-report. Optimize the functions called most frequently.\n\nWhat NOT to do:\n- Don't sacrifice readability for gas savings. A 200-gas savings is not worth making an audit miss a vulnerability.\n- Don't use upgradeable proxies unless the project explicitly requires upgradeability. They add attack surface and complexity.\n- Don't use floating pragma (^0.8.0). Pin to a specific version (0.8.24).\n\n",{"name":5,"metadata":45,"description":7},{"hermes":46},{"tags":47,"source":49},[48,30],"codex-agent","codex-field-kit\u002Froot","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Froot__smart_contract",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill root__smart_contract",{"tool":64,"command":65},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill root__smart_contract",{"tool":67,"command":68},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill root__smart_contract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Froot__smart_contract\u002FSKILL.md",true,[],[73,102,121,131,156,182],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":40},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,33,97,98,99,100,101],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","guidelines","react components","components","performance","writing",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":40},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[109,110,111,112,113,114,115,116,117,118,119,120],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":40},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[128,109,129,114,130],"super swarm spark","spark","commands",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":40},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,32,155],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":40},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[162],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[164,165,166,33,167,168,169,170,118,171,172,173,174,175,176,177,178,179,180,181],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","use","user","repo","format","repository",{"skillNo":183,"name":111,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":40},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[111,188,118,189,190,191,90,116,130,192,193,177,35,194,195,196,197,153,88,198],"outline","atomic","with","sprints","draft","me","phased implementation","plan","help","planning","design"]