[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XJZKPC8Q682TJTKS7828C":3,"skill-same:01M79XJZKPC8Q682TJTKS7828C":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79XJZKPC8Q682TJTKS7828C","code-maturity-assessor",null,"Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing, then produces a scorecard with evidence-based ratings and a priority-ordered roadmap. Use when assessing or scoring the maturity of a smart contract or blockchain codebase, producing a maturity scorecard or evaluation, or judging how mature, well-tested, or well-documented such a project is against a rubric.","Heesho\u002Fraffle-fun","Heesho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100749457?v=4","01M79XHBVXHD5BHPJTHXK51VSC","01M79XHBWZQNAH0BTYT9A1RFCW",0,"MIT","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-maturity-assessor\ndescription: Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing, then produces a scorecard with evidence-based ratings and a priority-ordered roadmap. Use when assessing or scoring the maturity of a smart contract or blockchain codebase, producing a maturity scorecard or evaluation, or judging how mature, well-tested, or well-documented such a project is against a rubric.\n---\n\n# Code Maturity Assessor\n\n## Purpose\n\nSystematically assesses codebase maturity using Trail of Bits' 9-category framework. Provides evidence-based ratings and actionable recommendations.\n\n**Framework**: Building Secure Contracts - Code Maturity Evaluation v0.1.0\n\n---\n\n## How This Works\n\n### Phase 1: Discovery\nExplores the codebase to understand:\n- Project structure and platform\n- Contract\u002Fmodule files\n- Test coverage\n- Documentation availability\n\n### Phase 2: Analysis\nFor each of 9 categories, I'll:\n- **Search the code** for relevant patterns\n- **Read key files** to assess implementation\n- **Present findings** with file references\n- **Ask clarifying questions** about processes I can't see in code\n- **Determine rating** based on criteria\n\n### Phase 3: Report\nGenerates:\n- Executive summary\n- Maturity scorecard (ratings for all 9 categories)\n- Detailed analysis with evidence\n- Priority-ordered improvement roadmap\n\n---\n\n## Rating System\n\n- **Missing (0)**: Not present\u002Fnot implemented\n- **Weak (1)**: Several significant improvements needed\n- **Moderate (2)**: Adequate, can be improved\n- **Satisfactory (3)**: Above average, minor improvements\n- **Strong (4)**: Exceptional, only small improvements possible\n\n**Rating Logic**:\n- ANY \"Weak\" criteria → **Weak**\n- NO \"Weak\" + SOME \"Moderate\" unmet → **Moderate**\n- ALL \"Moderate\" + SOME \"Satisfactory\" met → **Satisfactory**\n- ALL \"Satisfactory\" + exceptional practices → **Strong**\n\n---\n\n## The 9 Categories\n\nI assess 9 comprehensive categories covering all aspects of code maturity. For detailed criteria, analysis approaches, and rating thresholds, see [ASSESSMENT_CRITERIA.md](resources\u002FASSESSMENT_CRITERIA.md).\n\n### Quick Reference:\n\n**1. ARITHMETIC**\n- Overflow protection mechanisms\n- Precision handling and rounding\n- Formula specifications\n- Edge case testing\n\n**2. AUDITING**\n- Event definitions and coverage\n- Monitoring infrastructure\n- Incident response planning\n\n**3. AUTHENTICATION \u002F ACCESS CONTROLS**\n- Privilege management\n- Role separation\n- Access control testing\n- Key compromise scenarios\n\n**4. COMPLEXITY MANAGEMENT**\n- Function scope and clarity\n- Cyclomatic complexity\n- Inheritance hierarchies\n- Code duplication\n\n**5. DECENTRALIZATION**\n- Centralization risks\n- Upgrade control mechanisms\n- User opt-out paths\n- Timelock\u002Fmultisig patterns\n\n**6. DOCUMENTATION**\n- Specifications and architecture\n- Inline code documentation\n- User stories\n- Domain glossaries\n\n**7. TRANSACTION ORDERING RISKS**\n- MEV vulnerabilities\n- Front-running protections\n- Slippage controls\n- Oracle security\n\n**8. LOW-LEVEL MANIPULATION**\n- Assembly usage\n- Unsafe code sections\n- Low-level calls\n- Justification and testing\n\n**9. TESTING & VERIFICATION**\n- Test coverage\n- Fuzzing and formal verification\n- CI\u002FCD integration\n- Test quality\n\nFor complete assessment criteria including what I'll analyze, what I'll ask you, and detailed rating thresholds (WEAK\u002FMODERATE\u002FSATISFACTORY\u002FSTRONG), see [ASSESSMENT_CRITERIA.md](resources\u002FASSESSMENT_CRITERIA.md).\n\n---\n\n## Example Output\n\nWhen the assessment is complete, you'll receive a comprehensive maturity report including:\n\n- **Executive Summary**: Overall score, top 3 strengths, top 3 gaps, priority recommendations\n- **Maturity Scorecard**: Table with all 9 categories rated with scores and notes\n- **Detailed Analysis**: Category-by-category breakdown with evidence (file:line references)\n- **Improvement Roadmap**: Priority-ordered recommendations (CRITICAL\u002FHIGH\u002FMEDIUM) with effort estimates\n\nFor a complete example assessment report, see [EXAMPLE_REPORT.md](resources\u002FEXAMPLE_REPORT.md).\n\n---\n\n## Assessment Process\n\nWhen invoked, I will:\n\n1. **Explore codebase**\n   - Find contract\u002Fmodule files\n   - Identify test files\n   - Locate documentation\n\n2. **Analyze each category**\n   - Search for relevant code patterns\n   - Read key implementations\n   - Assess against criteria\n   - Collect evidence\n\n3. **Interactive assessment**\n   - Present my findings with file references\n   - Ask about processes I can't see in code\n   - Discuss borderline cases\n   - Determine ratings together\n\n4. **Generate report**\n   - Executive summary\n   - Maturity scorecard table\n   - Detailed category analysis with evidence\n   - Priority-ordered improvement roadmap\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Found some findings, assessment complete\" | Assessment requires evaluating ALL 9 categories | Complete assessment of all 9 categories with evidence for each |\n| \"I see events, auditing category looks good\" | Events alone don't equal auditing maturity | Check logging comprehensiveness, testing, incident response processes |\n| \"Code looks simple, complexity is low\" | Visual simplicity masks composition complexity | Analyze cyclomatic complexity, dependency depth, state machine transitions |\n| \"Not a DeFi protocol, MEV category doesn't apply\" | MEV extends beyond DeFi (governance, NFTs, games) | Verify with transaction ordering analysis before declaring N\u002FA |\n| \"No assembly found, low-level category is N\u002FA\" | Low-level risks include external calls, delegatecall, inline assembly | Search for all low-level patterns before skipping category |\n| \"This is taking too long\" | Thorough assessment requires time per category | Complete all 9 categories, ask clarifying questions about off-chain processes |\n| \"I can rate this without evidence\" | Ratings without file:line references = unsubstantiated claims | Collect concrete code evidence for every category assessment |\n| \"User will know what to improve\" | Vague guidance = no action | Provide priority-ordered roadmap with specific improvements and effort estimates |\n\n---\n\n## Report Format\n\nFor detailed report structure and templates, see [REPORT_FORMAT.md](resources\u002FREPORT_FORMAT.md).\n\n### Structure:\n\n1. **Executive Summary**\n   - Project name and platform\n   - Overall maturity (average rating)\n   - Top 3 strengths\n   - Top 3 critical gaps\n   - Priority recommendations\n\n2. **Maturity Scorecard**\n   - Table with all 9 categories\n   - Ratings and scores\n   - Key findings notes\n\n3. **Detailed Analysis**\n   - Per-category breakdown\n   - Evidence with file:line references\n   - Gaps and improvement actions\n\n4. **Improvement Roadmap**\n   - CRITICAL (immediate)\n   - HIGH (1-2 months)\n   - MEDIUM (2-4 months)\n   - Effort estimates and impact\n\n---\n\n## Ready to Begin\n\n**Estimated Time**: 30-40 minutes\n\n**I'll need**:\n- Access to full codebase\n- Your knowledge of processes (monitoring, incident response, team practices)\n- Context about the project (DeFi, NFT, infrastructure, etc.)\n\nLet's assess this codebase!\n","# Code Maturity Assessor\n\n## Purpose\n\nSystematically assesses codebase maturity using Trail of Bits' 9-category framework. Provides evidence-based ratings and actionable recommendations.\n\n**Framework**: Building Secure Contracts - Code Maturity Evaluation v0.1.0\n\n---\n\n## How This Works\n\n### Phase 1: Discovery\nExplores the codebase to understand:\n- Project structure and platform\n- Contract\u002Fmodule files\n- Test coverage\n- Documentation availability\n\n### Phase 2: Analysis\nFor each of 9 categories, I'll:\n- **Search the code** for relevant patterns\n- **Read key files** to assess implementation\n- **Present findings** with file references\n- **Ask clarifying questions** about processes I can't see in code\n- **Determine rating** based on criteria\n\n### Phase 3: Report\nGenerates:\n- Executive summary\n- Maturity scorecard (ratings for all 9 categories)\n- Detailed analysis with evidence\n- Priority-ordered improvement roadmap\n\n---\n\n## Rating System\n\n- **Missing (0)**: Not present\u002Fnot implemented\n- **Weak (1)**: Several significant improvements needed\n- **Moderate (2)**: Adequate, can be improved\n- **Satisfactory (3)**: Above average, minor improvements\n- **Strong (4)**: Exceptional, only small improvements possible\n\n**Rating Logic**:\n- ANY \"Weak\" criteria → **Weak**\n- NO \"Weak\" + SOME \"Moderate\" unmet → **Moderate**\n- ALL \"Moderate\" + SOME \"Satisfactory\" met → **Satisfactory**\n- ALL \"Satisfactory\" + exceptional practices → **Strong**\n\n---\n\n## The 9 Categories\n\nI assess 9 comprehensive categories covering all aspects of code maturity. For detailed criteria, analysis approaches, and rating thresholds, see [ASSESSMENT_CRITERIA.md](resources\u002FASSESSMENT_CRITERIA.md).\n\n### Quick Reference:\n\n**1. ARITHMETIC**\n- Overflow protection mechanisms\n- Precision handling and rounding\n- Formula specifications\n- Edge case testing\n\n**2. AUDITING**\n- Event definitions and coverage\n- Monitoring infrastructure\n- Incident response planning\n\n**3. AUTHENTICATION \u002F ACCESS CONTROLS**\n- Privilege management\n- Role separation\n- Access control testing\n- Key compromise scenarios\n\n**4. COMPLEXITY MANAGEMENT**\n- Function scope and clarity\n- Cyclomatic complexity\n- Inheritance hierarchies\n- Code duplication\n\n**5. DECENTRALIZATION**\n- Centralization risks\n- Upgrade control mechanisms\n- User opt-out paths\n- Timelock\u002Fmultisig patterns\n\n**6. DOCUMENTATION**\n- Specifications and architecture\n- Inline code documentation\n- User stories\n- Domain glossaries\n\n**7. TRANSACTION ORDERING RISKS**\n- MEV vulnerabilities\n- Front-running protections\n- Slippage controls\n- Oracle security\n\n**8. LOW-LEVEL MANIPULATION**\n- Assembly usage\n- Unsafe code sections\n- Low-level calls\n- Justification and testing\n\n**9. TESTING & VERIFICATION**\n- Test coverage\n- Fuzzing and formal verification\n- CI\u002FCD integration\n- Test quality\n\nFor complete assessment criteria including what I'll analyze, what I'll ask you, and detailed rating thresholds (WEAK\u002FMODERATE\u002FSATISFACTORY\u002FSTRONG), see [ASSESSMENT_CRITERIA.md](resources\u002FASSESSMENT_CRITERIA.md).\n\n---\n\n## Example Output\n\nWhen the assessment is complete, you'll receive a comprehensive maturity report including:\n\n- **Executive Summary**: Overall score, top 3 strengths, top 3 gaps, priority recommendations\n- **Maturity Scorecard**: Table with all 9 categories rated with scores and notes\n- **Detailed Analysis**: Category-by-category breakdown with evidence (file:line references)\n- **Improvement Roadmap**: Priority-ordered recommendations (CRITICAL\u002FHIGH\u002FMEDIUM) with effort estimates\n\nFor a complete example assessment report, see [EXAMPLE_REPORT.md](resources\u002FEXAMPLE_REPORT.md).\n\n---\n\n## Assessment Process\n\nWhen invoked, I will:\n\n1. **Explore codebase**\n   - Find contract\u002Fmodule files\n   - Identify test files\n   - Locate documentation\n\n2. **Analyze each category**\n   - Search for relevant code patterns\n   - Read key implementations\n   - Assess against criteria\n   - Collect evidence\n\n3. **Interactive assessment**\n   - Present my findings with file references\n   - Ask about processes I can't see in code\n   - Discuss borderline cases\n   - Determine ratings together\n\n4. **Generate report**\n   - Executive summary\n   - Maturity scorecard table\n   - Detailed category analysis with evidence\n   - Priority-ordered improvement roadmap\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Found some findings, assessment complete\" | Assessment requires evaluating ALL 9 categories | Complete assessment of all 9 categories with evidence for each |\n| \"I see events, auditing category looks good\" | Events alone don't equal auditing maturity | Check logging comprehensiveness, testing, incident response processes |\n| \"Code looks simple, complexity is low\" | Visual simplicity masks composition complexity | Analyze cyclomatic complexity, dependency depth, state machine transitions |\n| \"Not a DeFi protocol, MEV category doesn't apply\" | MEV extends beyond DeFi (governance, NFTs, games) | Verify with transaction ordering analysis before declaring N\u002FA |\n| \"No assembly found, low-level category is N\u002FA\" | Low-level risks include external calls, delegatecall, inline assembly | Search for all low-level patterns before skipping category |\n| \"This is taking too long\" | Thorough assessment requires time per category | Complete all 9 categories, ask clarifying questions about off-chain processes |\n| \"I can rate this without evidence\" | Ratings without file:line references = unsubstantiated claims | Collect concrete code evidence for every category assessment |\n| \"User will know what to improve\" | Vague guidance = no action | Provide priority-ordered roadmap with specific improvements and effort estimates |\n\n---\n\n## Report Format\n\nFor detailed report structure and templates, see [REPORT_FORMAT.md](resources\u002FREPORT_FORMAT.md).\n\n### Structure:\n\n1. **Executive Summary**\n   - Project name and platform\n   - Overall maturity (average rating)\n   - Top 3 strengths\n   - Top 3 critical gaps\n   - Priority recommendations\n\n2. **Maturity Scorecard**\n   - Table with all 9 categories\n   - Ratings and scores\n   - Key findings notes\n\n3. **Detailed Analysis**\n   - Per-category breakdown\n   - Evidence with file:line references\n   - Gaps and improvement actions\n\n4. **Improvement Roadmap**\n   - CRITICAL (immediate)\n   - HIGH (1-2 months)\n   - MEDIUM (2-4 months)\n   - Effort estimates and impact\n\n---\n\n## Ready to Begin\n\n**Estimated Time**: 30-40 minutes\n\n**I'll need**:\n- Access to full codebase\n- Your knowledge of processes (monitoring, incident response, team practices)\n- Context about the project (DeFi, NFT, infrastructure, etc.)\n\nLet's assess this codebase!\n",{"name":5,"description":7},"main","aa4fc8e4a5441efccc61aca4e77753a2e9f88c8b","audits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun","https:\u002F\u002Fraffle-fun-lake.vercel.app","https:\u002F\u002Fgithub.com\u002FHeesho","2026-10-22 13:02:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Heesho\u002Fraffle-fun --skill code-maturity-assessor",{"tool":36,"command":37},"bunx","bunx skills add Heesho\u002Fraffle-fun --skill code-maturity-assessor",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Heesho\u002Fraffle-fun --skill code-maturity-assessor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor\u002FSKILL.md",true,[44,50,56,60,64],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",242,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Ftrail-of-bits-mark.svg","ASSET","资产文件",3084,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor\u002Fassets\u002Ftrail-of-bits-mark.svg",{"path":57,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":58,"sourceHtmlUrl":59},"resources\u002FASSESSMENT_CRITERIA.md",9876,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor\u002Fresources\u002FASSESSMENT_CRITERIA.md",{"path":61,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":62,"sourceHtmlUrl":63},"resources\u002FEXAMPLE_REPORT.md",7595,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor\u002Fresources\u002FEXAMPLE_REPORT.md",{"path":65,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":66,"sourceHtmlUrl":67},"resources\u002FREPORT_FORMAT.md",726,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcode-maturity-assessor\u002Fresources\u002FREPORT_FORMAT.md",[69,76,83,90,95,102],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M79XNCGXQ9R07VAPFB1H1WNF","spec-to-code-compliance","Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation against a whitepaper, protocol spec, or design document.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FOPENAI-TOB\u002Fattempt-02\u002FS5\u002Fresources\u002Fskills\u002Fspec-to-code-compliance\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M79XN7ADEZVW17912WC2CM7R","0xsimao-ai","Accounting-first smart contract security audit in the style of 0xSimao — maps the protocol's money model, then attacks it with 12 parallel lenses derived from his 869 published findings. Trigger on \"0xsimao ai\", \"0xsimao audit\", \"audit\", \"simao audit\", \"check this contract\", \"review for security\". Modes - default (full repo) or a specific filename.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FOPENAI-SIMAO\u002Fattempt-01\u002Fresources\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M79XN26B8ZCW79FATC4TSXA5","solidity-auditor","Security audit of Solidity code while you develop. Trigger on \"audit\", \"check this contract\", \"review for security\", \"loop mode\", \"run the auditor in loop mode\", \"run 3 passes\". Modes - default (full repo) or a specific filename. Loop mode runs several passes in one scan, each pass told what the earlier ones found, and ends in one combined report; it remembers findings between scans in a ledger.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FOPENAI-PASHOV\u002Fattempt-01\u002Fharness-reference\u002FSKILL.md",[],[],{"skillNo":91,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M79XMX0BKWJN0T8HZEBWTB6P","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fspec-to-code-compliance\u002F2.0.2\u002Fskills\u002Fspec-to-code-compliance\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M79XMM06CBG09CMZ5N8PGAZ1","entry-point-analyzer","Analyzes smart contract codebases to identify state-changing entry points for security auditing. Detects externally callable functions that modify state, categorizes them by access level (public, admin, role-restricted, contract-only), and generates structured audit reports. Excludes view\u002Fpure\u002Fread-only functions. Use when auditing smart contracts (Solidity, Vyper, Solana\u002FRust, Move, TON, CosmWasm) or when asked to find entry points, audit flows, external functions, access control patterns, or privileged operations.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fentry-point-analyzer\u002F1.0.4\u002Fskills\u002Fentry-point-analyzer\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M79XMCTG9288DZNAM1R3K2K2","ton-vulnerability-scanner","Scans TON (The Open Network) smart contracts for 3 critical vulnerabilities including integer-as-boolean misuse, fake Jetton contracts, and forward TON without gas checks. Use when auditing FunC contracts.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fton-vulnerability-scanner\u002FSKILL.md",[],[]]