[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BPHQY9RCEPTPW1CFHM3F8":3,"skill-same:01M79BPHQY9RCEPTPW1CFHM3F8":46},{"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":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79BPHQY9RCEPTPW1CFHM3F8","audit-reporting",null,"Structured finding format: severity, impact, PoC, remediation. Templates and classification standards for audit output. Used by Report Compiler.","sahil-kaushik1\u002FAuditing-Workflow","sahil-kaushik1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F143880923?v=4","01M79BEEK3947RQYD3WC00K9W3","Sahil Kaushik","01M79BEEKVHPFPTNBDB0GFXBHE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Faudit-reporting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: audit-reporting\ndescription: >\n  Structured finding format: severity, impact, PoC, remediation. Templates and\n  classification standards for audit output. Used by Report Compiler.\n---\n\n# Audit Reporting Skill\n\n## Purpose\n\nEnsure all audit outputs follow a consistent, auditor-grade format with proper severity\nclassification, concrete impact descriptions, and traceable evidence chains.\n\n## Severity Classification (Immunefi Standard)\n\n| Severity | Criteria |\n|----------|---------|\n| **Critical** | Direct loss of funds, permanent freezing of funds, protocol insolvency |\n| **High** | Theft of unclaimed yield, permanent DoS, governance manipulation |\n| **Medium** | Griefing with material loss, temporary DoS, value extraction below threshold |\n| **Low** | Non-critical issues, informational findings, gas optimizations |\n\n## Finding Report Structure\n\nEvery confirmed finding must include:\n\n1. **Title**: One-line description\n2. **Severity**: Critical\u002FHigh\u002FMedium\u002FLow with justification\n3. **Impact**: Concrete description (e.g., \"Attacker can drain 100% of vault TVL\")\n4. **Root Cause**: Specific code flaw with file and line reference\n5. **Attack Path**: Step-by-step, numbered sequence\n6. **PoC**: Link to runnable Foundry test\n7. **Affected Code**: File, lines, snippet\n8. **Remediation**: Specific fix with code example\n\n## Evidence Chain\n\nEvery finding must have a traceable path:\n\n```\nTask (specs\u002Ftasks\u002FTASK-{N}.md)\n  → Reasoning (specs\u002Freasoning\u002FTASK-{N}-reasoning.md)\n    → Verification (specs\u002Fverification\u002FTASK-{N}-verification.md)\n      → Finding (findings\u002FFINDING-{ID}.md)\n```\n\n## What Makes a Finding Actionable\n\n- ❌ \"There may be a reentrancy risk\" — NOT actionable\n- ✅ \"Reentrancy in Vault.withdraw() allows attacker to drain all ETH. PoC at test\u002Fexploit.t.sol\" — actionable\n\n## Coverage Reporting\n\nThe coverage map must honestly distinguish:\n- **Full coverage**: Function analyzed with multiple task approaches\n- **Partial coverage**: Function analyzed but not all paths\u002Fvalues tested\n- **No coverage**: Function not targeted by any task (must be in gap record)\n","# Audit Reporting Skill\n\n## Purpose\n\nEnsure all audit outputs follow a consistent, auditor-grade format with proper severity\nclassification, concrete impact descriptions, and traceable evidence chains.\n\n## Severity Classification (Immunefi Standard)\n\n| Severity | Criteria |\n|----------|---------|\n| **Critical** | Direct loss of funds, permanent freezing of funds, protocol insolvency |\n| **High** | Theft of unclaimed yield, permanent DoS, governance manipulation |\n| **Medium** | Griefing with material loss, temporary DoS, value extraction below threshold |\n| **Low** | Non-critical issues, informational findings, gas optimizations |\n\n## Finding Report Structure\n\nEvery confirmed finding must include:\n\n1. **Title**: One-line description\n2. **Severity**: Critical\u002FHigh\u002FMedium\u002FLow with justification\n3. **Impact**: Concrete description (e.g., \"Attacker can drain 100% of vault TVL\")\n4. **Root Cause**: Specific code flaw with file and line reference\n5. **Attack Path**: Step-by-step, numbered sequence\n6. **PoC**: Link to runnable Foundry test\n7. **Affected Code**: File, lines, snippet\n8. **Remediation**: Specific fix with code example\n\n## Evidence Chain\n\nEvery finding must have a traceable path:\n\n```\nTask (specs\u002Ftasks\u002FTASK-{N}.md)\n  → Reasoning (specs\u002Freasoning\u002FTASK-{N}-reasoning.md)\n    → Verification (specs\u002Fverification\u002FTASK-{N}-verification.md)\n      → Finding (findings\u002FFINDING-{ID}.md)\n```\n\n## What Makes a Finding Actionable\n\n- ❌ \"There may be a reentrancy risk\" — NOT actionable\n- ✅ \"Reentrancy in Vault.withdraw() allows attacker to drain all ETH. PoC at test\u002Fexploit.t.sol\" — actionable\n\n## Coverage Reporting\n\nThe coverage map must honestly distinguish:\n- **Full coverage**: Function analyzed with multiple task approaches\n- **Partial coverage**: Function analyzed but not all paths\u002Fvalues tested\n- **No coverage**: Function not targeted by any task (must be in gap record)\n",{"name":5,"description":7},"main","39a25d63191d67efe43cdce5b7507069e2307f0f",".gemini\u002Fskills\u002Faudit-reporting","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1","https:\u002F\u002Fdrive.google.com\u002Ffile\u002Fd\u002F1Te4TcrpgcN4j8DsYqVdjPl4QXVbs5XXo\u002Fview?usp=drive_link","Web3 security researcher \u002F developer","2026-10-18 15:17:21",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add sahil-kaushik1\u002FAuditing-Workflow --skill audit-reporting",{"tool":38,"command":39},"bunx","bunx skills add sahil-kaushik1\u002FAuditing-Workflow --skill audit-reporting",{"tool":41,"command":42},"pnpm","pnpm dlx skills add sahil-kaushik1\u002FAuditing-Workflow --skill audit-reporting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Faudit-reporting\u002FSKILL.md",true,[],[47,53,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79BSEAG0SS9CC2EN1S51K2X","stripe-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Frendertrust\u002F.claude\u002Fskills\u002Fstripe-patterns\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":6,"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},"01M79BSBAZXQBWCPKYJP38A35B","payment-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Fkeryk-ai\u002F.claude\u002Fskills\u002Fpayment-patterns\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},"01M79BS8PKZXFGBNQBS2GHNXZW","testing-patterns","Testing patterns for Jest and Playwright. Use when writing tests, setting up test fixtures, or validating RLS enforcement. Routes to existing test conventions.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftesting-patterns\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},"01M79BS3PR92A4QNEJAFNDKB2G","team-coordination","Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers team creation, messaging, shared task lists, and SAFe gate enforcement. Do NOT use for single-agent or simple subagent workflows.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fteam-coordination\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},"01M79BRZ422QD8D5QHQMXAVPWZ","task-compilation","Compile broad audit goals into structured proof obligations with 9 mandatory fields. Used after decomposition by the Threat Modeler agent.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftask-compilation\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},"01M79BRV2MK2AJZBNSE2BETP28","storage-layout-analysis","Proxy patterns, slot collisions, upgrade safety. Used during decomposition to identify storage-related vulnerabilities in upgradeable contracts.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fstorage-layout-analysis\u002FSKILL.md",[],[]]