[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJ0PSZKZJ88K7NJEJYPRSW":3,"skill-same:01M7EJ0PSZKZJ88K7NJEJYPRSW":81},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7EJ0PSZKZJ88K7NJEJYPRSW","entry-point-analyzer",null,"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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: entry-point-analyzer\ndescription: 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.\nallowed-tools: Read Grep Glob Bash\n---\n\n# Entry Point Analyzer\n\nSystematically identify all **state-changing** entry points in a smart contract codebase to guide security audits.\n\n## When to Use\n\nUse this skill when:\n- Starting a smart contract security audit to map the attack surface\n- Asked to find entry points, external functions, or audit flows\n- Analyzing access control patterns across a codebase\n- Identifying privileged operations and role-restricted functions\n- Building an understanding of which functions can modify contract state\n\n## When NOT to Use\n\nDo NOT use this skill for:\n- Vulnerability detection (use audit-context-building or domain-specific-audits)\n- Writing exploit POCs (use solidity-poc-builder)\n- Code quality or gas optimization analysis\n- Non-smart-contract codebases\n- Analyzing read-only functions (this skill excludes them)\n\n## Scope: State-Changing Functions Only\n\nThis skill focuses exclusively on functions that can modify state. **Excluded:**\n\n| Language | Excluded Patterns |\n|----------|-------------------|\n| Solidity | `view`, `pure` functions |\n| Vyper | `@view`, `@pure` functions |\n| Solana | Functions without `mut` account references |\n| Move | Non-entry `public fun` (module-callable only) |\n| TON | `get` methods (FunC), read-only receivers (Tact) |\n| CosmWasm | `query` entry point and its handlers |\n\n**Why exclude read-only functions?** They cannot directly cause loss of funds or state corruption. While they may leak information, the primary audit focus is on functions that can change state.\n\n## Workflow\n\n1. **Detect Language** - Identify contract language(s) from file extensions and syntax\n2. **Use Tooling (if available)** - For Solidity, check if Slither is available and use it\n3. **Locate Contracts** - Find all contract\u002Fmodule files (apply directory filter if specified)\n4. **Extract Entry Points** - Parse each file for externally callable, state-changing functions\n5. **Classify Access** - Categorize each function by access level\n6. **Generate Report** - Output structured markdown report\n\n## Slither Integration (Solidity)\n\nFor Solidity codebases, Slither can automatically extract entry points. Before manual analysis:\n\n### 1. Check if Slither is Available\n\n```bash\nwhich slither\n```\n\n### 2. If Slither is Detected, Run Entry Points Printer\n\n```bash\nslither . --print entry-points\n```\n\nThis outputs a table of all state-changing entry points with:\n- Contract name\n- Function name\n- Visibility\n- Modifiers applied\n\n### 3. Use Slither Output as Foundation\n\n- Parse the Slither output table to populate your analysis\n- Cross-reference with manual inspection for access control classification\n- Slither may miss some patterns (callbacks, dynamic access control)—supplement with manual review\n- If Slither fails (compilation errors, unsupported features), fall back to manual analysis\n\n### 4. When Slither is NOT Available\n\nIf `which slither` returns nothing, proceed with manual analysis using the language-specific reference files.\n\n## Language Detection\n\n| Extension | Language | Reference |\n|-----------|----------|-----------|\n| `.sol` | Solidity | [{baseDir}\u002Freferences\u002Fsolidity.md]({baseDir}\u002Freferences\u002Fsolidity.md) |\n| `.vy` | Vyper | [{baseDir}\u002Freferences\u002Fvyper.md]({baseDir}\u002Freferences\u002Fvyper.md) |\n| `.rs` + `Cargo.toml` with `solana-program` | Solana (Rust) | [{baseDir}\u002Freferences\u002Fsolana.md]({baseDir}\u002Freferences\u002Fsolana.md) |\n| `.move` + `Move.toml` with `edition` | [{baseDir}\u002Freferences\u002Fmove-sui.md]({baseDir}\u002Freferences\u002Fmove-sui.md) |\n| `.move` + `Move.toml` with `Aptos` | [{baseDir}\u002Freferences\u002Fmove-aptos.md]({baseDir}\u002Freferences\u002Fmove-aptos.md) |\n| `.fc`, `.func`, `.tact` | TON (FunC\u002FTact) | [{baseDir}\u002Freferences\u002Fton.md]({baseDir}\u002Freferences\u002Fton.md) |\n| `.rs` + `Cargo.toml` with `cosmwasm-std` | CosmWasm | [{baseDir}\u002Freferences\u002Fcosmwasm.md]({baseDir}\u002Freferences\u002Fcosmwasm.md) |\n\nLoad the appropriate reference file(s) based on detected language before analysis.\n\n## Access Classification\n\nClassify each state-changing entry point into one of these categories:\n\n### 1. Public (Unrestricted)\nFunctions callable by anyone without restrictions.\n\n### 2. Role-Restricted\nFunctions limited to specific roles. Common patterns to detect:\n- Explicit role names: `admin`, `owner`, `governance`, `guardian`, `operator`, `manager`, `minter`, `pauser`, `keeper`, `relayer`, `lender`, `borrower`\n- Role-checking patterns: `onlyRole`, `hasRole`, `require(msg.sender == X)`, `assert_owner`, `#[access_control]`\n- When role is ambiguous, flag as **\"Restricted (review required)\"** with the restriction pattern noted\n\n### 3. Contract-Only (Internal Integration Points)\nFunctions callable only by other contracts, not by EOAs. Indicators:\n- Callbacks: `onERC721Received`, `uniswapV3SwapCallback`, `flashLoanCallback`\n- Interface implementations with contract-caller checks\n- Functions that revert if `tx.origin == msg.sender`\n- Cross-contract hooks\n\n## Output Format\n\nGenerate a markdown report with this structure:\n\n```markdown\n# Entry Point Analysis: [Project Name]\n\n**Analyzed**: [timestamp]\n**Scope**: [directories analyzed or \"full codebase\"]\n**Languages**: [detected languages]\n**Focus**: State-changing functions only (view\u002Fpure excluded)\n\n## Summary\n\n| Category | Count |\n|----------|-------|\n| Public (Unrestricted) | X |\n| Role-Restricted | X |\n| Restricted (Review Required) | X |\n| Contract-Only | X |\n| **Total** | **X** |\n\n---\n\n## Public Entry Points (Unrestricted)\n\nState-changing functions callable by anyone—prioritize for attack surface analysis.\n\n| Function | File | Notes |\n|----------|------|-------|\n| `functionName(params)` | `path\u002Fto\u002Ffile.sol:L42` | Brief note if relevant |\n\n---\n\n## Role-Restricted Entry Points\n\n### Admin \u002F Owner\n| Function | File | Restriction |\n|----------|------|-------------|\n| `setFee(uint256)` | `Config.sol:L15` | `onlyOwner` |\n\n### Governance\n| Function | File | Restriction |\n|----------|------|-------------|\n\n### Guardian \u002F Pauser\n| Function | File | Restriction |\n|----------|------|-------------|\n\n### Other Roles\n| Function | File | Restriction | Role |\n|----------|------|-------------|------|\n\n---\n\n## Restricted (Review Required)\n\nFunctions with access control patterns that need manual verification.\n\n| Function | File | Pattern | Why Review |\n|----------|------|---------|------------|\n| `execute(bytes)` | `Executor.sol:L88` | `require(trusted[msg.sender])` | Dynamic trust list |\n\n---\n\n## Contract-Only (Internal Integration Points)\n\nFunctions only callable by other contracts—useful for understanding trust boundaries.\n\n| Function | File | Expected Caller |\n|----------|------|-----------------|\n| `onFlashLoan(...)` | `Vault.sol:L200` | Flash loan provider |\n\n---\n\n## Files Analyzed\n\n- `path\u002Fto\u002Ffile1.sol` (X state-changing entry points)\n- `path\u002Fto\u002Ffile2.sol` (X state-changing entry points)\n```\n\n## Filtering\n\nWhen user specifies a directory filter:\n- Only analyze files within that path\n- Note the filter in the report header\n- Example: \"Analyze only `src\u002Fcore\u002F`\" → scope = `src\u002Fcore\u002F`\n\n## Analysis Guidelines\n\n1. **Be thorough**: Don't skip files. Every state-changing externally callable function matters.\n2. **Be conservative**: When uncertain about access level, flag for review rather than miscategorize.\n3. **Skip read-only**: Exclude `view`, `pure`, and equivalent read-only functions.\n4. **Note inheritance**: If a function's access control comes from a parent contract, note this.\n5. **Track modifiers**: List all access-related modifiers\u002Fdecorators applied to each function.\n6. **Identify patterns**: Look for common patterns like:\n   - Initializer functions (often unrestricted on first call)\n   - Upgrade functions (high-privilege)\n   - Emergency\u002Fpause functions (guardian-level)\n   - Fee\u002Fparameter setters (admin-level)\n   - Token transfers and approvals (often public)\n\n## Common Role Patterns by Protocol Type\n\n| Protocol Type | Common Roles |\n|---------------|--------------|\n| DEX | `owner`, `feeManager`, `pairCreator` |\n| Lending | `admin`, `guardian`, `liquidator`, `oracle` |\n| Governance | `proposer`, `executor`, `canceller`, `timelock` |\n| NFT | `minter`, `admin`, `royaltyReceiver` |\n| Bridge | `relayer`, `guardian`, `validator`, `operator` |\n| Vault\u002FYield | `strategist`, `keeper`, `harvester`, `manager` |\n\n## Rationalizations to Reject\n\nWhen analyzing entry points, reject these shortcuts:\n- \"This function looks standard\" → Still classify it; standard functions can have non-standard access control\n- \"The modifier name is clear\" → Verify the modifier's actual implementation\n- \"This is obviously admin-only\" → Trace the actual restriction; \"obvious\" assumptions miss subtle bypasses\n- \"I'll skip the callbacks\" → Callbacks define trust boundaries; always include them\n- \"It doesn't modify much state\" → Any state change can be exploited; include all non-view functions\n\n## Error Handling\n\nIf a file cannot be parsed:\n1. Note it in the report under \"Analysis Warnings\"\n2. Continue with remaining files\n3. Suggest manual review for unparsable files\n","# Entry Point Analyzer\n\nSystematically identify all **state-changing** entry points in a smart contract codebase to guide security audits.\n\n## When to Use\n\nUse this skill when:\n- Starting a smart contract security audit to map the attack surface\n- Asked to find entry points, external functions, or audit flows\n- Analyzing access control patterns across a codebase\n- Identifying privileged operations and role-restricted functions\n- Building an understanding of which functions can modify contract state\n\n## When NOT to Use\n\nDo NOT use this skill for:\n- Vulnerability detection (use audit-context-building or domain-specific-audits)\n- Writing exploit POCs (use solidity-poc-builder)\n- Code quality or gas optimization analysis\n- Non-smart-contract codebases\n- Analyzing read-only functions (this skill excludes them)\n\n## Scope: State-Changing Functions Only\n\nThis skill focuses exclusively on functions that can modify state. **Excluded:**\n\n| Language | Excluded Patterns |\n|----------|-------------------|\n| Solidity | `view`, `pure` functions |\n| Vyper | `@view`, `@pure` functions |\n| Solana | Functions without `mut` account references |\n| Move | Non-entry `public fun` (module-callable only) |\n| TON | `get` methods (FunC), read-only receivers (Tact) |\n| CosmWasm | `query` entry point and its handlers |\n\n**Why exclude read-only functions?** They cannot directly cause loss of funds or state corruption. While they may leak information, the primary audit focus is on functions that can change state.\n\n## Workflow\n\n1. **Detect Language** - Identify contract language(s) from file extensions and syntax\n2. **Use Tooling (if available)** - For Solidity, check if Slither is available and use it\n3. **Locate Contracts** - Find all contract\u002Fmodule files (apply directory filter if specified)\n4. **Extract Entry Points** - Parse each file for externally callable, state-changing functions\n5. **Classify Access** - Categorize each function by access level\n6. **Generate Report** - Output structured markdown report\n\n## Slither Integration (Solidity)\n\nFor Solidity codebases, Slither can automatically extract entry points. Before manual analysis:\n\n### 1. Check if Slither is Available\n\n```bash\nwhich slither\n```\n\n### 2. If Slither is Detected, Run Entry Points Printer\n\n```bash\nslither . --print entry-points\n```\n\nThis outputs a table of all state-changing entry points with:\n- Contract name\n- Function name\n- Visibility\n- Modifiers applied\n\n### 3. Use Slither Output as Foundation\n\n- Parse the Slither output table to populate your analysis\n- Cross-reference with manual inspection for access control classification\n- Slither may miss some patterns (callbacks, dynamic access control)—supplement with manual review\n- If Slither fails (compilation errors, unsupported features), fall back to manual analysis\n\n### 4. When Slither is NOT Available\n\nIf `which slither` returns nothing, proceed with manual analysis using the language-specific reference files.\n\n## Language Detection\n\n| Extension | Language | Reference |\n|-----------|----------|-----------|\n| `.sol` | Solidity | [{baseDir}\u002Freferences\u002Fsolidity.md]({baseDir}\u002Freferences\u002Fsolidity.md) |\n| `.vy` | Vyper | [{baseDir}\u002Freferences\u002Fvyper.md]({baseDir}\u002Freferences\u002Fvyper.md) |\n| `.rs` + `Cargo.toml` with `solana-program` | Solana (Rust) | [{baseDir}\u002Freferences\u002Fsolana.md]({baseDir}\u002Freferences\u002Fsolana.md) |\n| `.move` + `Move.toml` with `edition` | [{baseDir}\u002Freferences\u002Fmove-sui.md]({baseDir}\u002Freferences\u002Fmove-sui.md) |\n| `.move` + `Move.toml` with `Aptos` | [{baseDir}\u002Freferences\u002Fmove-aptos.md]({baseDir}\u002Freferences\u002Fmove-aptos.md) |\n| `.fc`, `.func`, `.tact` | TON (FunC\u002FTact) | [{baseDir}\u002Freferences\u002Fton.md]({baseDir}\u002Freferences\u002Fton.md) |\n| `.rs` + `Cargo.toml` with `cosmwasm-std` | CosmWasm | [{baseDir}\u002Freferences\u002Fcosmwasm.md]({baseDir}\u002Freferences\u002Fcosmwasm.md) |\n\nLoad the appropriate reference file(s) based on detected language before analysis.\n\n## Access Classification\n\nClassify each state-changing entry point into one of these categories:\n\n### 1. Public (Unrestricted)\nFunctions callable by anyone without restrictions.\n\n### 2. Role-Restricted\nFunctions limited to specific roles. Common patterns to detect:\n- Explicit role names: `admin`, `owner`, `governance`, `guardian`, `operator`, `manager`, `minter`, `pauser`, `keeper`, `relayer`, `lender`, `borrower`\n- Role-checking patterns: `onlyRole`, `hasRole`, `require(msg.sender == X)`, `assert_owner`, `#[access_control]`\n- When role is ambiguous, flag as **\"Restricted (review required)\"** with the restriction pattern noted\n\n### 3. Contract-Only (Internal Integration Points)\nFunctions callable only by other contracts, not by EOAs. Indicators:\n- Callbacks: `onERC721Received`, `uniswapV3SwapCallback`, `flashLoanCallback`\n- Interface implementations with contract-caller checks\n- Functions that revert if `tx.origin == msg.sender`\n- Cross-contract hooks\n\n## Output Format\n\nGenerate a markdown report with this structure:\n\n```markdown\n# Entry Point Analysis: [Project Name]\n\n**Analyzed**: [timestamp]\n**Scope**: [directories analyzed or \"full codebase\"]\n**Languages**: [detected languages]\n**Focus**: State-changing functions only (view\u002Fpure excluded)\n\n## Summary\n\n| Category | Count |\n|----------|-------|\n| Public (Unrestricted) | X |\n| Role-Restricted | X |\n| Restricted (Review Required) | X |\n| Contract-Only | X |\n| **Total** | **X** |\n\n---\n\n## Public Entry Points (Unrestricted)\n\nState-changing functions callable by anyone—prioritize for attack surface analysis.\n\n| Function | File | Notes |\n|----------|------|-------|\n| `functionName(params)` | `path\u002Fto\u002Ffile.sol:L42` | Brief note if relevant |\n\n---\n\n## Role-Restricted Entry Points\n\n### Admin \u002F Owner\n| Function | File | Restriction |\n|----------|------|-------------|\n| `setFee(uint256)` | `Config.sol:L15` | `onlyOwner` |\n\n### Governance\n| Function | File | Restriction |\n|----------|------|-------------|\n\n### Guardian \u002F Pauser\n| Function | File | Restriction |\n|----------|------|-------------|\n\n### Other Roles\n| Function | File | Restriction | Role |\n|----------|------|-------------|------|\n\n---\n\n## Restricted (Review Required)\n\nFunctions with access control patterns that need manual verification.\n\n| Function | File | Pattern | Why Review |\n|----------|------|---------|------------|\n| `execute(bytes)` | `Executor.sol:L88` | `require(trusted[msg.sender])` | Dynamic trust list |\n\n---\n\n## Contract-Only (Internal Integration Points)\n\nFunctions only callable by other contracts—useful for understanding trust boundaries.\n\n| Function | File | Expected Caller |\n|----------|------|-----------------|\n| `onFlashLoan(...)` | `Vault.sol:L200` | Flash loan provider |\n\n---\n\n## Files Analyzed\n\n- `path\u002Fto\u002Ffile1.sol` (X state-changing entry points)\n- `path\u002Fto\u002Ffile2.sol` (X state-changing entry points)\n```\n\n## Filtering\n\nWhen user specifies a directory filter:\n- Only analyze files within that path\n- Note the filter in the report header\n- Example: \"Analyze only `src\u002Fcore\u002F`\" → scope = `src\u002Fcore\u002F`\n\n## Analysis Guidelines\n\n1. **Be thorough**: Don't skip files. Every state-changing externally callable function matters.\n2. **Be conservative**: When uncertain about access level, flag for review rather than miscategorize.\n3. **Skip read-only**: Exclude `view`, `pure`, and equivalent read-only functions.\n4. **Note inheritance**: If a function's access control comes from a parent contract, note this.\n5. **Track modifiers**: List all access-related modifiers\u002Fdecorators applied to each function.\n6. **Identify patterns**: Look for common patterns like:\n   - Initializer functions (often unrestricted on first call)\n   - Upgrade functions (high-privilege)\n   - Emergency\u002Fpause functions (guardian-level)\n   - Fee\u002Fparameter setters (admin-level)\n   - Token transfers and approvals (often public)\n\n## Common Role Patterns by Protocol Type\n\n| Protocol Type | Common Roles |\n|---------------|--------------|\n| DEX | `owner`, `feeManager`, `pairCreator` |\n| Lending | `admin`, `guardian`, `liquidator`, `oracle` |\n| Governance | `proposer`, `executor`, `canceller`, `timelock` |\n| NFT | `minter`, `admin`, `royaltyReceiver` |\n| Bridge | `relayer`, `guardian`, `validator`, `operator` |\n| Vault\u002FYield | `strategist`, `keeper`, `harvester`, `manager` |\n\n## Rationalizations to Reject\n\nWhen analyzing entry points, reject these shortcuts:\n- \"This function looks standard\" → Still classify it; standard functions can have non-standard access control\n- \"The modifier name is clear\" → Verify the modifier's actual implementation\n- \"This is obviously admin-only\" → Trace the actual restriction; \"obvious\" assumptions miss subtle bypasses\n- \"I'll skip the callbacks\" → Callbacks define trust boundaries; always include them\n- \"It doesn't modify much state\" → Any state change can be exploited; include all non-view functions\n\n## Error Handling\n\nIf a file cannot be parsed:\n1. Note it in the report under \"Analysis Warnings\"\n2. Continue with remaining files\n3. Suggest manual review for unparsable files\n",{"name":5,"description":7,"allowed-tools":24},"Read Grep Glob Bash","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fentry-point-analyzer",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill entry-point-analyzer",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill entry-point-analyzer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill entry-point-analyzer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002FSKILL.md",true,[47,53,57,61,65,69,73,77],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",238,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcosmwasm.md",5477,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Freferences\u002Fcosmwasm.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fmove-aptos.md",3464,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Freferences\u002Fmove-aptos.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fmove-sui.md",3533,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Freferences\u002Fmove-sui.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fsolana.md",4810,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Freferences\u002Fsolana.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fsolidity.md",5071,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Freferences\u002Fsolidity.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fton.md",5058,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Freferences\u002Fton.md",{"path":78,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fvyper.md",3934,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fentry-point-analyzer\u002Freferences\u002Fvyper.md",[82,90,95,102,109,116],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":91,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":89},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":89},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":89},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":89},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":89},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]