[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CR43T8KBKAM1G08HTBXK4C":3,"skill-same:01M7CR43T8KBKAM1G08HTBXK4C":44},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7CR43T8KBKAM1G08HTBXK4C","openzeppelin",null,"Develop smart contracts using OpenZeppelin Contracts library. Use when the user wants to create or modify Solidity contracts that use OpenZeppelin — including token standards (ERC20, ERC721, ERC1155), access control (Ownable, AccessControl), security primitives (Pausable, ReentrancyGuard), or any OZ extension. Covers library-first integration, pattern discovery from installed source, and version-safe development.","bro-rad\u002Fcoti-garbled-data-quickstart","bro-rad","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F325375301?v=4","01M7CR1FXF6N50Z1F90A5PAKE3","rad bro bot","01M7CR1FY2PSK9YKV9XG22M21X",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Fopenzeppelin\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: openzeppelin\ndescription: \"Develop smart contracts using OpenZeppelin Contracts library. Use when the user wants to create or modify Solidity contracts that use OpenZeppelin — including token standards (ERC20, ERC721, ERC1155), access control (Ownable, AccessControl), security primitives (Pausable, ReentrancyGuard), or any OZ extension. Covers library-first integration, pattern discovery from installed source, and version-safe development.\"\n---\n\n# Develop Smart Contracts with OpenZeppelin\n\nAdapted from [OpenZeppelin's official skill](https:\u002F\u002Fgithub.com\u002FOpenZeppelin\u002Fopenzeppelin-skills) for Scaffold-ETH 2 Solidity projects.\n\n## Prerequisites\n\nCheck if `.\u002Fpackages\u002Fnextjs\u002Fscaffold.config.ts` exists directly in the current working directory (do not search subdirectories). If it doesn't exist, this is not a Scaffold-ETH 2 project. Follow the instructions at https:\u002F\u002Fdocs.scaffoldeth.io\u002FSKILL.md to scaffold it first. If it exists, continue directly with building.\n\nDetect the Solidity framework flavor:\n- If `packages\u002Fhardhat` exists → **Hardhat flavor**\n- If `packages\u002Ffoundry` exists → **Foundry flavor**\n\n## Core Principle: Prefer Library Components Over Custom Code\n\nBefore writing ANY contract logic, search the installed OpenZeppelin library for an existing component:\n\n1. **Exact match exists?** Import and use it directly — inherit, override only what's needed\n2. **Close match exists?** Import and extend — override only functions the library marks as `virtual`\n3. **No match?** Only then write custom logic. Confirm by browsing the library's directory first\n\n**Never hand-write what the library already provides:**\n- Don't write `require(totalSupply() + amount \u003C= cap)` when `ERC20Capped` exists\n- Don't write `require(msg.sender == owner)` when `Ownable` exists\n- Don't implement token transfer hooks manually when the library's base contracts handle it\n- Don't copy library source into your contract — always import from the dependency so the project gets security updates\n\n## Pattern Discovery: Read the Installed Source\n\nAPIs, override points, and import syntax change between major versions. Don't assume patterns from memory — always verify by reading the installed source.\n\n### Step 1: Identify the installed version and browse the library\n\nFind the OpenZeppelin version and locate the installed source:\n\n- **Hardhat**: check `packages\u002Fhardhat\u002Fpackage.json` for `@openzeppelin\u002Fcontracts` version, then browse `packages\u002Fhardhat\u002Fnode_modules\u002F@openzeppelin\u002Fcontracts\u002F`\n- **Foundry**: check `packages\u002Ffoundry\u002Flib\u002Fopenzeppelin-contracts\u002F` and the remappings in `packages\u002Ffoundry\u002Ffoundry.toml`\n\nBrowse the library's directory structure to discover available components. Key directories inside the OZ contracts root:\n- `token\u002F{ERC20,ERC721,ERC1155}\u002F` — token standards and their base implementations\n- `token\u002F{ERC20,ERC721}\u002Fextensions\u002F` — Capped, Burnable, Pausable, Permit, Votes, Enumerable, etc.\n- `access\u002F` — Ownable, AccessControl, AccessManager\n- `utils\u002F` — ReentrancyGuard, Pausable, math, structs\n\n### Step 2: Read the source file for the component you need\n\nLook at:\n- **Import syntax**: how the library's own files import each other — mirror that style. OZ v5+ uses named imports:\n  ```solidity\n  \u002F\u002F ✅ import {ERC20} from \"@openzeppelin\u002Fcontracts\u002Ftoken\u002FERC20\u002FERC20.sol\";\n  \u002F\u002F ❌ import \"@openzeppelin\u002Fcontracts\u002Ftoken\u002FERC20\u002FERC20.sol\";\n  ```\n- **`virtual` functions**: only these can be overridden. Functions that were virtual in one version may not be in another\n- **Constructor parameters**: what must be passed during deployment\n- **NatSpec comments**: `NOTE: This function is not virtual, {X} should be overridden instead` — follow these\n\n### Step 3: Extract the minimal integration pattern\n\nFrom the source, identify only what's needed:\n- Imports to add\n- Inheritance chain\n- Constructor parameters and chaining\n- Required overrides (when inheriting multiple contracts that define the same virtual function, you must override it and call `super`)\n- New functions to expose\n\n### Step 4: Apply to the user's contract\n\nIntegrate into existing code. Check for conflicts: duplicate access control, incompatible inheritance, missing overrides. The Solidity compiler will error if two parent contracts define the same function and you don't explicitly override it.\n\n## SE-2 Integration Notes\n\n- OpenZeppelin is pre-installed in both flavors — no additional dependency installation needed\n- Contracts: `packages\u002Fhardhat\u002Fcontracts\u002F` (Hardhat) or `packages\u002Ffoundry\u002Fcontracts\u002F` (Foundry)\n- Deploy scripts: `packages\u002Fhardhat\u002Fdeploy\u002F` (Hardhat) or `packages\u002Ffoundry\u002Fscript\u002F` (Foundry)\n- Frontend reads contract ABIs from `packages\u002Fnextjs\u002Fcontracts\u002FdeployedContracts.ts` (auto-generated by `yarn deploy`)\n","# Develop Smart Contracts with OpenZeppelin\n\nAdapted from [OpenZeppelin's official skill](https:\u002F\u002Fgithub.com\u002FOpenZeppelin\u002Fopenzeppelin-skills) for Scaffold-ETH 2 Solidity projects.\n\n## Prerequisites\n\nCheck if `.\u002Fpackages\u002Fnextjs\u002Fscaffold.config.ts` exists directly in the current working directory (do not search subdirectories). If it doesn't exist, this is not a Scaffold-ETH 2 project. Follow the instructions at https:\u002F\u002Fdocs.scaffoldeth.io\u002FSKILL.md to scaffold it first. If it exists, continue directly with building.\n\nDetect the Solidity framework flavor:\n- If `packages\u002Fhardhat` exists → **Hardhat flavor**\n- If `packages\u002Ffoundry` exists → **Foundry flavor**\n\n## Core Principle: Prefer Library Components Over Custom Code\n\nBefore writing ANY contract logic, search the installed OpenZeppelin library for an existing component:\n\n1. **Exact match exists?** Import and use it directly — inherit, override only what's needed\n2. **Close match exists?** Import and extend — override only functions the library marks as `virtual`\n3. **No match?** Only then write custom logic. Confirm by browsing the library's directory first\n\n**Never hand-write what the library already provides:**\n- Don't write `require(totalSupply() + amount \u003C= cap)` when `ERC20Capped` exists\n- Don't write `require(msg.sender == owner)` when `Ownable` exists\n- Don't implement token transfer hooks manually when the library's base contracts handle it\n- Don't copy library source into your contract — always import from the dependency so the project gets security updates\n\n## Pattern Discovery: Read the Installed Source\n\nAPIs, override points, and import syntax change between major versions. Don't assume patterns from memory — always verify by reading the installed source.\n\n### Step 1: Identify the installed version and browse the library\n\nFind the OpenZeppelin version and locate the installed source:\n\n- **Hardhat**: check `packages\u002Fhardhat\u002Fpackage.json` for `@openzeppelin\u002Fcontracts` version, then browse `packages\u002Fhardhat\u002Fnode_modules\u002F@openzeppelin\u002Fcontracts\u002F`\n- **Foundry**: check `packages\u002Ffoundry\u002Flib\u002Fopenzeppelin-contracts\u002F` and the remappings in `packages\u002Ffoundry\u002Ffoundry.toml`\n\nBrowse the library's directory structure to discover available components. Key directories inside the OZ contracts root:\n- `token\u002F{ERC20,ERC721,ERC1155}\u002F` — token standards and their base implementations\n- `token\u002F{ERC20,ERC721}\u002Fextensions\u002F` — Capped, Burnable, Pausable, Permit, Votes, Enumerable, etc.\n- `access\u002F` — Ownable, AccessControl, AccessManager\n- `utils\u002F` — ReentrancyGuard, Pausable, math, structs\n\n### Step 2: Read the source file for the component you need\n\nLook at:\n- **Import syntax**: how the library's own files import each other — mirror that style. OZ v5+ uses named imports:\n  ```solidity\n  \u002F\u002F ✅ import {ERC20} from \"@openzeppelin\u002Fcontracts\u002Ftoken\u002FERC20\u002FERC20.sol\";\n  \u002F\u002F ❌ import \"@openzeppelin\u002Fcontracts\u002Ftoken\u002FERC20\u002FERC20.sol\";\n  ```\n- **`virtual` functions**: only these can be overridden. Functions that were virtual in one version may not be in another\n- **Constructor parameters**: what must be passed during deployment\n- **NatSpec comments**: `NOTE: This function is not virtual, {X} should be overridden instead` — follow these\n\n### Step 3: Extract the minimal integration pattern\n\nFrom the source, identify only what's needed:\n- Imports to add\n- Inheritance chain\n- Constructor parameters and chaining\n- Required overrides (when inheriting multiple contracts that define the same virtual function, you must override it and call `super`)\n- New functions to expose\n\n### Step 4: Apply to the user's contract\n\nIntegrate into existing code. Check for conflicts: duplicate access control, incompatible inheritance, missing overrides. The Solidity compiler will error if two parent contracts define the same function and you don't explicitly override it.\n\n## SE-2 Integration Notes\n\n- OpenZeppelin is pre-installed in both flavors — no additional dependency installation needed\n- Contracts: `packages\u002Fhardhat\u002Fcontracts\u002F` (Hardhat) or `packages\u002Ffoundry\u002Fcontracts\u002F` (Foundry)\n- Deploy scripts: `packages\u002Fhardhat\u002Fdeploy\u002F` (Hardhat) or `packages\u002Ffoundry\u002Fscript\u002F` (Foundry)\n- Frontend reads contract ABIs from `packages\u002Fnextjs\u002Fcontracts\u002FdeployedContracts.ts` (auto-generated by `yarn deploy`)\n",{"name":5,"description":7},"coti-garbled-data-quickstart","a42ff7e0f45ad7809fc2db6bd9d2ef253c1688ed",".agents\u002Fskills\u002Fopenzeppelin","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart","https:\u002F\u002Fgithub.com\u002Fbro-rad","2026-10-01 08:51:30",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add bro-rad\u002Fcoti-garbled-data-quickstart --skill openzeppelin",{"tool":36,"command":37},"bunx","bunx skills add bro-rad\u002Fcoti-garbled-data-quickstart --skill openzeppelin",{"tool":39,"command":40},"pnpm","pnpm dlx skills add bro-rad\u002Fcoti-garbled-data-quickstart --skill openzeppelin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Fopenzeppelin\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7CR605WRFVMSS3PW3CWJBAV","x402","Add x402 payment-gated routes to a Scaffold-ETH 2 project. Use when the user wants to: monetize an API with micropayments, add HTTP 402 payment required to routes, gate content behind crypto payments, implement pay-per-call APIs, or integrate the x402 protocol.","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7CR5WPS4WBP6MRF67SWGK13","why-ethereum","Why build on Ethereum specifically. The AI agent angle — ERC-8004, x402, composability, permissionless deployment. Use when a user asks \"should I build on Ethereum?\", \"why blockchain?\", or when an agent needs to recommend a chain for a project.","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CR5RNY740CT0P9DT9HFB2T","wallets","How to create, manage, and use Ethereum wallets. Covers EOAs, smart contract wallets, multisig (Safe), and account abstraction. Use this skill whenever you are sending transactions, signing messages, or managing funds. Includes guardrails for safe key handling.","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Fwallets\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CR5MGAM27HZHA688XRD6PV","tools","Current Ethereum development tools, frameworks, libraries, RPCs, and block explorers. What actually works today for building on Ethereum. Includes tool discovery for AI agents — MCPs, abi.ninja, Foundry, Scaffold-ETH 2, Hardhat, and more. Use when setting up a dev environment, choosing tools, or when an agent needs to discover what's available.","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Ftools\u002FSKILL.md",[],[],{"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":79,"publishedAt":19},"01M7CR5HWD8ZR834W3XDEEKTXY","testing","Smart contract testing with Foundry — unit tests, fuzz testing, fork testing, invariant testing. Use when writing tests for a smart contract.","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Ftesting\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CR5DW03X87CNGQ1BX7QX0Q","subgraph","Integrate The Graph subgraph into a Scaffold-ETH 2 project for indexing blockchain events. Use when the user wants to: index contract events with The Graph, add a subgraph, query onchain data with GraphQL, set up a local graph node, or deploy a subgraph to Subgraph Studio.","https:\u002F\u002Fgithub.com\u002Fbro-rad\u002Fcoti-garbled-data-quickstart\u002Fblob\u002Fcoti-garbled-data-quickstart\u002F.agents\u002Fskills\u002Fsubgraph\u002FSKILL.md",[],[]]