[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DSMH2ZAMK247RFF4F1EVT3":3,"skill-same:01M6DSMH2ZAMK247RFF4F1EVT3":83},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6DSMH2ZAMK247RFF4F1EVT3","algorand-vulnerability-scanner",null,"Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL\u002FPyTeal).","AntifragileTech\u002Fantifragile-claude-code","AntifragileTech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F174357194?v=4","01M6DQCYMK4CDSQQAN0ZC72NTV","01M6DQCYS9YPW1WKMQ5TJMPQ43",9,"MIT","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fsecurity\u002Falgorand-vulnerability-scanner\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"scanner","algorand vulnerability scanner","algorand","vulnerability scanner","vulnerability","access","projects","common","use","vulnerabilities","contracts","fees","transaction","Access Control","control","missing","issues","2026-11-10 10:12:30",false,"---\nname: algorand-vulnerability-scanner\ndescription: Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL\u002FPyTeal).\n---\n\n# Algorand Vulnerability Scanner\n\n## 1. Purpose\n\nSystematically scan Algorand smart contracts (TEAL and PyTeal) for platform-specific security vulnerabilities documented in Trail of Bits' \"Not So Smart Contracts\" database. This skill encodes 11 critical vulnerability patterns unique to Algorand's transaction model.\n\n## 2. When to Use This Skill\n\n- Auditing Algorand smart contracts (stateful applications or smart signatures)\n- Reviewing TEAL assembly or PyTeal code\n- Pre-audit security assessment of Algorand projects\n- Validating fixes for reported Algorand vulnerabilities\n- Training team on Algorand-specific security patterns\n\n## 3. Platform Detection\n\n### File Extensions & Indicators\n- **TEAL files**: `.teal`\n- **PyTeal files**: `.py` with PyTeal imports\n\n### Language\u002FFramework Markers\n```python\n# PyTeal indicators\nfrom pyteal import *\nfrom algosdk import *\n\n# Common patterns\nTxn, Gtxn, Global, InnerTxnBuilder\nOnComplete, ApplicationCall, TxnType\n@router.method, @Subroutine\n```\n\n### Project Structure\n- `approval_program.py` \u002F `clear_program.py`\n- `contract.teal` \u002F `signature.teal`\n- References to Algorand SDK or Beaker framework\n\n### Tool Support\n- **Tealer**: Trail of Bits static analyzer for Algorand\n- Installation: `pip3 install tealer`\n- Usage: `tealer contract.teal --detect all`\n\n---\n\n## 4. How This Skill Works\n\nWhen invoked, I will:\n\n1. **Search your codebase** for TEAL\u002FPyTeal files\n2. **Analyze each file** for the 11 vulnerability patterns\n3. **Report findings** with file references and severity\n4. **Provide fixes** for each identified issue\n5. **Run Tealer** (if installed) for automated detection\n\n---\n\n## 5. Example Output\n\nWhen vulnerabilities are found, you'll get a report like this:\n\n```\n=== ALGORAND VULNERABILITY SCAN RESULTS ===\n\nProject: my-algorand-dapp\nFiles Scanned: 3 (.teal, .py)\nVulnerabilities Found: 2\n\n---\n\n[CRITICAL] Rekeying Attack\nFile: contracts\u002Fapproval.py:45\nPattern: Missing RekeyTo validation\n\nCode:\n    If(Txn.type_enum() == TxnType.Payment,\n        Seq([\n            # Missing: Assert(Txn.rekey_to() == Global.zero_address())\n            App.globalPut(Bytes(\"balance\"), balance + Txn.amount()),\n            Approve()\n        ])\n    )\n\nIssue: The contract doesn't validate the RekeyTo field, allowing attackers\nto change account authorization and bypass restrictions.\n\n\n---\n\n## 5. Vulnerability Patterns (11 Patterns)\n\nI check for 11 critical vulnerability patterns unique to Algorand. For detailed detection patterns, code examples, mitigations, and testing strategies, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n\n### Pattern Summary:\n\n1. **Rekeying Vulnerability** ⚠️ CRITICAL - Unchecked RekeyTo field\n2. **Missing Transaction Verification** ⚠️ CRITICAL - No GroupSize\u002FGroupIndex checks\n3. **Group Transaction Manipulation** ⚠️ HIGH - Unsafe group transaction handling\n4. **Asset Clawback Risk** ⚠️ HIGH - Missing clawback address checks\n5. **Application State Manipulation** ⚠️ MEDIUM - Unsafe global\u002Flocal state updates\n6. **Asset Opt-In Missing** ⚠️ HIGH - No asset opt-in validation\n7. **Minimum Balance Violation** ⚠️ MEDIUM - Account below minimum balance\n8. **Close Remainder To Check** ⚠️ HIGH - Unchecked CloseRemainderTo field\n9. **Application Clear State** ⚠️ MEDIUM - Unsafe clear state program\n10. **Atomic Transaction Ordering** ⚠️ HIGH - Assuming transaction order\n11. **Logic Signature Reuse** ⚠️ HIGH - Logic sigs without uniqueness constraints\n\nFor complete vulnerability patterns with code examples, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n## 5. Scanning Workflow\n\n### Step 1: Platform Identification\n1. Confirm file extensions (`.teal`, `.py`)\n2. Identify framework (PyTeal, Beaker, pure TEAL)\n3. Determine contract type (stateful application vs smart signature)\n4. Locate approval and clear state programs\n\n### Step 2: Static Analysis with Tealer\n```bash\n# Run Tealer on contract\ntealer contract.teal --detect all\n\n# Or specific detectors\ntealer contract.teal --detect unprotected-rekey,group-size-check,update-application-check\n```\n\n### Step 3: Manual Vulnerability Sweep\nFor each of the 11 vulnerabilities above:\n1. Search for relevant transaction field usage\n2. Verify validation logic exists\n3. Check for bypass conditions\n4. Validate inner transaction handling\n\n### Step 4: Transaction Field Validation Matrix\nCreate checklist for all transaction types used:\n\n**Payment Transactions**:\n- [ ] RekeyTo validated\n- [ ] CloseRemainderTo validated\n- [ ] Fee validated (if smart signature)\n\n**Asset Transfers**:\n- [ ] Asset ID validated\n- [ ] AssetCloseTo validated\n- [ ] RekeyTo validated\n\n**Application Calls**:\n- [ ] OnComplete validated\n- [ ] Access controls enforced\n- [ ] Group size validated\n\n**Inner Transactions**:\n- [ ] Fee explicitly set to 0\n- [ ] RekeyTo not user-controlled (Teal v6+)\n- [ ] All fields validated\n\n### Step 5: Group Transaction Analysis\nFor atomic transaction groups:\n1. Validate `Global.group_size()` checks\n2. Review absolute vs relative indexing\n3. Check for replay protection (Lease field)\n4. Verify OnComplete fields for ApplicationCalls in group\n\n### Step 6: Access Control Review\n- [ ] Creator\u002Fadmin privileges properly enforced\n- [ ] Update\u002Fdelete operations protected\n- [ ] Sensitive functions have authorization checks\n\n---\n\n## 6. Reporting Format\n\n### Finding Template\n```markdown\n## [SEVERITY] Vulnerability Name (e.g., Missing RekeyTo Validation)\n\n**Location**: `contract.teal:45-50` or `approval_program.py:withdraw()`\n\n**Description**:\nThe contract approves payment transactions without validating the RekeyTo field, allowing an attacker to rekey the account and bypass future authorization checks.\n\n**Vulnerable Code**:\n```python\n# approval_program.py, line 45\nIf(Txn.type_enum() == TxnType.Payment,\n    Approve()  # Missing RekeyTo check\n)\n```\n\n**Attack Scenario**:\n1. Attacker submits payment transaction with RekeyTo set to attacker's address\n2. Contract approves transaction without checking RekeyTo\n3. Account authorization is rekeyed to attacker\n4. Attacker gains full control of account\n\n**Recommendation**:\nAdd explicit validation of the RekeyTo field:\n```python\nIf(And(\n    Txn.type_enum() == TxnType.Payment,\n    Txn.rekey_to() == Global.zero_address()\n), Approve(), Reject())\n```\n\n**References**:\n- building-secure-contracts\u002Fnot-so-smart-contracts\u002Falgorand\u002Frekeying\n- Tealer detector: `unprotected-rekey`\n```\n\n---\n\n## 7. Priority Guidelines\n\n### Critical (Immediate Fix Required)\n- Rekeying attacks\n- CloseRemainderTo \u002F AssetCloseTo issues\n- Access control bypasses\n\n### High (Fix Before Deployment)\n- Unchecked transaction fees\n- Asset ID validation issues\n- Group size validation\n- Clear state transaction checks\n\n### Medium (Address in Audit)\n- Inner transaction fee issues\n- Time-based replay attacks\n- DoS via asset opt-in\n\n---\n\n## 8. Testing Recommendations\n\n### Unit Tests Required\n- Test each vulnerability scenario with PoC exploit\n- Verify fixes prevent exploitation\n- Test edge cases (group size = 0, empty addresses, etc.)\n\n### Tealer Integration\n```bash\n# Add to CI\u002FCD pipeline\ntealer approval.teal --detect all --json > tealer-report.json\n\n# Fail build on critical findings\ntealer approval.teal --detect all --fail-on critical,high\n```\n\n### Scenario Testing\n- Submit transactions with all critical fields manipulated\n- Test atomic groups with unexpected sizes\n- Attempt access control bypasses\n- Verify inner transaction fee handling\n\n---\n\n## 9. Additional Resources\n\n- **Building Secure Contracts**: `building-secure-contracts\u002Fnot-so-smart-contracts\u002Falgorand\u002F`\n- **Tealer Documentation**: https:\u002F\u002Fgithub.com\u002Fcrytic\u002Ftealer\n- **Algorand Developer Docs**: https:\u002F\u002Fdeveloper.algorand.org\u002Fdocs\u002F\n- **PyTeal Documentation**: https:\u002F\u002Fpyteal.readthedocs.io\u002F\n\n---\n\n## 10. Quick Reference Checklist\n\nBefore completing Algorand audit, verify ALL items checked:\n\n- [ ] RekeyTo validated in all transaction types\n- [ ] CloseRemainderTo validated in payment transactions\n- [ ] AssetCloseTo validated in asset transfers\n- [ ] Transaction fees validated (smart signatures)\n- [ ] Group size validated for atomic transactions\n- [ ] Lease field used for replay protection (where applicable)\n- [ ] Access controls on Update\u002FDelete operations\n- [ ] Asset ID validated in all asset operations\n- [ ] Asset transfers use pull pattern to avoid DoS\n- [ ] Inner transaction fees explicitly set to 0\n- [ ] OnComplete field validated for ApplicationCall transactions\n- [ ] Tealer scan completed with no critical\u002Fhigh findings\n- [ ] Unit tests cover all vulnerability scenarios\n","# Algorand Vulnerability Scanner\n\n## 1. Purpose\n\nSystematically scan Algorand smart contracts (TEAL and PyTeal) for platform-specific security vulnerabilities documented in Trail of Bits' \"Not So Smart Contracts\" database. This skill encodes 11 critical vulnerability patterns unique to Algorand's transaction model.\n\n## 2. When to Use This Skill\n\n- Auditing Algorand smart contracts (stateful applications or smart signatures)\n- Reviewing TEAL assembly or PyTeal code\n- Pre-audit security assessment of Algorand projects\n- Validating fixes for reported Algorand vulnerabilities\n- Training team on Algorand-specific security patterns\n\n## 3. Platform Detection\n\n### File Extensions & Indicators\n- **TEAL files**: `.teal`\n- **PyTeal files**: `.py` with PyTeal imports\n\n### Language\u002FFramework Markers\n```python\n# PyTeal indicators\nfrom pyteal import *\nfrom algosdk import *\n\n# Common patterns\nTxn, Gtxn, Global, InnerTxnBuilder\nOnComplete, ApplicationCall, TxnType\n@router.method, @Subroutine\n```\n\n### Project Structure\n- `approval_program.py` \u002F `clear_program.py`\n- `contract.teal` \u002F `signature.teal`\n- References to Algorand SDK or Beaker framework\n\n### Tool Support\n- **Tealer**: Trail of Bits static analyzer for Algorand\n- Installation: `pip3 install tealer`\n- Usage: `tealer contract.teal --detect all`\n\n---\n\n## 4. How This Skill Works\n\nWhen invoked, I will:\n\n1. **Search your codebase** for TEAL\u002FPyTeal files\n2. **Analyze each file** for the 11 vulnerability patterns\n3. **Report findings** with file references and severity\n4. **Provide fixes** for each identified issue\n5. **Run Tealer** (if installed) for automated detection\n\n---\n\n## 5. Example Output\n\nWhen vulnerabilities are found, you'll get a report like this:\n\n```\n=== ALGORAND VULNERABILITY SCAN RESULTS ===\n\nProject: my-algorand-dapp\nFiles Scanned: 3 (.teal, .py)\nVulnerabilities Found: 2\n\n---\n\n[CRITICAL] Rekeying Attack\nFile: contracts\u002Fapproval.py:45\nPattern: Missing RekeyTo validation\n\nCode:\n    If(Txn.type_enum() == TxnType.Payment,\n        Seq([\n            # Missing: Assert(Txn.rekey_to() == Global.zero_address())\n            App.globalPut(Bytes(\"balance\"), balance + Txn.amount()),\n            Approve()\n        ])\n    )\n\nIssue: The contract doesn't validate the RekeyTo field, allowing attackers\nto change account authorization and bypass restrictions.\n\n\n---\n\n## 5. Vulnerability Patterns (11 Patterns)\n\nI check for 11 critical vulnerability patterns unique to Algorand. For detailed detection patterns, code examples, mitigations, and testing strategies, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n\n### Pattern Summary:\n\n1. **Rekeying Vulnerability** ⚠️ CRITICAL - Unchecked RekeyTo field\n2. **Missing Transaction Verification** ⚠️ CRITICAL - No GroupSize\u002FGroupIndex checks\n3. **Group Transaction Manipulation** ⚠️ HIGH - Unsafe group transaction handling\n4. **Asset Clawback Risk** ⚠️ HIGH - Missing clawback address checks\n5. **Application State Manipulation** ⚠️ MEDIUM - Unsafe global\u002Flocal state updates\n6. **Asset Opt-In Missing** ⚠️ HIGH - No asset opt-in validation\n7. **Minimum Balance Violation** ⚠️ MEDIUM - Account below minimum balance\n8. **Close Remainder To Check** ⚠️ HIGH - Unchecked CloseRemainderTo field\n9. **Application Clear State** ⚠️ MEDIUM - Unsafe clear state program\n10. **Atomic Transaction Ordering** ⚠️ HIGH - Assuming transaction order\n11. **Logic Signature Reuse** ⚠️ HIGH - Logic sigs without uniqueness constraints\n\nFor complete vulnerability patterns with code examples, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n## 5. Scanning Workflow\n\n### Step 1: Platform Identification\n1. Confirm file extensions (`.teal`, `.py`)\n2. Identify framework (PyTeal, Beaker, pure TEAL)\n3. Determine contract type (stateful application vs smart signature)\n4. Locate approval and clear state programs\n\n### Step 2: Static Analysis with Tealer\n```bash\n# Run Tealer on contract\ntealer contract.teal --detect all\n\n# Or specific detectors\ntealer contract.teal --detect unprotected-rekey,group-size-check,update-application-check\n```\n\n### Step 3: Manual Vulnerability Sweep\nFor each of the 11 vulnerabilities above:\n1. Search for relevant transaction field usage\n2. Verify validation logic exists\n3. Check for bypass conditions\n4. Validate inner transaction handling\n\n### Step 4: Transaction Field Validation Matrix\nCreate checklist for all transaction types used:\n\n**Payment Transactions**:\n- [ ] RekeyTo validated\n- [ ] CloseRemainderTo validated\n- [ ] Fee validated (if smart signature)\n\n**Asset Transfers**:\n- [ ] Asset ID validated\n- [ ] AssetCloseTo validated\n- [ ] RekeyTo validated\n\n**Application Calls**:\n- [ ] OnComplete validated\n- [ ] Access controls enforced\n- [ ] Group size validated\n\n**Inner Transactions**:\n- [ ] Fee explicitly set to 0\n- [ ] RekeyTo not user-controlled (Teal v6+)\n- [ ] All fields validated\n\n### Step 5: Group Transaction Analysis\nFor atomic transaction groups:\n1. Validate `Global.group_size()` checks\n2. Review absolute vs relative indexing\n3. Check for replay protection (Lease field)\n4. Verify OnComplete fields for ApplicationCalls in group\n\n### Step 6: Access Control Review\n- [ ] Creator\u002Fadmin privileges properly enforced\n- [ ] Update\u002Fdelete operations protected\n- [ ] Sensitive functions have authorization checks\n\n---\n\n## 6. Reporting Format\n\n### Finding Template\n```markdown\n## [SEVERITY] Vulnerability Name (e.g., Missing RekeyTo Validation)\n\n**Location**: `contract.teal:45-50` or `approval_program.py:withdraw()`\n\n**Description**:\nThe contract approves payment transactions without validating the RekeyTo field, allowing an attacker to rekey the account and bypass future authorization checks.\n\n**Vulnerable Code**:\n```python\n# approval_program.py, line 45\nIf(Txn.type_enum() == TxnType.Payment,\n    Approve()  # Missing RekeyTo check\n)\n```\n\n**Attack Scenario**:\n1. Attacker submits payment transaction with RekeyTo set to attacker's address\n2. Contract approves transaction without checking RekeyTo\n3. Account authorization is rekeyed to attacker\n4. Attacker gains full control of account\n\n**Recommendation**:\nAdd explicit validation of the RekeyTo field:\n```python\nIf(And(\n    Txn.type_enum() == TxnType.Payment,\n    Txn.rekey_to() == Global.zero_address()\n), Approve(), Reject())\n```\n\n**References**:\n- building-secure-contracts\u002Fnot-so-smart-contracts\u002Falgorand\u002Frekeying\n- Tealer detector: `unprotected-rekey`\n```\n\n---\n\n## 7. Priority Guidelines\n\n### Critical (Immediate Fix Required)\n- Rekeying attacks\n- CloseRemainderTo \u002F AssetCloseTo issues\n- Access control bypasses\n\n### High (Fix Before Deployment)\n- Unchecked transaction fees\n- Asset ID validation issues\n- Group size validation\n- Clear state transaction checks\n\n### Medium (Address in Audit)\n- Inner transaction fee issues\n- Time-based replay attacks\n- DoS via asset opt-in\n\n---\n\n## 8. Testing Recommendations\n\n### Unit Tests Required\n- Test each vulnerability scenario with PoC exploit\n- Verify fixes prevent exploitation\n- Test edge cases (group size = 0, empty addresses, etc.)\n\n### Tealer Integration\n```bash\n# Add to CI\u002FCD pipeline\ntealer approval.teal --detect all --json > tealer-report.json\n\n# Fail build on critical findings\ntealer approval.teal --detect all --fail-on critical,high\n```\n\n### Scenario Testing\n- Submit transactions with all critical fields manipulated\n- Test atomic groups with unexpected sizes\n- Attempt access control bypasses\n- Verify inner transaction fee handling\n\n---\n\n## 9. Additional Resources\n\n- **Building Secure Contracts**: `building-secure-contracts\u002Fnot-so-smart-contracts\u002Falgorand\u002F`\n- **Tealer Documentation**: https:\u002F\u002Fgithub.com\u002Fcrytic\u002Ftealer\n- **Algorand Developer Docs**: https:\u002F\u002Fdeveloper.algorand.org\u002Fdocs\u002F\n- **PyTeal Documentation**: https:\u002F\u002Fpyteal.readthedocs.io\u002F\n\n---\n\n## 10. Quick Reference Checklist\n\nBefore completing Algorand audit, verify ALL items checked:\n\n- [ ] RekeyTo validated in all transaction types\n- [ ] CloseRemainderTo validated in payment transactions\n- [ ] AssetCloseTo validated in asset transfers\n- [ ] Transaction fees validated (smart signatures)\n- [ ] Group size validated for atomic transactions\n- [ ] Lease field used for replay protection (where applicable)\n- [ ] Access controls on Update\u002FDelete operations\n- [ ] Asset ID validated in all asset operations\n- [ ] Asset transfers use pull pattern to avoid DoS\n- [ ] Inner transaction fees explicitly set to 0\n- [ ] OnComplete field validated for ApplicationCall transactions\n- [ ] Tealer scan completed with no critical\u002Fhigh findings\n- [ ] Unit tests cover all vulnerability scenarios\n",{"name":5,"description":7},"master","c73386b305dec167db7654e0e6feacb462d4f9dc","assets\u002Fskills\u002Fsecurity\u002Falgorand-vulnerability-scanner",1,"https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code","https:\u002F\u002Fgithub.com\u002FAntifragileTech","2026-10-02 14:22:14",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add AntifragileTech\u002Fantifragile-claude-code --skill algorand-vulnerability-scanner",{"tool":53,"command":54},"bunx","bunx skills add AntifragileTech\u002Fantifragile-claude-code --skill algorand-vulnerability-scanner",{"tool":56,"command":57},"pnpm","pnpm dlx skills add AntifragileTech\u002Fantifragile-claude-code --skill algorand-vulnerability-scanner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fsecurity\u002Falgorand-vulnerability-scanner\u002FSKILL.md",true,[61,67,71,75,79],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fauthentication.md","REFERENCE","参考文档",5812,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Finfisical-api\u002Freferences\u002Fauthentication.md",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fpagination-and-rate-limits.md",8449,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Finfisical-api\u002Freferences\u002Fpagination-and-rate-limits.md",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fprojects-and-identities.md",10487,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Finfisical-api\u002Freferences\u002Fprojects-and-identities.md",{"path":76,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fsecrets-endpoints.md",12550,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Finfisical-api\u002Freferences\u002Fsecrets-endpoints.md",{"path":80,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":81,"sourceHtmlUrl":82},"resources\u002FVULNERABILITY_PATTERNS.md",12636,"https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fsecurity\u002Falgorand-vulnerability-scanner\u002Fresources\u002FVULNERABILITY_PATTERNS.md",[84,109,124,139,152,165],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":103,"publishedAt":35},"01M6DT9Q6VYA615SCXR757TZZ7","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwriting-skills\u002FSKILL.md",[90,95,98],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[104,105,26,106,107,108],"writing skills","writing","editing","work","deployment",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":117,"publishedAt":35},"01M6DT9GFHDNY90P41WGAE1TV0","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwriting-plans\u002FSKILL.md",[115,116],{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[118,119,105,120,121,26,122,123],"plans","writing plans","requirements","task","code","spec",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":132,"publishedAt":35},"01M6DT9C6PFGD86WS3HY7YE3XG","docs:write-concisely","Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwrite-concisely\u002FSKILL.md",[130,131],{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[133,134,135,136,137,138,105],"docs:write concisely","write","docs","read","Rules","documentation",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":35},"01M6DT98AWQ27P0N1CG97WAG66","kaizen:why","Iterative Five Whys root cause analysis drilling from symptoms to fundamentals","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwhy\u002FSKILL.md",[],[141,146,147,148,149,150,151],"why","kaizen","issue","five whys","analysis","root cause analysis",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":35},"01M6DT93EH25NAX19R3WGE1P53","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fverification-loop\u002FSKILL.md",[],[159,160,161,162,122,163,164],"verification loop","verification","loop","sessions","claude code sessions","system",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":35},"01M6DT90GW7Z7VCN98P9DVYSNC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fverification-before-completion\u002FSKILL.md",[],[172,160,173,107,26,174,175,176],"verification before completion","commands","evidence","claim","complete"]