[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BR1MCPD7W22D0X4YRR5KG":3,"skill-same:01M75BR1MCPD7W22D0X4YRR5KG":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75BR1MCPD7W22D0X4YRR5KG","audit-context-building",null,"Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Faudit-context-building\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: audit-context-building\ndescription: Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.\n---\n\n# Deep Context Builder Skill (Ultra-Granular Pure Context Mode)\n\n## 1. Purpose\n\nThis skill governs **how Claude thinks** during the context-building phase of an audit.\n\nWhen active, Claude will:\n- Perform **line-by-line \u002F block-by-block** code analysis by default.\n- Apply **First Principles**, **5 Whys**, and **5 Hows** at micro scale.\n- Continuously link insights → functions → modules → entire system.\n- Maintain a stable, explicit mental model that evolves with new evidence.\n- Identify invariants, assumptions, flows, and reasoning hazards.\n\nThis skill defines a structured analysis format (see Example: Function Micro-Analysis below) and runs **before** the vulnerability-hunting phase.\n\n---\n\n## 2. When to Use This Skill\n\nUse when:\n- Deep comprehension is needed before bug or vulnerability discovery.\n- You want bottom-up understanding instead of high-level guessing.\n- Reducing hallucinations, contradictions, and context loss is critical.\n- Preparing for security auditing, architecture review, or threat modeling.\n\nDo **not** use for:\n- Vulnerability findings\n- Fix recommendations\n- Exploit reasoning\n- Severity\u002Fimpact rating\n\n---\n\n## 3. How This Skill Behaves\n\nWhen active, Claude will:\n- Default to **ultra-granular analysis** of each block and line.\n- Apply micro-level First Principles, 5 Whys, and 5 Hows.\n- Build and refine a persistent global mental model.\n- Update earlier assumptions when contradicted (\"Earlier I thought X; now Y.\").\n- Periodically anchor summaries to maintain stable context.\n- Avoid speculation; express uncertainty explicitly when needed.\n\nGoal: **deep, accurate understanding**, not conclusions.\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"I get the gist\" | Gist-level understanding misses edge cases | Line-by-line analysis required |\n| \"This function is simple\" | Simple functions compose into complex bugs | Apply 5 Whys anyway |\n| \"I'll remember this invariant\" | You won't. Context degrades. | Write it down explicitly |\n| \"External call is probably fine\" | External = adversarial until proven otherwise | Jump into code or model as hostile |\n| \"I can skip this helper\" | Helpers contain assumptions that propagate | Trace the full call chain |\n| \"This is taking too long\" | Rushed context = hallucinated vulnerabilities later | Slow is fast |\n\n---\n\n## 4. Phase 1 — Initial Orientation (Bottom-Up Scan)\n\nBefore deep analysis, Claude performs a minimal mapping:\n\n1. Identify major modules\u002Ffiles\u002Fcontracts.\n2. Note obvious public\u002Fexternal entrypoints.\n3. Identify likely actors (users, owners, relayers, oracles, other contracts).\n4. Identify important storage variables, dicts, state structs, or cells.\n5. Build a preliminary structure without assuming behavior.\n\nThis establishes anchors for detailed analysis.\n\n---\n\n## 5. Phase 2 — Ultra-Granular Function Analysis (Default Mode)\n\nEvery non-trivial function receives full micro analysis.\n\n### 5.1 Per-Function Microstructure Checklist\n\nFor each function:\n\n1. **Purpose**\n   - Why the function exists and its role in the system.\n\n2. **Inputs & Assumptions**\n   - Parameters and implicit inputs (state, sender, env).\n   - Preconditions and constraints.\n\n3. **Outputs & Effects**\n   - Return values.\n   - State\u002Fstorage writes.\n   - Events\u002Fmessages.\n   - External interactions.\n\n4. **Block-by-Block \u002F Line-by-Line Analysis**\n   For each logical block:\n   - What it does.\n   - Why it appears here (ordering logic).\n   - What assumptions it relies on.\n   - What invariants it establishes or maintains.\n   - What later logic depends on it.\n\n   Apply per-block:\n   - **First Principles**\n   - **5 Whys**\n   - **5 Hows**\n\n---\n\n### 5.2 Cross-Function & External Flow Analysis\n*(Full Integration of Jump-Into-External-Code Rule)*\n\nWhen encountering calls, **continue the same micro-first analysis across boundaries.**\n\n#### Internal Calls\n- Jump into the callee immediately.\n- Perform block-by-block analysis of relevant code.\n- Track flow of data, assumptions, and invariants:\n  caller → callee → return → caller.\n- Note if callee logic behaves differently in this specific call context.\n\n#### External Calls — Two Cases\n\n**Case A — External Call to a Contract Whose Code Exists in the Codebase**\nTreat as an internal call:\n- Jump into the target contract\u002Ffunction.\n- Continue block-by-block micro-analysis.\n- Propagate invariants and assumptions seamlessly.\n- Consider edge cases based on the *actual* code, not a black-box guess.\n\n**Case B — External Call Without Available Code (True External \u002F Black Box)**\nAnalyze as adversarial:\n- Describe payload\u002Fvalue\u002Fgas or parameters sent.\n- Identify assumptions about the target.\n- Consider all outcomes:\n  - revert\n  - incorrect\u002Fstrange return values\n  - unexpected state changes\n  - misbehavior\n  - reentrancy (if applicable)\n\n#### Continuity Rule\nTreat the entire call chain as **one continuous execution flow**.\nNever reset context.\nAll invariants, assumptions, and data dependencies must propagate across calls.\n\n---\n\n### 5.3 Complete Analysis Example\n\nSee [FUNCTION_MICRO_ANALYSIS_EXAMPLE.md](resources\u002FFUNCTION_MICRO_ANALYSIS_EXAMPLE.md) for a complete walkthrough demonstrating:\n- Full micro-analysis of a DEX swap function\n- Application of First Principles, 5 Whys, and 5 Hows\n- Block-by-block analysis with invariants and assumptions\n- Cross-function dependency mapping\n- Risk analysis for external interactions\n\nThis example demonstrates the level of depth and structure required for all analyzed functions.\n\n---\n\n### 5.4 Output Requirements\n\nWhen performing ultra-granular analysis, Claude MUST structure output following the format defined in [OUTPUT_REQUIREMENTS.md](resources\u002FOUTPUT_REQUIREMENTS.md).\n\nKey requirements:\n- **Purpose** (2-3 sentences minimum)\n- **Inputs & Assumptions** (all parameters, preconditions, trust assumptions)\n- **Outputs & Effects** (returns, state writes, external calls, events, postconditions)\n- **Block-by-Block Analysis** (What, Why here, Assumptions, First Principles\u002F5 Whys\u002F5 Hows)\n- **Cross-Function Dependencies** (internal calls, external calls with risk analysis, shared state)\n\nQuality thresholds:\n- Minimum 3 invariants per function\n- Minimum 5 assumptions documented\n- Minimum 3 risk considerations for external interactions\n- At least 1 First Principles application\n- At least 3 combined 5 Whys\u002F5 Hows applications\n\n---\n\n### 5.5 Completeness Checklist\n\nBefore concluding micro-analysis of a function, verify against the [COMPLETENESS_CHECKLIST.md](resources\u002FCOMPLETENESS_CHECKLIST.md):\n\n- **Structural Completeness**: All required sections present (Purpose, Inputs, Outputs, Block-by-Block, Dependencies)\n- **Content Depth**: Minimum thresholds met (invariants, assumptions, risk analysis, First Principles)\n- **Continuity & Integration**: Cross-references, propagated assumptions, invariant couplings\n- **Anti-Hallucination**: Line number citations, no vague statements, evidence-based claims\n\nAnalysis is complete when all checklist items are satisfied and no unresolved \"unclear\" items remain.\n\n---\n\n## 6. Phase 3 — Global System Understanding\n\nAfter sufficient micro-analysis:\n\n1. **State & Invariant Reconstruction**\n   - Map reads\u002Fwrites of each state variable.\n   - Derive multi-function and multi-module invariants.\n\n2. **Workflow Reconstruction**\n   - Identify end-to-end flows (deposit, withdraw, lifecycle, upgrades).\n   - Track how state transforms across these flows.\n   - Record assumptions that persist across steps.\n\n3. **Trust Boundary Mapping**\n   - Actor → entrypoint → behavior.\n   - Identify untrusted input paths.\n   - Privilege changes and implicit role expectations.\n\n4. **Complexity & Fragility Clustering**\n   - Functions with many assumptions.\n   - High branching logic.\n   - Multi-step dependencies.\n   - Coupled state changes across modules.\n\nThese clusters help guide the vulnerability-hunting phase.\n\n---\n\n## 7. Stability & Consistency Rules\n*(Anti-Hallucination, Anti-Contradiction)*\n\nClaude must:\n\n- **Never reshape evidence to fit earlier assumptions.**\n  When contradicted:\n  - Update the model.\n  - State the correction explicitly.\n\n- **Periodically anchor key facts**\n  Summarize core:\n  - invariants\n  - state relationships\n  - actor roles\n  - workflows\n\n- **Avoid vague guesses**\n  Use:\n  - \"Unclear; need to inspect X.\"\n  instead of:\n  - \"It probably…\"\n\n- **Cross-reference constantly**\n  Connect new insights to previous state, flows, and invariants to maintain global coherence.\n\n---\n\n## 8. Subagent Usage\n\nClaude may spawn subagents for:\n- Dense or complex functions.\n- Long data-flow or control-flow chains.\n- Cryptographic \u002F mathematical logic.\n- Complex state machines.\n- Multi-module workflow reconstruction.\n\nUse the **`function-analyzer`** agent for per-function deep analysis.\nIt follows the full microstructure checklist, cross-function flow\nrules, and quality thresholds defined in this skill, and enforces\nthe pure-context-building constraint.\n\nSubagents must:\n- Follow the same micro-first rules.\n- Return summaries that Claude integrates into its global model.\n\n---\n\n## 9. Relationship to Other Phases\n\nThis skill runs **before**:\n- Vulnerability discovery\n- Classification \u002F triage\n- Report writing\n- Impact modeling\n- Exploit reasoning\n\nIt exists solely to build:\n- Deep understanding\n- Stable context\n- System-level clarity\n\n---\n\n## 10. Non-Goals\n\nWhile active, Claude should NOT:\n- Identify vulnerabilities\n- Propose fixes\n- Generate proofs-of-concept\n- Model exploits\n- Assign severity or impact\n\nThis is **pure context building** only.\n","# Deep Context Builder Skill (Ultra-Granular Pure Context Mode)\n\n## 1. Purpose\n\nThis skill governs **how Claude thinks** during the context-building phase of an audit.\n\nWhen active, Claude will:\n- Perform **line-by-line \u002F block-by-block** code analysis by default.\n- Apply **First Principles**, **5 Whys**, and **5 Hows** at micro scale.\n- Continuously link insights → functions → modules → entire system.\n- Maintain a stable, explicit mental model that evolves with new evidence.\n- Identify invariants, assumptions, flows, and reasoning hazards.\n\nThis skill defines a structured analysis format (see Example: Function Micro-Analysis below) and runs **before** the vulnerability-hunting phase.\n\n---\n\n## 2. When to Use This Skill\n\nUse when:\n- Deep comprehension is needed before bug or vulnerability discovery.\n- You want bottom-up understanding instead of high-level guessing.\n- Reducing hallucinations, contradictions, and context loss is critical.\n- Preparing for security auditing, architecture review, or threat modeling.\n\nDo **not** use for:\n- Vulnerability findings\n- Fix recommendations\n- Exploit reasoning\n- Severity\u002Fimpact rating\n\n---\n\n## 3. How This Skill Behaves\n\nWhen active, Claude will:\n- Default to **ultra-granular analysis** of each block and line.\n- Apply micro-level First Principles, 5 Whys, and 5 Hows.\n- Build and refine a persistent global mental model.\n- Update earlier assumptions when contradicted (\"Earlier I thought X; now Y.\").\n- Periodically anchor summaries to maintain stable context.\n- Avoid speculation; express uncertainty explicitly when needed.\n\nGoal: **deep, accurate understanding**, not conclusions.\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"I get the gist\" | Gist-level understanding misses edge cases | Line-by-line analysis required |\n| \"This function is simple\" | Simple functions compose into complex bugs | Apply 5 Whys anyway |\n| \"I'll remember this invariant\" | You won't. Context degrades. | Write it down explicitly |\n| \"External call is probably fine\" | External = adversarial until proven otherwise | Jump into code or model as hostile |\n| \"I can skip this helper\" | Helpers contain assumptions that propagate | Trace the full call chain |\n| \"This is taking too long\" | Rushed context = hallucinated vulnerabilities later | Slow is fast |\n\n---\n\n## 4. Phase 1 — Initial Orientation (Bottom-Up Scan)\n\nBefore deep analysis, Claude performs a minimal mapping:\n\n1. Identify major modules\u002Ffiles\u002Fcontracts.\n2. Note obvious public\u002Fexternal entrypoints.\n3. Identify likely actors (users, owners, relayers, oracles, other contracts).\n4. Identify important storage variables, dicts, state structs, or cells.\n5. Build a preliminary structure without assuming behavior.\n\nThis establishes anchors for detailed analysis.\n\n---\n\n## 5. Phase 2 — Ultra-Granular Function Analysis (Default Mode)\n\nEvery non-trivial function receives full micro analysis.\n\n### 5.1 Per-Function Microstructure Checklist\n\nFor each function:\n\n1. **Purpose**\n   - Why the function exists and its role in the system.\n\n2. **Inputs & Assumptions**\n   - Parameters and implicit inputs (state, sender, env).\n   - Preconditions and constraints.\n\n3. **Outputs & Effects**\n   - Return values.\n   - State\u002Fstorage writes.\n   - Events\u002Fmessages.\n   - External interactions.\n\n4. **Block-by-Block \u002F Line-by-Line Analysis**\n   For each logical block:\n   - What it does.\n   - Why it appears here (ordering logic).\n   - What assumptions it relies on.\n   - What invariants it establishes or maintains.\n   - What later logic depends on it.\n\n   Apply per-block:\n   - **First Principles**\n   - **5 Whys**\n   - **5 Hows**\n\n---\n\n### 5.2 Cross-Function & External Flow Analysis\n*(Full Integration of Jump-Into-External-Code Rule)*\n\nWhen encountering calls, **continue the same micro-first analysis across boundaries.**\n\n#### Internal Calls\n- Jump into the callee immediately.\n- Perform block-by-block analysis of relevant code.\n- Track flow of data, assumptions, and invariants:\n  caller → callee → return → caller.\n- Note if callee logic behaves differently in this specific call context.\n\n#### External Calls — Two Cases\n\n**Case A — External Call to a Contract Whose Code Exists in the Codebase**\nTreat as an internal call:\n- Jump into the target contract\u002Ffunction.\n- Continue block-by-block micro-analysis.\n- Propagate invariants and assumptions seamlessly.\n- Consider edge cases based on the *actual* code, not a black-box guess.\n\n**Case B — External Call Without Available Code (True External \u002F Black Box)**\nAnalyze as adversarial:\n- Describe payload\u002Fvalue\u002Fgas or parameters sent.\n- Identify assumptions about the target.\n- Consider all outcomes:\n  - revert\n  - incorrect\u002Fstrange return values\n  - unexpected state changes\n  - misbehavior\n  - reentrancy (if applicable)\n\n#### Continuity Rule\nTreat the entire call chain as **one continuous execution flow**.\nNever reset context.\nAll invariants, assumptions, and data dependencies must propagate across calls.\n\n---\n\n### 5.3 Complete Analysis Example\n\nSee [FUNCTION_MICRO_ANALYSIS_EXAMPLE.md](resources\u002FFUNCTION_MICRO_ANALYSIS_EXAMPLE.md) for a complete walkthrough demonstrating:\n- Full micro-analysis of a DEX swap function\n- Application of First Principles, 5 Whys, and 5 Hows\n- Block-by-block analysis with invariants and assumptions\n- Cross-function dependency mapping\n- Risk analysis for external interactions\n\nThis example demonstrates the level of depth and structure required for all analyzed functions.\n\n---\n\n### 5.4 Output Requirements\n\nWhen performing ultra-granular analysis, Claude MUST structure output following the format defined in [OUTPUT_REQUIREMENTS.md](resources\u002FOUTPUT_REQUIREMENTS.md).\n\nKey requirements:\n- **Purpose** (2-3 sentences minimum)\n- **Inputs & Assumptions** (all parameters, preconditions, trust assumptions)\n- **Outputs & Effects** (returns, state writes, external calls, events, postconditions)\n- **Block-by-Block Analysis** (What, Why here, Assumptions, First Principles\u002F5 Whys\u002F5 Hows)\n- **Cross-Function Dependencies** (internal calls, external calls with risk analysis, shared state)\n\nQuality thresholds:\n- Minimum 3 invariants per function\n- Minimum 5 assumptions documented\n- Minimum 3 risk considerations for external interactions\n- At least 1 First Principles application\n- At least 3 combined 5 Whys\u002F5 Hows applications\n\n---\n\n### 5.5 Completeness Checklist\n\nBefore concluding micro-analysis of a function, verify against the [COMPLETENESS_CHECKLIST.md](resources\u002FCOMPLETENESS_CHECKLIST.md):\n\n- **Structural Completeness**: All required sections present (Purpose, Inputs, Outputs, Block-by-Block, Dependencies)\n- **Content Depth**: Minimum thresholds met (invariants, assumptions, risk analysis, First Principles)\n- **Continuity & Integration**: Cross-references, propagated assumptions, invariant couplings\n- **Anti-Hallucination**: Line number citations, no vague statements, evidence-based claims\n\nAnalysis is complete when all checklist items are satisfied and no unresolved \"unclear\" items remain.\n\n---\n\n## 6. Phase 3 — Global System Understanding\n\nAfter sufficient micro-analysis:\n\n1. **State & Invariant Reconstruction**\n   - Map reads\u002Fwrites of each state variable.\n   - Derive multi-function and multi-module invariants.\n\n2. **Workflow Reconstruction**\n   - Identify end-to-end flows (deposit, withdraw, lifecycle, upgrades).\n   - Track how state transforms across these flows.\n   - Record assumptions that persist across steps.\n\n3. **Trust Boundary Mapping**\n   - Actor → entrypoint → behavior.\n   - Identify untrusted input paths.\n   - Privilege changes and implicit role expectations.\n\n4. **Complexity & Fragility Clustering**\n   - Functions with many assumptions.\n   - High branching logic.\n   - Multi-step dependencies.\n   - Coupled state changes across modules.\n\nThese clusters help guide the vulnerability-hunting phase.\n\n---\n\n## 7. Stability & Consistency Rules\n*(Anti-Hallucination, Anti-Contradiction)*\n\nClaude must:\n\n- **Never reshape evidence to fit earlier assumptions.**\n  When contradicted:\n  - Update the model.\n  - State the correction explicitly.\n\n- **Periodically anchor key facts**\n  Summarize core:\n  - invariants\n  - state relationships\n  - actor roles\n  - workflows\n\n- **Avoid vague guesses**\n  Use:\n  - \"Unclear; need to inspect X.\"\n  instead of:\n  - \"It probably…\"\n\n- **Cross-reference constantly**\n  Connect new insights to previous state, flows, and invariants to maintain global coherence.\n\n---\n\n## 8. Subagent Usage\n\nClaude may spawn subagents for:\n- Dense or complex functions.\n- Long data-flow or control-flow chains.\n- Cryptographic \u002F mathematical logic.\n- Complex state machines.\n- Multi-module workflow reconstruction.\n\nUse the **`function-analyzer`** agent for per-function deep analysis.\nIt follows the full microstructure checklist, cross-function flow\nrules, and quality thresholds defined in this skill, and enforces\nthe pure-context-building constraint.\n\nSubagents must:\n- Follow the same micro-first rules.\n- Return summaries that Claude integrates into its global model.\n\n---\n\n## 9. Relationship to Other Phases\n\nThis skill runs **before**:\n- Vulnerability discovery\n- Classification \u002F triage\n- Report writing\n- Impact modeling\n- Exploit reasoning\n\nIt exists solely to build:\n- Deep understanding\n- Stable context\n- System-level clarity\n\n---\n\n## 10. Non-Goals\n\nWhile active, Claude should NOT:\n- Identify vulnerabilities\n- Propose fixes\n- Generate proofs-of-concept\n- Model exploits\n- Assign severity or impact\n\nThis is **pure context building** only.\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Faudit-context-building",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill audit-context-building",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill audit-context-building",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill audit-context-building","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Faudit-context-building\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"resources\u002FCOMPLETENESS_CHECKLIST.md","REFERENCE","参考文档",1880,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Faudit-context-building\u002Fresources\u002FCOMPLETENESS_CHECKLIST.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"resources\u002FFUNCTION_MICRO_ANALYSIS_EXAMPLE.md",18173,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Faudit-context-building\u002Fresources\u002FFUNCTION_MICRO_ANALYSIS_EXAMPLE.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"resources\u002FOUTPUT_REQUIREMENTS.md",2449,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Faudit-context-building\u002Fresources\u002FOUTPUT_REQUIREMENTS.md",[61,68,75,84,91,98],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]