[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BPQ2M0XZ5750CCACT5CBK":3,"skill-same:01M79BPQ2M0XZ5750CCACT5CBK":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},"01M79BPQ2M0XZ5750CCACT5CBK","context-isolation",null,"Enforce that untriggered knowledge is not loaded and irrelevant context is excluded. Three types: trigger, responsibility, and per-task isolation.","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\u002Fcontext-isolation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: context-isolation\ndescription: >\n  Enforce that untriggered knowledge is not loaded and irrelevant context\n  is excluded. Three types: trigger, responsibility, and per-task isolation.\n---\n\n# Context Isolation Skill\n\n## Purpose\n\n> \"If it is not triggered, do not read it. If it is irrelevant, do not place it in\n> the current context.\"\n\nSplitting prompts into files is NOT real isolation if the agent still reads all of them.\nThis skill enforces actual isolation at three levels.\n\n## Three Isolation Types\n\n### 1. Trigger Isolation\nSkills are loaded ONLY when their trigger condition is met.\n\n| Skill | Trigger | When NOT to load |\n|-------|---------|-----------------|\n| `foundry-harness` | During verification | During decomposition |\n| `defi-patterns` | During threat modeling | During verification |\n| `drift-detection` | During reasoning | During decomposition |\n\n**Rule**: If a skill's trigger condition is not met, the agent MUST NOT read it.\n\n### 2. Responsibility Isolation\nEach agent sees ONLY its role-relevant artifacts.\n\n| Agent | Can See | Cannot See |\n|-------|---------|------------|\n| Deep Reasoner | Task file, context package, target code | Verifier's prior conclusions, other tasks' reasoning |\n| Verifier | Task file, reasoner's CLAIM only (not chain-of-thought), target code | Reasoner's internal reasoning process |\n| Judge | Both reasoner and verifier outputs | Nothing restricted |\n| Decomposer | Source code, SAST facts | Previous audit findings (anchoring bias) |\n\n**Rule**: Agents MUST NOT consume artifacts outside their responsibility boundary.\n\n### 3. Context Isolation (Per-Task)\nThe Context Builder provides ONLY task-relevant context.\n\nFor a task targeting `Vault.withdraw()`:\n- ✅ Include: Vault.sol, imported interfaces, ERC20 token contract\n- ✅ Include: State variables listed in the task's \"Relevant State\"\n- ❌ Exclude: Governance.sol (unless the task specifically involves governance)\n- ❌ Exclude: Frontend deployment config\n- ❌ Exclude: Test files from previous audits\n\n**Rule**: Context packages MUST document what was excluded and why.\n\n## Enforcement\n\nThe Context Builder agent is responsible for building isolation-compliant context\npackages. The Judge checks that reasoning outputs don't reference excluded context\n(which would indicate an isolation violation).\n\n## Why This Matters\n\nWithout real isolation:\n- One huge prompt becomes several smaller prompt fragments (same problem)\n- Irrelevant context dilutes attention on the actual task\n- Anchoring bias from previous findings prevents fresh analysis\n- Context overload causes the model to take shortcuts (vulnerability drift)\n","# Context Isolation Skill\n\n## Purpose\n\n> \"If it is not triggered, do not read it. If it is irrelevant, do not place it in\n> the current context.\"\n\nSplitting prompts into files is NOT real isolation if the agent still reads all of them.\nThis skill enforces actual isolation at three levels.\n\n## Three Isolation Types\n\n### 1. Trigger Isolation\nSkills are loaded ONLY when their trigger condition is met.\n\n| Skill | Trigger | When NOT to load |\n|-------|---------|-----------------|\n| `foundry-harness` | During verification | During decomposition |\n| `defi-patterns` | During threat modeling | During verification |\n| `drift-detection` | During reasoning | During decomposition |\n\n**Rule**: If a skill's trigger condition is not met, the agent MUST NOT read it.\n\n### 2. Responsibility Isolation\nEach agent sees ONLY its role-relevant artifacts.\n\n| Agent | Can See | Cannot See |\n|-------|---------|------------|\n| Deep Reasoner | Task file, context package, target code | Verifier's prior conclusions, other tasks' reasoning |\n| Verifier | Task file, reasoner's CLAIM only (not chain-of-thought), target code | Reasoner's internal reasoning process |\n| Judge | Both reasoner and verifier outputs | Nothing restricted |\n| Decomposer | Source code, SAST facts | Previous audit findings (anchoring bias) |\n\n**Rule**: Agents MUST NOT consume artifacts outside their responsibility boundary.\n\n### 3. Context Isolation (Per-Task)\nThe Context Builder provides ONLY task-relevant context.\n\nFor a task targeting `Vault.withdraw()`:\n- ✅ Include: Vault.sol, imported interfaces, ERC20 token contract\n- ✅ Include: State variables listed in the task's \"Relevant State\"\n- ❌ Exclude: Governance.sol (unless the task specifically involves governance)\n- ❌ Exclude: Frontend deployment config\n- ❌ Exclude: Test files from previous audits\n\n**Rule**: Context packages MUST document what was excluded and why.\n\n## Enforcement\n\nThe Context Builder agent is responsible for building isolation-compliant context\npackages. The Judge checks that reasoning outputs don't reference excluded context\n(which would indicate an isolation violation).\n\n## Why This Matters\n\nWithout real isolation:\n- One huge prompt becomes several smaller prompt fragments (same problem)\n- Irrelevant context dilutes attention on the actual task\n- Anchoring bias from previous findings prevents fresh analysis\n- Context overload causes the model to take shortcuts (vulnerability drift)\n",{"name":5,"description":7},"main","39a25d63191d67efe43cdce5b7507069e2307f0f",".gemini\u002Fskills\u002Fcontext-isolation","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 context-isolation",{"tool":38,"command":39},"bunx","bunx skills add sahil-kaushik1\u002FAuditing-Workflow --skill context-isolation",{"tool":41,"command":42},"pnpm","pnpm dlx skills add sahil-kaushik1\u002FAuditing-Workflow --skill context-isolation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fcontext-isolation\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",[],[]]